Okay something i find very odd.
When booting the livecd network manager is there, i select my wireless net and connect.
Yet i install and it doesn’t appear, i click the network bit under the status tab of the computer menu and by default it’s using ifup and not network manager…anyone else get that? Or is it supposed to be that way…seems rather unfriendly though.
So what you are seeing seems to be correct. I have installed both openSUSE 11.3 RC1 and RC2 and did a system update to 11.3 final release. For new installations, using ifup is the default. If you do an upgrade, your network setup is unchanged from your setup before the upgrade.
Thank You,
Maybe the install should find out if you have some sort of “walk-away” system (like a laptop) or a “fixed” one (always on the same network). Because for the latter network manager is of no use (rather a nuisance).
On 07/15/2010 01:36 PM, hcvv wrote:
>
> Maybe the install should find out if you have some sort of “walk-away”
> system (like a laptop) or a “fixed” one (always on the same network).
> Because for the latter network manager is of no use (rather a nuisance).
It does. If you install without a wireless device in your system, it uses ifup.
If there is a supported wireless device, then NetworkManager is chosen. It gets
it right unless you have a USB or PCMCIA wifi device that is not plugged in when
installing.
For years now, the installer indeed detects this. So installing on my server gives me an ‘ifup’ setup, installing from the same media on my laptop gives me a ‘networkmanager’ setup. I’m sure 11.0 already did this.
@jdmcdaniel3: please verify first before declaring something the default. I did a quick search, but there’s nothing to be found about ifup being the default for openSUSE, instead of an ‘installer decision’.
Larry, you pushed the button first…
Hm, my experience with desktops having both cabled and wireless is that during install configuring the cable using ifup is chosen, but I may be wrong.
In any case, that is correct to me. When being a desktop (or “computer room sever”) ifup is the correct way, cable or wireless.
One only needs network manager when the system must to connect to different networks in a different way on direction from the end-user.
Here is another user that has Wireless (and not connected wired) but got ifup and not Networkmanager. Perhaps you want to read this as well.
Adventures/thoughts installing openSUSE 11.3
Thank You,
Knurpht, the behavior has definitely changed in this release. My laptop, which has had NetworkManager chosen for the last few installs went with ifup this time. The only non-standard part of my installation is that my card is a Broadcom and I have to grab the firmware after the installation is complete. My guess is that the detection has changed and missing firmware now counts as the wireless card not being there.
On 07/15/2010 10:46 PM, quantamm wrote:
>
> Knurpht, the behavior has definitely changed in this release. My laptop,
> which has had NetworkManager chosen for the last few installs went with
> ifup this time. The only non-standard part of my installation is that my
> card is a Broadcom and I have to grab the firmware after the
> installation is complete. My guess is that the detection has changed and
> missing firmware now counts as the wireless card not being there.
Without the firmware, b43 cannot create a wireless device (wlan0), thus your
computer has no wireless device. It is exactly the same as installing with no
wireless device installed!
Sure, I agree, but in 11.1 (and IIRC 11.0 and 11.2) this didn’t stop Suse from using NetworkManager by default.
Read it. In my above posts, only tell about some of the experiences I had and the ideas I have about how several types of systems should be configured.
IMHO there are two decisions to take:
I do not provide solutions, but try to explain that those making the installer have to do some intelligent guessing and they may program differnet solutions in course of time (and thus between openSUSE levels) without it ever getting correct for everybody.
The other thread has an mixed discussion where it seems that some of the participants think that network manager implies wireless (or vv) and ifup implies cabled (or vv). It is not even clear from that thread if the OP has a desktop and thus needs ifup, or a laptop and thus needs network manager. (And I use the words “desktop” and “laptop” not for the size, but for the usage of the box).
On 16/07/10 05:16, quantamm wrote:
>
> lwfinger;2189441 Wrote:
>>
>> Without the firmware, b43 cannot create a wireless device (wlan0), thus
>> your
>> computer has no wireless device. It is exactly the same as installing
>> with no
>> wireless device installed!
>
> Sure, I agree, but in 11.1 (and IIRC 11.0 and 11.2) this didn’t stop
> Suse from using NetworkManager by default.
>
>
I’ve a laptop with a Broadcom device and 11.3 configured Network Manager
as default. Two desktops with Broadcom chips were installed with ifup as
default.
Did you go through most of the wireless card configuration during the
install or do it all afterwards? I’ve a feeling that may make a difference.
–
Graham Davis, Bracknell, Berks. E-mail: newsman, not newsboy
On a slight tangent regarding wireless and installation, it seems a bit pointless to me that the install checks for and sets up the wireless interface and then tries to go on line without the option of typing a passcode. Most wifi routers are protected, but you cannot access them during install.
Oh, and networkmanger should not be the default under KDE at all, ever, as it often causes more problems than it solves, it is a ported gnome programme. KDE really needs to get rid of this and look at something new.
I hope you understand that networkmager is a server runing in your system and is not KDE or Gnome software. It runs as root (of course, nobody else can manage network devices).
The desktops (KDE, Gnome, …) have their own clients to work with networkmanager. The fact that such a client is not functioning as expected has not much to do with networkmanager itself.
Sorry, I should have said Knetworkmanager, which is a poorly implemented client.
No need to apoligize. I allready had the idea what you wanted to say, but it is better for others to make it clear.