On Monday, March 28, 2011 06:28:33 am Yamaban wrote:
On Mon, 28 Mar 2011 13:58, Don Raboud
wrote: On Monday, March 28, 2011 04:37:05 am Yamaban wrote:
On Mon, 28 Mar 2011 03:01, Don Raboud
wrote: Is there a way to force Network Manager to autoconnect using a fixed IP address? There is a conection present called "Auto eth0" which takes precedence over my defined connection "Fixed IP".
Under Manage Connections there is no "Auto eth0" listed, so it appears to be built in and I can't change anything about it. Under my defined connection "Fixed IP" "Connect automatically" is checked but that hasn't helped. (There is also a greyed-out unchecked box "System connection".)
<snip>
- in section "Network Setup Method" select Traditional Method with ifup.
<snip>
--
Yamaban, - who really dislikes the "Network Manager" behavior, - out.
8-)
Thanks Yamaban for the detailed instructions! That would however leave me back at the traditional method (an option I was considering) but I am trying to get Network Manager to work predictably with respect to automagically assigned IP addresses.
In the meantime, I think I have found a workaround. Network Manager calls dhcpclient when an automatic connection needs to be made. So I edited /etc/dhclient.conf by adding the following lines to the end of the default supplied file
interface "eth0" {
fixed-address 192.168.1.65;
}
so that dhclient will request this specific IP address. The router happily supplies it, so I now get the desired behavior. Hopefully nothing else gets messed up by this change, but as this is my home machine with one wired connection only, I don't think this will cause any problems.
Wow! Never thougt of this in conjuction with Network Manager. For a "normal" Desktop with "just" one ip this should work for sure.
(My setup is much more complex, three eth, one with two IPv4, one with six IPv4 and four IPv6, and one with zero IPv4 but eight IPv6, all with vlan config, a bit much for Network Manager. And then comes the routing. No fun at all the first time, but great when it works.)
Wow! I don't even want to know why it is like that...
Cheers, and kudos to you, please be so nice and share your solution in the forum.
Yamaban, I'll be happy to share it, when it finally works :-( I thought it was working. Before the change, "Fixed IP" -> consistently returned 192.168.1.65 "Auto eth0" -> *consistently* returned 192.168.1.64. I made the change stated above (and only that change), restarted the network, and both interfaces now *consistently* (about 5 attemps each) return 192.168.1.65. However, to be sure this was working as expected, I changed the dhconfig.conf file to request a different address (192.168.1.66 or 192.168.1.200) and followed the same steps and this time the change did not work - I still get 192.168.1.65 consistently from both interfaces, whnich is an improvement, but not predictable. From the logs, "Auto eth0" calls dhcpclient so I think this approach should work, but as I see three possible issues spring to mind: 1) dhcpclient and dhclient.conf cannot combine to request a fixed ip address. From my reading of the man page (admittedly late last night) it appears that this should be possible however. 2) I have the syntax wrong for dhclient.conf - this is a distinct possibility. I'll have to do more digging and testing as I've never played with this before. 3) My particular router won't honor such a request for a fixed IP address. I have no idea about this one. I'll report back anything I find out. If anyone else has any ideas I would appreciate the input. -- Don -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org