debug about NetworkManager & resolv.conf being erased

Arnaud Abélard arnaud.abelard at univ-nantes.fr
Fri Feb 25 09:29:34 UTC 2005


Dan, you've been asking for debug infos about NetworkManager & the 
resolv.conf problem, so here it comes:

I've been trying to use NetworkManager to manage my ethernet and 
wireless devices on FC3. As it was previously said on the list, 
NetworkManager sometimes erase the current resolv.conf file with en 
empty one.

I did some tests:

NetworkManager will only do the dhcp request when detecting a new 
network connection. Which means that if you run NetworkManager when the 
network cable is already plugged on the NIC, NetworkManager will not do 
the dhcp request and will erase the resolv.conf file with an empty one.

I ran NetworkManager after booting. the network cable is already plugged 
on the NIC:

[root at gallilee ~]# NetworkManager --no-daemon
NetworkManager: starting...
NetworkManager: eth0: Driver support level is fully-supported
NetworkManager: nm_create_device_and_add_to_list(): adding device 'eth0' 
(wired)
NetworkManager: eth1: Driver support level is fully-supported
NetworkManager: nm_create_device_and_add_to_list(): adding device 'eth1' 
(wireless)
NetworkManager: running mainloop...
NetworkManager: nm_dbus_get_networks(): 
org.freedesktop.NetworkManagerInfo.NoNetworks raised There were are no 
wireless networks stored.
NetworkManager: AUTO: Best wired device = eth0, best wireless device = 
eth1 ()
NetworkManager:     SWITCH: best device changed
NetworkManager: nm_state_modification_monitor(): beginning activation 
for device 'eth0'
NetworkManager: nm_state_modification_monitor() activated device eth0

Result: resolv.conf has been erased.


Now, i stop NetworkManager and unplug the network cable then run 
NetworkManager once more before replugging the cable:

[root at gallilee ~]# NetworkManager --no-daemon
NetworkManager: starting...
NetworkManager: eth0: Driver support level is fully-supported
NetworkManager: nm_create_device_and_add_to_list(): adding device 'eth0' 
(wired)
NetworkManager: eth1: Driver support level is fully-supported
NetworkManager: nm_create_device_and_add_to_list(): adding device 'eth1' 
(wireless)
NetworkManager: running mainloop...
NetworkManager: nm_dbus_get_networks(): 
org.freedesktop.NetworkManagerInfo.NoNetworks raised There were are no 
wireless networks stored.
NetworkManager: AUTO: Best wired device = (null), best wireless device = 
eth1 ()
NetworkManager:     SWITCH: best device changed
NetworkManager: nm_state_modification_monitor(): beginning activation 
for device 'eth1'
NetworkManager: nm_device_activation_worker (eth1) started...
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: nm_device_activate_wireless(eth1): waiting for an access 
point.
NetworkManager: HAL signaled link state change for device eth0.
NetworkManager: AUTO: Best wired device = eth0, best wireless device = 
eth1 ()
NetworkManager:     SWITCH: best device changed
NetworkManager: nm_device_activation_cancel(eth1): cancelling...
NetworkManager: nm_device_activation_worker(eth1): activation canceled.
NetworkManager: Activation (eth1) IP configuration/DHCP returned = 0
NetworkManager: Activation (eth1) IP configuration/DHCP unsuccessful! 
Ending activation...
NetworkManager: Activation (eth1) ending thread.
NetworkManager: nm_device_activation_cancel(eth1): cancelled.
NetworkManager: nm_state_modification_monitor(): beginning activation 
for device 'eth0'
NetworkManager: nm_device_activation_worker (eth0) started...
NetworkManager: dhcp_interface_init: MAC address = 00:0f:1f:fe:9d:2f
NetworkManager: ClassID  = "Linux 2.6.10-1.766_FC3 i686"
ClientID = "1.0.15.1F.FE.9D.2F.00.00"
NetworkManager: Broadcasting DHCP_DISCOVER
NetworkManager: DHCP: Starting request loop
NetworkManager: DHCP: Sending request packet...
NetworkManager: DHCP: Sent request packet.
NetworkManager: DHCP: Waiting for reply...
NetworkManager: DHCP waiting for data, overall end_time = {1109323109s, 
138338us}
NetworkManager: DHCP waiting for data of minimum size 28, remaining 
timeout = {5s, 96347us}
NetworkManager: DHCP: Got some data to check for reply packet.
NetworkManager: DHCP: actual data length was 339
NetworkManager: debug_dump_dhcp_options: 7 options received:
NetworkManager: i=1  (subnetMask)  len=4   option = 255.255.255.0
NetworkManager: i=3  (routersOnSubnet)  len=4   option = xxxxxxxx
NetworkManager: i=6  (dns)  len=8   option = xxxxxxxx
NetworkManager: i=6  (dns)  len=8   option = xxxxxx
NetworkManager: i=15 (domainName)  len=31  option = "xxxxxxxxxxxxxx"
NetworkManager: i=51 (dhcpMessageType)  len=4   option = 43200
NetworkManager: i=53 (dhcpParamRequest)  len=1   option = 2
NetworkManager: i=54 (dhcpMsg)  len=4   option = xxxxxx
NetworkManager: dhcp_msg->yiaddr  = xxxxxx
NetworkManager: dhcp_msg->siaddr  = xxxxxxx
NetworkManager: dhcp_msg->giaddr  = 0.0.0.0
NetworkManager: dhcp_msg->sname   = ""
NetworkManager: Server Hardware Address   = 00.10.5A.DE.FF.B1
NetworkManager: broadcastAddr option is missing in DHCP server response. 
Assuming xxxxxx.255
NetworkManager: dhcpIPaddrLeaseTime = 43200 in DHCP server response.
NetworkManager: dhcpT1value is missing in DHCP server response. Assuming 
21600 sec
NetworkManager: dhcpT2value is missing in DHCP server response. Assuming 
37800 sec
NetworkManager: DHCP_OFFER received from  (xxxxxxxx)
NetworkManager: Broadcasting DHCP_REQUEST for xxxxxxxx
NetworkManager: DHCP: Starting request loop
NetworkManager: DHCP: Sending request packet...
NetworkManager: DHCP: Sent request packet.
NetworkManager: DHCP: Waiting for reply...
NetworkManager: DHCP waiting for data, overall end_time = {1109323110s, 
-600706us}
NetworkManager: DHCP waiting for data of minimum size 28, remaining 
timeout = {5s, 132041us}
NetworkManager: DHCP: Got some data to check for reply packet.
NetworkManager: DHCP: actual data length was 339
NetworkManager: debug_dump_dhcp_options: 10 options received:
NetworkManager: i=1  (subnetMask)  len=4   option = xxxxxx.0
NetworkManager: i=3  (routersOnSubnet)  len=4   option = xxxxxxxx
NetworkManager: i=6  (dns)  len=8   option = xxxxxxxx
NetworkManager: i=6  (dns)  len=8   option = xxxxxxx
NetworkManager: i=15 (domainName)  len=31  option = "xxxxxxxx"
NetworkManager: i=28 (broadcastAddr)  len=4   option = xxxxxx.255
NetworkManager: i=51 (dhcpMessageType)  len=4   option = 43200
NetworkManager: i=53 (dhcpParamRequest)  len=1   option = 5
NetworkManager: i=54 (dhcpMsg)  len=4   option = xxxxxxxxx
NetworkManager: i=58 (dhcpClassIdentifier)  len=4   option = 0
NetworkManager: i=59 (dhcpClientIdentifier)  len=4   option = 0
NetworkManager: dhcp_msg->yiaddr  = xxxxxxxx
NetworkManager: dhcp_msg->siaddr  = xxxxxxxx
NetworkManager: dhcp_msg->giaddr  = 0.0.0.0
NetworkManager: dhcp_msg->sname   = ""
NetworkManager: Server Hardware Address   = 00.10.5A.DE.FF.B1
NetworkManager: dhcpIPaddrLeaseTime = 43200 in DHCP server response.
NetworkManager: dhcpT1value is missing in DHCP server response. Assuming 
21600 sec
NetworkManager: dhcpT2value is missing in DHCP server response. Assuming 
37800 sec
NetworkManager: DHCP_ACK received from  (xxxxxxxx)
NetworkManager: Your IP address = xxxxxxxx
NetworkManager: : Adding nameserver: xxxxxxx
NetworkManager: : Adding nameserver: xxxxxxx
NetworkManager: : Adding domain search: xxxxxxx
NetworkManager: Activation (eth0) IP configuration/DHCP returned = 1
NetworkManager: Activation (eth0) IP configuration/DHCP successful!
NetworkManager: nm_state_modification_monitor() activated device eth0
NetworkManager: nm_device_activation_worker(eth0): device activated


Result: the resolv.conf file is properly filled.



-- 
Arnaud Abélard
Administrateur Systèmes et Réseaux
Faculté de Sciences et Techniques
Université de Nantes




More information about the fedora-devel-list mailing list