On Wednesday 09 September 2009 15:03:04 LM--- wrote: > [...] > > _The_ _problem_ : > > The selection of the eth0 interface, into which the DSL cable coming > from the router is plugged does not take place. The system > “automatically” chooses usb0, which is not wired – unless I interfere > manually. > > > _Description_ _of_ _facts_ : > > During booting, everything seems to go fine: I can read (as I always > read under etch, which is still on my desktop) the following: > DHCPOFFER from xxx.xxx.x.xxx > DHCPREQUEST on eth0 to 255.255.255.255 port 67 > DHCPACK from xxx.xxx.x.xxx > bound to xxx(IP address of the "right" interface, eth0)xxx - renewal > in ..... seconds > done
Looks good. You should be able to ping at least xxx.xxx.x.xxx (DHCPACK from ...). > And then, I don't know why, once the booting process is over and I > log in, everything goes wrong... > > - Under KDE: > Situation # 1 > KNetworkConf (in KDE ConfigCentre – Network parameters) does show > eth0 _alone_ , but it is not given any IP address (although DHCP is > the preselectioned IP detection mode); nothing changes before > detection is restarted by deactivating then reactivating the > interface in this module. Situation #2 > knetworkmanager, the applet I installed to ease connection and > deconnection to the network, is as much “confused”; after KDE starts > it “runs empty” can't/won't connect to any interface for about 20 > seconds, to finally systematically choose the wrong one: “usb0” I don't know that tool and I would not trust it. But did you by chance install the network-manager? dpkg -l network-manager will tell you. > - Under command line: > if I go to the command line with tty1 --> log in --> turn to root --> > to enter instruction "ifconfig -a" , in the first 20 seconds I get > this: > > eth0 Link encap:Ethernet HWaddr 00:02:b3:eb:d8:02 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:15 errors:0 dropped:0 overruns:0 frame:0 > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:1000 > RX bytes:1913 (1.8 KiB) TX bytes:8587 (8.3 KiB) > > lo Link encap:Boucle locale > inet adr:127.0.0.1 Masque:255.0.0.0 > adr inet6: ::1/128 Scope:Hôte > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:52 errors:0 dropped:0 overruns:0 frame:0 > TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:0 > RX bytes:3500 (3.4 KiB) TX bytes:3500 (3.4 KiB) > > usb0 Link encap:Ethernet HWaddr 5e:cd:b5:00:88:c4 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:4 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > and later I get that: > > eth0 Link encap:Ethernet HWaddr 00:02:b3:eb:d8:02 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:17 errors:0 dropped:0 overruns:0 frame:0 > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:1000 > RX bytes:2033 (1.9 KiB) TX bytes:8587 (8.3 KiB) > > lo Link encap:Boucle locale > inet adr:127.0.0.1 Masque:255.0.0.0 > adr inet6: ::1/128 Scope:Hôte > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:52 errors:0 dropped:0 overruns:0 frame:0 > TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:0 > RX bytes:3500 (3.4 KiB) TX bytes:3500 (3.4 KiB) > > usb0 Link encap:Ethernet HWaddr 5e:cd:b5:00:88:c4 > inet adr:169.254.91.233 Bcast:169.254.255.255 > Masque:255.255.0.0 adr inet6: fe80::5ccd:b5ff:fe00:88c4/64 > Scope:Lien > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:16 dropped:0 overruns:0 carrier:0 > collisions:0 lg file transmission:1000 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) That IP is probably just fine and a zeroconf address (rfc3927), most definitely from avahi-autoipd and does not harm nor help. However, it's quite strange that your eth0 does not have an ip address. > This confirms what I see under KDE: > something (what?) makes the system (which element, routine, module, > programme, package?) choose the wrong interface “usb0”. > > How to solve this problem? This is the whole headache here! > > My other problem is, I don't really know which other tests to carry > out to find out which setting I have to try with which programme, > routine or module or else... - before thinking of filling any bug > report for a particular package... Please check if you have network-manager installed. You could also try `ip addr` and the like. > If you have ideas, I would be very thankful (if you need other > information, let me know, I'll get it for you). > > Thanks very much in advance. > > Ludo > > > PS Here is the contents of the first /etc/network/interfaces file > (the one generated at install) > > BEGIN--- > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > address 127.0.0.1 > netmask 255.0.0.0 > > # The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp > > auto eth0 > > END--- > > I've had five versions and none worked as I wished... Did you try commenting out allow-hotplug eth0? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
