Bug 272855 - kopete fails to connect after network connection is switched to vpnc
Summary: kopete fails to connect after network connection is switched to vpnc
Status: RESOLVED NOT A BUG
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.0.80
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-09 14:40 UTC by Erik Boritsch
Modified: 2016-07-27 16:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Boritsch 2011-05-09 14:40:31 UTC
Version:           1.0.80 (using KDE 4.6.2) 
OS:                Linux

My university has wireless internet for students via cisco vpn, so in order to connect to the Internet you need to connect to an open wireless network and then create a vpnc connection.
While connecting itself works via networkmanager just fine, kopete is unable to connect to jabber (probably other protocols as well, didn't try) after I create such a vpnc connection if I was previously using it at home via normal wireless or ethernet. 
I need to restart kopete in order to make it connect. Other apps which rely on networkmanager status connect just fine.

Reproducible: Always

Steps to Reproduce:
1. connect to internet normally, e.g. wireless or ethernet. Kopete autoconnects all the protocols.
2. disconnect
3. connect to open wireless network which doesn't have internet connection
4. connect to vpn which is then default route and the internet connection
5. kopete fails to autoconnect (maybe fails to recognize the default route), restart of kopete needed
Comment 1 Alexey Neyman 2012-03-03 22:24:07 UTC
Same problem, KDE 4.8.00, Kubuntu 12.04 beta 1.
Comment 2 Alexey Neyman 2012-05-19 16:14:30 UTC
Found where my problem was: In KNetworkManager, the open VPN configuration. In IPv4 tab, select "Routes" from the drop list and check "Use only for resources on this connection" box.
Comment 3 Phil 2016-07-03 17:09:33 UTC
I am using Linux Mint 17.3 KDE.

Kernel: 3.19.0-32-generic i686 (32 bit gcc: 4.8.2)
Desktop: KDE Plasma 4.14.2 (Qt 4.8.6) Distro: Linux Mint 17.3 Rosa

If I am connected to my Internet provider (ISP), without using a VPN provider's connection, Kopete, KDE-Telepathy, Kmail, Jitsi, and others, etc... will work perfectly, and fast, and connect to all my messaging accounts (xmpp, sip).

As soon as I connect to a VPN server location using the openVPN protocol to a VPN provider, like "vpnbook", or "vpngate", they all stop working, and will not login to the various messenger accounts.

But, I can connect using "qTox" no problem?

I tried what  Alexey Neyman 2012-05-19 12:14:30 EDT suggested,
"Found where my problem was: In KNetworkManager, the open VPN configuration. In IPv4 tab, select "Routes" from the drop list and check "Use only for resources on this connection" box."

That works for the messaging clients, but then the VPN connection does not work properly, which makes that option useless. I tested this using "ipleak.net", before and after making the changes "Alexey" tried.

This is a problem that I would really like to know how to solve. Perhaps there is some other settings in the Network Manager, or the VPN Connection, or somewhere else, that would make the messaging clients work (connect) while using a VPN server connection? If so, could anyone tell me what they are, and how to implement them, please?

Thank you very much,
Phil
Comment 4 Pali Rohár 2016-07-27 16:52:26 UTC
Hi! This is not a problem with Kopete, but with your VPN software which does set routing correctly. I'm not goint to add any hacks into Kopete just because some VPN softwares are broken... I will close this bug as invalid Kopete project. Rather report problem to your VPN software.