*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> Before I go much further, what is the tcpdump command to dump the
> dhcp packets, and how would I then decode them to figure out what is
> going wrong?
The command is ``tcpdump -e -x -s 1500 udp port 67'', and interpreting
them is a pain - you need to basically decode them yourself, because
tcpdump won't do it for you. I have a patch from a friend and fellow
DHCP hacker to tcpdump that I haven't had time to try yet, but I
usually just copy the hexadecimal output into an emacs buffer and run
an emacs macro on it that unpacks it into a set of nested
S-expressions. If you're emacs-lisp-literate, I can send you the
macros...
You may be able to get quick satisfaction by just moving the filename
declarations inside of the host declarations, BTW.
_MelloN_
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
