Bug 224795 - after vpn failure no automatic network reconfiguration
Summary: after vpn failure no automatic network reconfiguration
Status: RESOLVED UPSTREAM
Alias: None
Product: knetworkmanager
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
: 229177 249869 299179 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-01-29 17:46 UTC by Michi
Modified: 2012-05-02 02:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michi 2010-01-29 17:46:54 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Hi,

I am on a rather brittle network connection and as a consequence my vpn connections is breaking on a regular basis with just a short notification, and more often than not I simply don't absorb it, because networkmanager is restoring the original routing information and the network simply continues to work (for most things like browsing the web). So without realizing it I quite often loose my "stealth mode".

Now, I'd rather get a proper network failure in such a situation, meaning that networkmanager should not automatically try to reconnect. Maybe this could also become an option in the vpn preferences.

thx for your time
Mich;
Comment 1 Lamarque V. Souza 2011-03-18 23:51:07 UTC
This is a upstream issue:

https://bugzilla.gnome.org/show_bug.cgi?id=349151
Comment 2 Lamarque V. Souza 2011-03-18 23:52:20 UTC
*** Bug 249869 has been marked as a duplicate of this bug. ***
Comment 3 Michi 2011-04-09 18:07:06 UTC
(In reply to comment #1)
> This is a upstream issue:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=349151

I don't think that it is exactly what I meant. Although, reconnecting the VPN automatically would be a great thing, yes.
The other problem is that a broken VPN should not be replaced with a transparent connection. In such a case you think you're hiding but in real you're open as hell.
Comment 4 Lamarque V. Souza 2011-05-17 01:31:03 UTC
*** Bug 229177 has been marked as a duplicate of this bug. ***
Comment 5 Lamarque V. Souza 2011-09-10 18:21:50 UTC
The branch nm09 of Plasma NM adds an overlay to the system tray icon to indicate a VPN connection is active, so you can always know when VPN is activate. Do you think this suffices? If so then I will close this bug.

As for not reconfiguring a non-encrypted connection when VPN fails you should contact NetworkManager developers. NM's clients, like Plasma NM, cannot control that. Also several people who use VPN (me included) just need it to access a particular non-public network and not the entire Internet. If the VPN connection becomes unavailable I like the fact that I still can access the rest of the Internet.
Comment 6 Michi 2011-09-22 07:15:40 UTC
(In reply to comment #5)
> The branch nm09 of Plasma NM adds an overlay to the system tray icon to
> indicate a VPN connection is active, so you can always know when VPN is
> activate. Do you think this suffices? If so then I will close this bug.
> 
> As for not reconfiguring a non-encrypted connection when VPN fails you should
> contact NetworkManager developers. NM's clients, like Plasma NM, cannot control
> that. Also several people who use VPN (me included) just need it to access a
> particular non-public network and not the entire Internet. If the VPN
> connection becomes unavailable I like the fact that I still can access the rest
> of the Internet.

how about creating hooks to execute user scripts before and after a connection change?
Comment 7 Lamarque V. Souza 2011-09-22 15:53:32 UTC
(In reply to comment #6)
> (In reply to comment #5)
> > The branch nm09 of Plasma NM adds an overlay to the system tray icon to
> > indicate a VPN connection is active, so you can always know when VPN is
> > activate. Do you think this suffices? If so then I will close this bug.
> > 
> > As for not reconfiguring a non-encrypted connection when VPN fails you should
> > contact NetworkManager developers. NM's clients, like Plasma NM, cannot control
> > that. Also several people who use VPN (me included) just need it to access a
> > particular non-public network and not the entire Internet. If the VPN
> > connection becomes unavailable I like the fact that I still can access the rest
> > of the Internet.
> 
> how about creating hooks to execute user scripts before and after a connection
> change?

Already in my loooooooong TODO list (https://bugs.kde.org/show_bug.cgi?id=153990). There are yet too many things to implement but too few developers in Plasma NM. I am not being paid to work on Plasma NM and do some "freelance" work that I have to give priority since that work pays my bills.
Comment 8 Lamarque V. Souza 2011-10-29 20:33:22 UTC
Closing as upstream since auto reconnect for VPN connections must be implemented in NetworkManager, not Plasma NM.
Comment 9 Lamarque V. Souza 2012-05-01 18:10:59 UTC
*** Bug 299179 has been marked as a duplicate of this bug. ***
Comment 10 Lamarque V. Souza 2012-05-02 02:35:50 UTC
*** Bug 299179 has been marked as a duplicate of this bug. ***