On 08/02/2011 15:08, Jürgen Dietl wrote:
Hello, its me again,
I am still fighting with DHCP-Fail Over. I am very happy that
there is a dissector for dhcp-fo already in wireshark and I say
a big thanx for this.
When I look at the packet-dhcp-failover.c at http://ethereal.sourcearchive.com/documentation/0.10.10/packet-dhcp-failover_8c-source.html
I can see the following server and message type:
DHCP_FO_SS_UNKNOWN_PACKET,
DHCP_FO_SS_PARTNER_DOWN,
DHCP_FO_SS_NORMAL,
DHCP_FO_SS_COMMUNICATION_INTERRUPTED,
DHCP_FO_SS_RESOLUTION_INTERRUPTED,
DHCP_FO_SS_POTENTIAL_CONFLICT,
DHCP_FO_SS_RECOVER,
DHCP_FO_SS_RECOVER_DONE,
DHCP_FO_SS_SHUTDOWN,
DHCP_FO_SS_PAUSED,
DHCP_FO_SS_STARTUP,
DHCP_FO_SS_RECOVER_WAIT
/* message-types of failover */
enum {
DHCP_FO_RESERVED,
DHCP_FO_POOLREQ,
DHCP_FO_POOLRESP,
DHCP_FO_BNDUPD,
DHCP_FO_BNDACK,
DHCP_FO_CONNECT,
DHCP_FO_CONNECTACK,
DHCP_FO_UPDREQ,
DHCP_FO_UPDDONE,
DHCP_FO_UPDREQALL,
DHCP_FO_STATE,
DHCP_FO_CONTACT,
DHCP_FO_DISCONNECT
All of them should have an 8 bit Integer Number. I was not able
to find out the numbers with reading the source code so I tried
them out. I was successful with the DHCP_FO-message-types:
The number is implied by the order in the enumeration
starting from 0, e.g. DHCP_FO_RESERVED is 0, DHCP_FO_POLREQ is 1,
and so on.
--
Regards,
Graham Bloice
|
