Ack...I'm an idiot. You've already said it's running.
I guess the next question is "is eth1 your internal LAN interface"?
On Mon, 22 Sep 2003, Vidiot wrote:
> I have a W2K laptop that I am attempting to connect to my internal LAN, but
> DHCP appears to not be working. THe daemon is running:
>
> ps -eaf | grep dhcp
> root 26358 1 0 Sep03 ? 00:00:03 /usr/sbin/dhcpd eth1
>
> The dhcp config file is as follows:
>
> cat dhcpd.conf
> subnet 192.168.1.0 netmask 255.255.255.0 {
> # --- default gateway
> option routers 192.168.1.1;
> option subnet-mask 255.255.255.0;
>
> option domain-name "vidiot.com";
> option domain-name-servers 192.168.1.1;
>
> # option time-offset +6; # GMT
> # option ntp-servers 192.168.1.1;
> # option netbios-name-servers 192.168.1.1;
> # --- Selects point-to-point node (default is hybrid). Don't change this unless
> # -- you understand Netbios very well
> # option netbios-node-type 2;
>
> range 192.168.1.11 192.168.1.20;
> # default-lease-time 21600;
> # max-lease-time 43200;
> }
>
>
> I saw the following when the laptop was booting (traffic from other PeeCees
> removed):
>
> 09:03:28.384060 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc32dfe66 [|bootp]
> 09:03:31.384659 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc32dfe66 secs:768
> [|bootp]
> 09:03:39.386238 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc32dfe66 secs:2816
> [|bootp]
> 09:03:55.389316 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xc32dfe66 secs:6912
> [|bootp]
> 09:04:26.405221 B arp who-has 169.254.149.109 tell 169.254.149.109
> 09:04:26.935322 B arp who-has 169.254.149.109 tell 169.254.149.109
> 09:04:27.935513 B arp who-has 169.254.149.109 tell 169.254.149.109
> 09:04:31.276146 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x544a8d2d
> flags:0x8000 [|bootp]
> 09:04:34.286713 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x544a8d2d secs:768
> flags:0x8000 [|bootp]
> 09:04:37.967401 B 169.254.149.109.netbios-ns > 169.254.255.255.netbios-ns:NBT UDP
> PACKET(137): REGISTRATION; REQUEST; BROADCAST
> 09:04:38.717541 B 169.254.149.109.netbios-ns > 169.254.255.255.netbios-ns:NBT UDP
> PACKET(137): REGISTRATION; REQUEST; BROADCAST
> 09:04:39.467680 B 169.254.149.109.netbios-ns > 169.254.255.255.netbios-ns:NBT UDP
> PACKET(137): REGISTRATION; REQUEST; BROADCAST
> 09:04:40.227821 B 169.254.149.109.netbios-ns > 169.254.255.255.netbios-ns:NBT UDP
> PACKET(137): REGISTRATION; REQUEST; BROADCAST
> 09:04:42.288203 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x544a8d2d secs:2816
> flags:0x8000 [|bootp]
> 09:04:50.009617 B 169.254.149.109.netbios-ns > 169.254.255.255.netbios-ns:NBT UDP
> PACKET(137): REGISTRATION; REQUEST; BROADCAST
> 09:04:50.759754 B 169.254.149.109.netbios-ns > 169.254.255.255.netbios-ns:NBT UDP
> PACKET(137): REGISTRATION; REQUEST; BROADCAST
>
>
>
> The 169 address is the last used address when it was connected at work.
>
> Anyone have an idea as to why DHCP is not responding?
>
> Thanks.
>
> MB
>
--
Mike Burger
http://www.bubbanfriends.org
Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000
To be notified of updates to the web site, send a message to:
[EMAIL PROTECTED]
with a message of:
subscribe
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
