KNetworkManager with network-manager-vpnc - no configuration in gutsy

Bug #187549 reported by epimeth on 2008-01-31
2
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Undecided
Unassigned

Bug Description

pretty fresh install of gutsy, fully updated with all repos.

I installed network-manager-vpnc so I can connect to the vpn at my office.
After installation, KNetworkManager has a new menu item, VPN Connections (yay!)
unfortunately, the only submenu item available is "Disconnect VPN", and it is grayed out.

I looked at some similar bugs, but none seemed to apply to this exact situation. Something that seemed to come up often was all sorts of 'nm-' commands. The only one I have is nm-tool, which only reports status information.

A quick response is appreciated!

epimeth (roy-roomsinny) wrote :

All right... so I broke and *did* install network-manager-gnome...
I set up a vpn through nm-applet -- now I know how to create one manually... why is there no documentation? :-( --
When I click on the connection, I get something along the lines of "cannot connect to VPN" without even being asked for a group password.
After I click OK, KNetworkManager has no options, wireless or wired, and says something along the lines of "Network Manager is not running", but I stay connected as ifconfig retains its settings, as does resolvconf. The only way I could find to restart the network manager (as I could find *very* little documentation) was to restart the computer, though I haven't tried to find and restart the network manager daemon / service / whatever and I'm sure that would work as well

Luka Renko (lure) wrote :

knetworkmanager 0.2.2 is now available in Hardy and have some fixes for VPN handling.
Can you check if you can reproduce this with up-to-date Hardy?

Also, you need to install network-manager-vpnc package and configure it in Options... -> Configure ... -> VPN Connections...

Changed in knetworkmanager:
status: New → Incomplete
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in knetworkmanager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers