Hello
i have selected networkmanager in YaST2 for my internet connexion because i think knetworkmanager is easy to use when i want to connect my laptop to a wifi AP when i’m away from home.
But when i’m home, i’ need to connect to my home ethernet network with a fix ip for some good reason like file synchronization via unison and tv via ip .
Therefore i used knetworkmanager to configure a connexion on my ethernet card . I entered all parameters on the knetwork window : fixed ip, network mask, DNS, default gateway, connexion name and, of course, i checked the automatic connexion box .
Then, i expect knetworkmanager to connect automatically with the fixed IP parameters i entered at each login when my ethernet cable is plugged into my laptop ethernet card at home . On opensuse 10.3, it works correctly, but with opensuse 11.1, it does not. Surprisingly, on opensuse 11.1, it connects with a dhcp IP, so without the fixed IP i parametered !!! (like 192.168.0.50 instead of 192.168.0.8)
I need this fixed IP, as written above.
I am quite disappointed by this unexpected bug/behaviour.
Maybe, there is a simple workaround ?
Is there some configuration feature that i missed to perform ?
How can i correct this annoying bug ?
Thanks for your help .
As a workaround you could in YaST networking settings set it to ifup while at home. I’ll agree that isn’t exactly a solution you want to hear… but till a better one is posted you could at least do your normal things.
Another possible workaround, maybe even one you want to use as a permanent solution is checking if your accesspoint/wireless router has an option to couple your mac address to a ‘static’ IP address.
I have run kdcop to find some function that i could call with a script at startup, something like ’ "dcop knetworkmanager connect “eth0” ’ . But i found nothing like that.
OK, sorry for my late reply due to … real life .
I finally found the time to reopen this opensuse 11.1
After a long research i found that NetworkManager is supposed to connect as
soon as possible to any network. And, at login, knetworkmanager seems to be
satisfied when a network is already connected.
So i took a look at NetworkManager and found intersting stuff
in /etc/NetworkManager/system-connections/ .
Here, you can find a config file named “System eth0” containing :
[ipv4]
method=auto
…
It means that networkmanager is doing some auto adressing (dhcp) for eth0 when
i want some manual. So, i searched the web for some other examples and i
finally filled it up with this :
[ipv4]
method=manual
adress1=192.168.x.y;255.255.255.0;192.168.x.1
dns=123.123.123.123
dns-search=domain.com
…
And now i have knetworkmanager and the fixed ip i wanted. And what is strange
is that knetworkmanager guesses that the connection configured by
Networkmanager corresponds to the one configured in knetworkmanager . Weird.
Anyway, first it is not what is expected.
And second, if i connect somewhere else than home with a wired connection,
networkmanager will not connect automatically with dhcp.
Thanks for your answers.
I’m investigating this in https://bugzilla.novell.com/show_bug.cgi?id=526582
wstephenson >> Great ! Shall i add a comment ?
wstephenson >> i have added my vote to your bug report …