pptp vpn regresses after feisty to gutsy upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
New
|
Undecided
|
Unassigned |
Bug Description
I have been successfully using network manager with a msft vpn at work for 6 or so months. Speed and reliability was consistent and good. After upgrading to Gutsy (gnome, no X or K), the connection works, but is very flaky. It prompts me to reenter my password a lot (even though I choose to save it in my keyring). When it does connect, it is only good for one app. THe seconf app that uses the tunnel will fail.
For example, i start the vpn connection, then ssh to a server at work. It works, and will stay connected for as long as I need it.
5 minutes after starting connection 1, I try to ssh or telnet to another (or the same server), that connection will say connection is refused. 1st conenction does not end, just cannot initiate a second terminal session.
This did not occur with this laptop and network under feisty. Ive looked in /var/log/daemon log, and the following output was noted.
Nov 2 20:49:13 e1505 pptp[7076]: anon log[ctrlp_
Nov 2 20:49:13 e1505 pptp[7076]: anon warn[ctrlp_
Nov 2 20:49:14 e1505 pptp[7074]: anon log[decaps_
Nov 2 20:49:18 e1505 NetworkManager: <info> VPN Activation (COMMERCE) Stage 4 of 4 (IP Config Get) reply received.
Nov 2 20:49:19 e1505 NetworkManager: <info> Clearing nscd hosts cache.
Nov 2 20:49:19 e1505 NetworkManager: <WARN> nm_spawn_process(): nm_spawn_
Nov 2 20:49:19 e1505 NetworkManager: <info> VPN Activation (COMMERCE) Stage 4 of 4 (IP Config Get) complete.
Nov 2 20:49:19 e1505 NetworkManager: <info> VPN Activation (COMMERCE) successful.
Nov 2 20:49:19 e1505 NetworkManager: <info> VPN service 'org.freedeskto
Nov 2 20:49:19 e1505 NetworkManager: <debug> [1194050959.227911] nm_dbus_
Nov 2 20:49:24 e1505 dhclient: DHCPREQUEST on eth1 to 192.168.0.100 port 67
Nov 2 20:49:24 e1505 dhclient: DHCPACK from 192.168.0.100
Nov 2 20:49:24 e1505 NetworkManager: <info> DHCP daemon state is now 3 (renew)
Note the nscd error and the pid 7074 and 7076 pptp errors. Is nscd needed for proper nm vpn funtionality? Did it work differently in feisty?
I think the problem has to do with dns.
I turned off option in NM -> Configure VPN -> PPP Options -> Exclusive device access, seemed to be better.
I tried with and without Configure VPN -> Routing -> Peer DNS through tunnel no change
services that try to resolve by dns fail, but by ip work.
telnetting to ip address works on multiple screens
rdp to name fails (used to work in feisty)
ssh fails do to RSA Key change (man in the middle attack), Think that related to getting different ip address from vpn service.
This is close to working.
One other issue is the password is never being save in teh keyring. It prompts me every time for username and password.