> > This is a dhclient issue, not an NM issue. Does your DHCP service > require certain options to be sent to it? If the server offered > 192.168.0.1 to the client, and dhclient is now requesting that address, > the server shouldn't be NAK-ing the request that it just sent to the > client. > > After some further tinkering around it seems like it's working. Must have been something wrong on the serverside (strangely enough, though, even previously, running dhclient eth0 from the terminal would work just fine, where as NM would fail to connect).
Anyway, sorry for the noise. I'll get back if I find something strange. Regards, Khashayar
_______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
