On Sat, 2007-10-06 at 10:21 -0400, Dan Williams wrote:
On Fri, 2007-10-05 at 13:17 -0500, Jason Martens wrote:
Hey all,
I'm using nm-6.5 in debian testing, and there is a problem with VPN
and dns. I connect with vpn, but after a while, the dns settings from
vpn are overwritten with the dns settings from the wireless network.
The DNS should not change while the vpn is connected, even if dhcp
renews it's lease. Make sense? Should I file a bug somewhere?
Can you get output from NM? It goes to wherever syslog will put it.
The DNS settings shouldn't change unless NM thinks that the VPN
connection has dropped. Also, I think debian uses resolvconf, and
something else may be poking resolvconf to overwrite the VPN settings.
NM logs would help determine whether it's NM rewriting /etc/resolv.conf,
or whether something else is the culprit through resolvconf.
Attached is the contents of my syslog starting from when I connected to
the wireless network, then initiated a vpnc connection, then later you
see the dhclient run, which I believe overwrites my resolv.conf. Also,
the resolvconf package is not installed on my system, fwiw.
Jason
Oct 12 12:05:22 mouse NetworkManager: info Device wlan0 activation
scheduled...
Oct 12 12:05:22 mouse NetworkManager: info VPN service
'org.freedesktop.NetworkManager.vpnc' signaled state change 4 - 5.
Oct 12 12:05:22 mouse NetworkManager: info VPN service
'org.freedesktop.NetworkManager.vpnc' signaled state change 5 - 6.
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) started...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0/wireless):
access point 'Northwestern' is encrypted, but NO valid key exists. New key
needed.
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) New wireless
user key requested for network 'Northwestern'.
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 2 of 5
(Device Configure) complete.
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) New wireless
user key for network 'Northwestern' received.
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 1 of 5
(Device Prepare) scheduled...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 1 of 5
(Device Prepare) started...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 2 of 5
(Device Configure) scheduled...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 1 of 5
(Device Prepare) complete.
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0) Stage 2 of 5
(Device Configure) starting...
Oct 12 12:05:22 mouse NetworkManager: info Activation (wlan0/wireless):
access point 'Northwestern' is encrypted, and a key exists. No new key needed.
Oct 12 12:05:22 mouse NetworkManager: info Error getting killswitch power:
org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Oct 12 12:05:23 mouse NetworkManager: info SUP: sending command
'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'
Oct 12 12:05:23 mouse kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was 'OK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command 'AP_SCAN 1'
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was 'OK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command
'ADD_NETWORK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was '0'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command 'SET_NETWORK
0 ssid 4e6f7274687765737465726e'
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was 'OK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command 'SET_NETWORK
0 proto WPA2'
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was 'OK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command 'SET_NETWORK
0 key_mgmt WPA-EAP'
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was 'OK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command 'SET_NETWORK
0 eap PEAP'
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was 'OK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command 'SET_NETWORK
0 identity username'
Oct 12 12:05:25 mouse NetworkManager: info SUP: response was 'OK'
Oct 12 12:05:25 mouse NetworkManager: info SUP: sending command 'SET_NETWORK
0 password password'
Oct 12
