On Sat, Apr 18, 2009 at 11:02:16AM +0800, Edwin Lee wrote: > > 18:29:13.006158 IP 0.0.0.0.bootpc > 255.255.255.255..bootps: > > BOOTP/DHCP, Request from 00:1b:fc:28:6c:59 (oui Unknown), length 300 > > 18:29:22.009067 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: > > BOOTP/DHCP, Request from 00:1b:fc:28:6c:59 (oui Unknown), length 300 > > 18:29:42.020064 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: > > BOOTP/DHCP, Request from 00:1b:fc:28:6c:59 (oui Unknown), length 300 Wow. So the router just doesn't respond to the dhcp client.
> [ 194.701027] device eth0 entered promiscuous mode > [ 203.407978] skge eth0: Link is up at 100 Mbps, full duplex, flow control > none > [ 203.408125] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > [ 211.866817] device eth0 left promiscuous mode > [ 214.360013] eth0: no IPv6 routers present > > hmm... if (in the AMD64), eth0 did not go into promiscuous mode, that is why > it could not get the broadcast DHCP response? That should be due to tcpdump setting the driver to listen to all packets (promiscuous mode). > Just to add on... i repeated the dmesg and tcpdump using the Jaunty > i386 live CD boot (with the successful DHCP). For a sanity check, can you statically set your IP address and does that work? I just want to make sure that the rest of its TCP/IP stack works fine and that the dhcp client is the only thing broken. Thanks, Patrick _______________________________________________ Slugnet mailing list [email protected] http://wiki.lugs.org.sg/LugsMailingListFaq http://www.lugs.org.sg/mailman/listinfo/slugnet
