Pidgin requires restart after connecting to VPN (vpnc)

Bug #362944 reported by luchon on 2009-04-17
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)

Bug Description

Binary package hint: network-manager-openvpn

After connecting to VPN (VPNC -> Cisco VPN), Pidgin fails to deliver (send and receive) messages. There is no errors of any sort. It appears that sent message went out, but there is no reply, and there are no new incoming messages.
Once Pidgin is bounced (quit/start) - messages flow normal, however, messages sent before the bounce were not delivered.
Another way to make messages flow without the restart is Disable/Enable pidgin accounts.

Did anyone else encountered this problem, and is there a work around?

Peter Meiser (meiser79) on 2009-10-06
affects: network-manager-openvpn (Ubuntu) → network-manager-vpnc (Ubuntu)
Michael (michaeljt) wrote :

I fear that this is not easily fixable. AFAICS, you log on to an IRC server using your IP address, and when you connect to a VPN, your IP address changes. I think that the best Pidgin could do here would be to detect the routing change and reconnect automatically. (Notes: 1) I am another user, not a maintainer. 2) This should probably be made a Pidgin wishlist item).

Alexander Sack (asac) wrote :

i am currently working on a simple lib that will allow reacting on online/offline/route changes in a connection-manager agnostic fashion ... not yet ready, but first code is here:

its a spare time project, so i think lucid is realistic for this.

Alexander Sack (asac) wrote :

to test if it works you could build it and run make check ... and then run the test_monitor testcase ... which should spit out when there are connect/disconnect/route changes .... if you want that would be great to test already.

Changed in ntrack:
status: New → Triaged
importance: Undecided → Wishlist
affects: network-manager-vpnc (Ubuntu) → pidgin (Ubuntu)
Changed in pidgin (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Andreas Kern (kerna) wrote :

maybe it's very easy to fix
the network-manager just has to announce the offline mode (vie D-Bus), which triggers pidgin to disconnect
when the network-manager finally established the new network connection (via vpn), he switches back to online mode and pidgin does the same

firefox already does this, so it should be reported to the network manager

CuteChaps (sh-senthilkumar) wrote :

yes ... I too experience the same kind of issue looking for good solution at the earliest,,,,,,

Alexander Sack (asac) wrote :

submitted patch for ntrack support to pidgin upstream tracker:

Changed in pidgin:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.