Short questions on DHCP
declan.moriarty at ntlworld.ie
Wed Oct 20 06:39:57 PDT 2004
I'm not getting going with DHCP, and have found it difficult to
make sense of why. Every one else does it in their sleep, but that
isn't much use to me. Both the linux daemons just get to
DHCPDISCOVER and time out. They apparently get no answer
Windows sets up. ipconfig /all (In windoze) gives me
dhcp derver - 220.127.116.11
dns server - 18.104.22.168
netmask - 255.255.255.0
gateway - 22.214.171.124
IP - 126.96.36.199
Beyond that, it appears to use nothing fancy.
The setup scripts in linux are a mess, so I want to set it manually
once and then get the scripts to do what works. Manually adding routes
route add <several>
as suggested in various docs to get on using an existing lease fails
Why? The only difference I can spot is in the case of the hostname
Likewise asking NTL, who assure me that the cable
modem assigns the IP to the box it operates off and consequently
I don't need any info. NTL do talk more crap than sense, but
it's an ntl badged cable modem. Could that be?
The guy who put installed this lifted a serial number from it and
rang it in. Is that an item of information used in the protocol?
A little port scan under windows showed the system has the BOOTP
instead of DHCP on port 67, but the windoze box listens on port 68.
More information about the blfs-support