Am Mittwoch, 25. Oktober 2006 09:55 schrieb Tim Post: > Hotplug setup right? May help to post your /etc/network/interfaces file. > > Best, > -Tim > > On Wed, 2006-10-25 at 09:17 +0200, Bernd Kloss wrote: > > Etch > > 2.6.17-2-k7 > > different realtek, 3COM, onboards > > > > Hello, > > > > I am having problems with clients on boot. > > Client is booting, but not finding yp-server > > This occurs on different clients, sometimes I have to reboot a client a > > few times and then it works. This behaviour is not reproducable. No > > rules. > > > > ifconfig shows description for lo, nothing for eth0. > > On > > ifconfig eth0 192.168.136.XYZ > > /etc/init.d/nis start > > everything is working normally. > > > > Has anyone a clue? > > > > Thanks and greetings > > Bernd Kloss
On running hwinfo, I found following information: net interface: name = lo, path = /class/net/lo type = 772 hw_addr = 00:00:00:00:00:00 net interface: name = eth0, path = /class/net/eth0 type = 1 hw_addr = 00:14:85:51:65:5b net device: path = /devices/pci0000:00/0000:00:12.0 net driver: name = via-rhine, path = /bus/pci/drivers/via-rhine net interface: name = sit0, path = /class/net/sit0 type = 776 hw_addr = 00:00:00:00 lo: ethtool link state: 1 eth0: ethtool link state: 1 ********************************************** sit0: GLINK ethtool error: Invalid argument ********************************************** >> pppoe.1: looking for pppoe >> pppoe.2: discovery Attempt number 1 eth0: Sending PADI packet Timeout waiting for PADO packets Attempt number 2 What is sit0 and what is GLINK tool. Is there any hint for not initialising eth0 correctly? Greetings Bernd Kloss
