Thanks Jim, I have copied output from tcpdump and netstat below - at least the cable and connections are working, together with the original error message.
(1) tcpdump Tux:/var/log# tcpdump -i eth1 port 67 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 20:12:18.839441 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:19.313829 IP 192.168.0.1.bootps > 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:29.383419 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:29.384031 IP 192.168.0.1.bootps > 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:12:49.321069 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:12:49.321692 IP 192.168.0.1.bootps > 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:13:29.525990 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:13:29.526630 IP 192.168.0.1.bootps > 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:14:48.837241 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:14:48.837908 IP 192.168.0.1.bootps > 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 20:17:27.569570 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:0b:2b:03:d2:57 (oui Unknown), length: 548 20:17:27.570080 IP 192.168.0.1.bootps > 192.168.0.2.bootpc: BOOTP/DHCP, Reply, length: 300 (2) netstat Tux:/home/adam# netstat -anp | grep ":67 " udp 0 0 0.0.0.0:67 0.0.0.0:* 3 669/dhcpd3 Tux:/home/adam# (3) Error message (transcribed, possibly with human error) Loading ROM image .... ROM segment 0x0000 length 0x0000 reloc 0x00020000 Etherboot 5.2.5 (GPL) http://etherboot.org Tagged ELF for [RTL8139] Relocating text from: [00013a50,0002454) to [05cef510,05f00000) Boot from (N)etwork or (Q)uit ? Probing pci nic ... [rtl8139] - ioaddr 0x1400, addr 00:0B:2B:03:D2:57 100Mbps full-duplex Searching for server (DHCP) ................... I'd welcome any constructive suggestions .. the natives are restless. Adam Bogacki, [EMAIL PROTECTED] On Thu, Sep 08, 2005 at 09:43:19AM -0400 or thereabouts, Jim McQuillan wrote: > Adam, > > I've missed the initial conversation of what's going on. > > If your client is saying 'Seeking server (DHCPD)' (btw, I think you > need to reread what it says on the screen, because although I've seen > something similar, I don't think that's exactly what it says). > > Anyway, if it says something like that, then it sounds like the client > can't find the DHCP server. Any monkeying around with the > 'next-server' parameter in dhcpd.conf won't have any effect on this, cuz > the client hasn't even found the dhcp server. next-server is for the > next step AFTER the dhcp reply. > > Watch in your log files. Depends on the distro, but look in > /var/log/daemon.log, or /var/log/messages or /var/log/syslog for info, > as the client is searching for the dhcp server. > > Also, try using tcpdump to watch the packets, and see if you are seeing > any DHCP packets. The syntax would be: > > tcpdump -i eth1 port 67 or 68 > > Adjust your 'eth1' as appropriate for your server. > > Once tcpdump is running, then turn on the client, and see what you get. > > If you don't see anything, then your clients dhcp requests aren't > getting to the server. Check cables and switches. > > If you do see DHCP requests, then the packets are getting to the server, > so now you need to figure out if the server is actually paying attention > to them. > > Is dhcpd actually listening? > > netstat -anp | grep ":67 " > > Should tell you. If you get no output from that command, then you need > to figure out why dhcpd isn't listening. > > Hope that helps, > > Jim McQuillan > [EMAIL PROTECTED] > > On Thu, 8 Sep 2005, Adam Bogacki wrote: > > > On Tue, Sep 06, 2005 at 06:03:41PM +0200 or thereabouts, Dave Cotton wrote: > > > On Tue, 2005-09-06 at 21:01 +1200, Adam Bogacki wrote: > > > > On Tue, Sep 06, 2005 at 08:47:23AM +0200 or thereabouts, Dave Cotton > > > > wrote: > > > > > On Tue, 2005-09-06 at 18:40 +1200, Adam Bogacki wrote: > > > > > > > > > > > It seems I have the same problem but having looked at > > > > > > 'ltspcfg' I can find no 'next-server' entry. > > > > > > > > > > > > Could you be more specific where it may be found ? > > > > > > > > > > > > > > > > It isn't in ltspcfg (yet, Jim? :)) just edit dhcpd.conf directly. > > > > > > > > > > I now have:- > > > > > > > > > > next-server [ip-of-original-server]; > > > > > > > > > > Seems also to give a speed boost to finding the server. > > > > > > > > > > > > > > > -- > > > > > Dave Cotton <[EMAIL PROTECTED]> > > > > > > > > > Thanks .. but it still hangs at "Searching for server > > > > [DHCPD] ..." > > > > > > > > Is this what you had in mind ? > > > > > > > > Adam. > > > > > > > > [1] dhcpd.conf > > > > > > > > >option domain-name-servers 203.96.152.4, 203.96.152.12; > > > > >option routers 192.168.0.1; > > > > >option subnet-mask 255.255.255.0; > > > > >default-lease-time 21600; > > > > >max-lease-time 21600; > > > > >next-server 203.79.110.81; > > > > > > No, surely this is your external address. > > > > > > If this is running on 192.168.0.1, strange as it may seem, 192.168.0.1 > > > is the next-server address. > > > > > Hmm .. thanks, but it still hangs at 'seeking server (DHCPD)'. > > What else am I missing here ? > > > > Adam Bogacki. > > > > "Anyone who believes that exponential growth can go on forever in a > > finite world is either a madman or an economist". > > > > -- Kenneth E. Boulding > > > > > > -- > > > Dave Cotton <[EMAIL PROTECTED]> > > > > > > > > >
signature.asc
Description: Digital signature
