Hi, None of my VPN profiles take over the default route. It's just a case of routing some RFC1918 (10.x, 172.16-31.x etc. etc.) via the VPN tunnel. Nothing else is affected. Pidgin sould never go thro the VPN tunnel atleast.
-- Rikki ----- Original Message ----- From: "Phil Hannent" <p...@hannent.co.uk> To: "Richard Allen" <r...@ra.is> Cc: "Pidgin Support List" <support@pidgin.im> Sent: Tuesday, 16 April, 2013 1:37:30 PM Subject: Re: pidgin and VPN issues. Hi, Do you actually need Pidgins traffic to do down the VPN? Because you can stop the VPN from becoming the default route for all traffic and only set it to be the route for your companies servers. If that is the case you can change the IPv4 Settings for the VPN and press the "Routes..." button. Tick the box "Use this connection only for resources on its network" then add the network address range of your company network "10.0.0.0" for example. Regards Phil Hannent On 16 April 2013 14:32, Richard Allen < r...@ra.is > wrote: Hello all, I'm using pidgin on Fedora 18 (This was also an issue in 17). My work requires me to fire up multiple VPN profiles each day. Normally this is fine. However when disengaging the VPN pidgin tends to lock up. This happens both with Cisco compatible (vpnc) profiles and also Anyconnect profiles. I use network manager for all VPN needs. When pidgin is frozen, there is no indication in the GUI (i.e. I dont notice anything) and pidgin is unkillable. I have to use kill -9 to stop it. Is this a known issue or are there any workarounds? Thanks in advance. -- Rikki _______________________________________________ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support _______________________________________________ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
