> > > However, i just installed Jaunty RC (AMD64), and
> i
> > couldn't get an
> > > address via DHCP. So it seems. Ethernet and DHCP
> is
> > supposed to be
> > > pretty agnostic, so i don't see why a different
> > version or different
> > > arch would give problems. So it could be problem
> > interfacing with the
> > > Ethernet card itself? However.... doing an
> ifconfig, i
> > can see that
> > > eth0 gets detected, and its HWaddr (MAC) is
> correct.
> > But, of course,
> > > there is no inet addr.
> >
> > 0] make sure that eth0 = the correct interface that
> you
> > plugged into by
> > looking at dmesg output before and after
> > plugging in the ethernet.
> >
> > 1] install tcpdump and start a packet capture
> >
> > sudo /usr/sbin/tcpdump -n -i eth0 -s 0
> > -w /tmp/packets.pcap
> >
> > While the capture is running, restart your dhcp
> client.
> > After that
> > fails, stop the capture (CTRL-C or sudo killall
> tcpdump)
> > and post it
> > online someplace where we can review it.
> >
> > 2] review packet capture with wireshark:
> >
> > http://wireshark.org/download.html
> >
> > When we have the file, we can review the capture as
> well
> > and see where
> > things are going awry.
>
>
>
> Thanks Patrick,
>
> i have done dmesg and tcpdump... i'll post (what seems to
> me) as the important bits here. Please let me know if the
> full files are really needed. From my very limited
> knowledge, it seems that it's trying to use IPv6...
>
>
> For dmesg, these are the few additional lines after i
> plugged in the ethernet cable (i unplugged it before
> booting):
>
> [ 168.930758] skge eth0: Link is up at 100 Mbps, full
> duplex, flow control none
> [ 168.931355] ADDRCONF(NETDEV_CHANGE): eth0: link
> becomes ready
> [ 179.232011] eth0: no IPv6 routers present
>
>
> For tcpdump, here is the whole output during the failed
> DHCP request (i used tcpdump -r to parse the captured pcap
> file)...
>
> 18:29:07..003884 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: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
>
> The MAC address in the tcpdump above is correct; it's of
> the eth0 interface.
Just to add on... i repeated the dmesg and tcpdump using the Jaunty i386 live
CD boot (with the successful DHCP).
For dmesg, there is the additional information about promiscuous mode. The 5
lines after i plugged in the ethernet cable are:
[ 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
For tcpdump, there is plenty of activity, including of course, the response for
DHCP/BOOTP.
hmm... if (in the AMD64), eth0 did not go into promiscuous mode, that is why it
could not get the broadcast DHCP response?
Thanks and Regards,
Edwin
Get your preferred Email name!
Now you can @ymail.com and @rocketmail.com
http://mail.promotions.yahoo.com/newdomains/sg/
_______________________________________________
Slugnet mailing list
[email protected]
http://wiki.lugs.org.sg/LugsMailingListFaq
http://www.lugs.org.sg/mailman/listinfo/slugnet
