[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

netcfg rc3 - dhcp failing



Hi

I've trawled the debian-boot mailing lists regarding the netcfg tool in
the netboot debian install and I was unable to find any existing
instances of this problem, so I was wondering if you could help.

The problem:

We are finding that during a network installation of debian, using the
d-i 2.6 kernel and initrd.gz, the install will stop at the dhcp/netcfg
step:


──────────────────┤ [!!] Configure the network ├────────────────────┐
                 Network autoconfiguration failed                    

  Your network is probably not using the DHCP protocol. Alternatively,  
  the DHCP server may be slow or some network hardware is not working
  properly.

                          <Continue>                             


If the user at this point manually selects 'continue' and then selects
'Retry network autoconfiguration' then the d-i successfully completes
dhcp autoconfiguration and continues into the installation.

However, if one jumps into the second virtual terminal after the above
netcfg failure and checks the interfaces and the routing table, you see
the following:

~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:0D:60:EB:16:B8
          inet addr:192.168.10.109  Bcast:192.168.10.255
Mask:255.255.255.0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1894 (1.8 KiB)  TX bytes:1384 (1.3 KiB)
          Base address:0x2500 Memory:fbfe0000-fc000000
~ #
~ # ip link
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0d:60:eb:16:b8 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0d:60:eb:16:b9 brd ff:ff:ff:ff:ff:ff
~ # ip route show
192.168.10.0/24 dev eth0  src 192.168.10.109
default via 192.168.10.1 dev eth0
~ # route
Kernel IP routing table
Destination	Gateway	Genmask		Flags Metric  Ref    Use Iface
192.168.10.0	*	255.255.255.0	U     0	      0	     0	 eth0
default		192.168.10.1   0.0.0.0	UG    0       0      0   eth0
~ #
~ # ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/32 scope host lo
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0d:60:eb:16:b8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.109/24 brd 192.168.10.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0d:60:eb:16:b9 brd ff:ff:ff:ff:ff:ff

So it seems that the netcfg succeeds to obtain the dhcp address but does
not seem to realise it.  This is on hardware requiring the e1000 or tg3
driver using the 2.6 kernel.  However, when booting on systems which
require the e100 driver we do not see this problem.

Can you offer any advice as to why this might be happening?  Do you
think it could be related to the isc-dhcp server which I'm running?  Or
to the e1000/tg3 drivers?

Please let me know what further information would be of use to
diagnosing this problem.

Many thanks.  Kind regards

- William



Reply to: