At present, DHCP debugging is enabled via exporting "CONNMAN_DHCP_DEBUG" in
the environment prior to launching Connection Manager and yields debugging
information such as:
daemon.info connmand[388]: DHCP: switch listening mode (0 ==> 1)
daemon.info connmand[388]: DHCP: sending DHCP discover request
daemon.info connmand[388]: DHCP: received DHCP packet (current state 0)
daemon.info connmand[388]: DHCP: start request (retries 0)
daemon.info connmand[388]: DHCP: switch listening mode (1 ==> 1)
daemon.info connmand[388]: DHCP: sending DHCP select request
daemon.info connmand[388]: DHCP: received DHCP packet (current state 1)
daemon.info connmand[388]: DHCP: switch listening mode (1 ==> 0)
daemon.info connmand[388]: DHCP: start bound
daemon.info connmand[388]: DHCP: processed DHCP packet (new state 2)
daemon.info connmand[388]: DHCP: switch listening mode (0 ==> 0)
daemon.info connmand[388]: DHCP: sending DHCP release request
daemon.info connmand[388]: DHCP: switch listening mode (0 ==> 0)
daemon.info connmand[401]: DHCP: switch listening mode (0 ==> 1)
daemon.info connmand[401]: DHCP: sending DHCP discover request
daemon.info connmand[401]: DHCP: sending DHCP discover request
daemon.info connmand[401]: DHCP: sending DHCP discover request
daemon.info connmand[401]: DHCP: received DHCP packet (current state 0)
daemon.info connmand[401]: DHCP: start request (retries 0)
daemon.info connmand[401]: DHCP: switch listening mode (1 ==> 1)
daemon.info connmand[401]: DHCP: sending DHCP select request
daemon.info connmand[401]: DHCP: received DHCP packet (current state 1)
daemon.info connmand[401]: DHCP: switch listening mode (1 ==> 0)
daemon.info connmand[401]: DHCP: start bound
daemon.info connmand[401]: DHCP: processed DHCP packet (new state 2)
Three questions that arise in debugging some DHCP issues on one of my test
networks:
1) Why is DHCP debugging not enabled with '-d "dhcp"' or some such? Does
'-d' work in the way it is documented in help for any subsystem?
2) Is there any reason that DHCP information is not always logged by
default?
3) Is there any reason that logged DHCP information does not contain more
detail such as that logged by dhclient3?
dhclient: Listening on LPF/eth0/00:0c:29:26:de:fd
dhclient: Sending on LPF/eth0/00:0c:29:26:de:fd
dhclient: Sending on Socket/fallback
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
dhclient: DHCPOFFER of 192.168.1.133 from 192.168.1.1
dhclient: DHCPREQUEST of 192.168.1.133 on eth0 to 255.255.255.255 port
67
dhclient: DHCPACK of 192.168.1.133 from 192.168.1.1
dhclient: bound to 192.168.1.133 -- renewal in 36658 seconds.
dhclient: DHCPREQUEST of 192.168.1.133 on eth0 to 192.168.1.1 port 67
dhclient: DHCPACK of 192.168.1.133 from 192.168.1.1
dhclient: bound to 192.168.1.133 -- renewal in 39981 seconds.
Thanks,
Grant
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
