yfh2
Apprentice
Joined: 20 May 2004
Posts: 242
|
 Posted: Sat Mar 24, 2007 5:48 pm Post subject: where has the 'lo' network interface gone ? |
 |
|
I have trouble with my network.
Basically, it comes down to the fact that the 'lo' interface has dissapeared.
It 'looks' as if it has been replaced by 'eth0', and 'eth0' by 'eth1' (therefore, I have no network working now)
I don't know where to look at ...
Here are some ouputs :
| Code: |
fanless eb # ifconfig -a
eth0 Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth1 Lien encap:Ethernet HWaddr 00:16:E6:40:F5:4D
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interruption:16
sit0 Lien encap:IPv6-dans-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
|
I don't know wether it's related, but here is the udev.rules part that deals with network devices :
| Code: |
# netlink devices
KERNEL=="route", NAME="netlink/%k"
KERNEL=="skip", NAME="netlink/%k"
KERNEL=="usersock", NAME="netlink/%k"
KERNEL=="fwmonitor", NAME="netlink/%k"
KERNEL=="tcpdiag", NAME="netlink/%k"
KERNEL=="nflog", NAME="netlink/%k"
KERNEL=="xfrm", NAME="netlink/%k"
KERNEL=="arpd", NAME="netlink/%k"
KERNEL=="route6", NAME="netlink/%k"
KERNEL=="ip6_fw", NAME="netlink/%k"
KERNEL=="dnrtmsg", NAME="netlink/%k"
KERNEL=="tap*", NAME="netlink/%k"
# network devices
KERNEL=="tun", NAME="net/%k", MODE="0600"
|
Of course, starting the net.lo fails :
| Code: |
fanless eb # /etc/init.d/net.lo start
* Starting lo
* Bringing up lo
* 127.0.0.1/8
* network interface lo does not exist
* Please verify hardware or kernel module (driver)
|
Any idea ? |
|
Duplicate Threads
