Le dimanche 27 décembre 2009 à 22:40 +1030, Karl Goetz a écrit : > On Sun, 27 Dec 2009 12:27:49 +0100 > samy boutayeb <s.bouta...@free.fr> wrote: > > > Hi, > > On the Yeeloong, wen I use a 2.6.27 or 2.6.31 kernel, the IP address > > is 192.168.1.x at boot time, as assigned by the dhcp server > > (192.168.1.1). So far, it's all right. > > > > However, with a 2.6.32.* kernel, the IP address assigned to eth0 is > > 169.254.57.xxx (which seems logical, considering the default parameter > > "link-local 169.254.0.0" in /etc/networks. I have to run dhclient in > > order to get a correct dynamic address for the eth0 interface. > > This parameter get lost after: > > - rebooting the Yeeloong > > - suspending it with FN+F1 > > > > Is this the intended behavior for the assignment of the ip address? > > * Do you have network manager? yes
> * What is the contents of your /etc/network/interfaces? # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp This said, if I execute network-admin, I have to choose the correct platform (I choose "gNewSense mipsel-l"), but this parameter get lost after rebooting. Then, the roaming mode parameter remains checked for both interfaces even if I try to uncheck them. Thanks Samy > kk > > > Regards, > > > > Samy > > _______________________________________________ > gNewSense-dev mailing list > gNewSense-dev@nongnu.org > http://lists.nongnu.org/mailman/listinfo/gnewsense-dev _______________________________________________ gNewSense-dev mailing list gNewSense-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/gnewsense-dev
