IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New dhcp command line client side tool
building a kickstart box
havnt messed with bootp in 18 years and its now dhcp
needed to figure out if the server was behaving before trying a PXE boot
needed a command line tool

http://www.phystech.com/download/
dhcpcd-1.3

add the following to /etc/syslog.conf
file:
local0.* /var/log/dhcpcd.log


refresh syslogd

get the following output
***********
Aug 28 03:20:34 lin10 dhcpcd[29232]: broadcasting DHCP_REQUEST for 192.168.0.207
Aug 28 03:20:34 lin10 dhcpcd[29232]: dns option is missing in DHCP server response. Assuming 192.168.0.105
Aug 28 03:20:34 lin10 dhcpcd[29232]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.0.255
Aug 28 03:20:34 lin10 dhcpcd[29232]: dhcpIPaddrLeaseTime=86400 in DHCP server response.
Aug 28 03:20:34 lin10 dhcpcd[29232]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec
Aug 28 03:20:34 lin10 dhcpcd[29232]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec
Aug 28 03:20:34 lin10 dhcpcd[29232]: DHCP_ACK received from (192.168.0.105)
New What does the server config look like?
And exactly which DHCP server are you using?

The simplest thing to do with DHCP is to throw Wireshark in the middle and see what the request and response actually contain. Otherwise it just becomes second guessing, trying to figure out which options map between client and server configurations.
New actually it sez what I wanted it to
trouble was that the usual telnetting to the port while running tcpdump didnt give me the info I wanted. These tools emulate a DHCPDISCOVER and report back verbosely. That gave me the info I needed.
thanx,
bill
     dhcp command line client side tool - (boxley) - (2)
         What does the server config look like? - (scoenye) - (1)
             actually it sez what I wanted it to - (boxley)

Battling him is like wiping off puppy slobber.
49 ms