Pidgin requires restart after connecting to VPN (vpnc)
Bug #362944 reported by
luchon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Pidgin |
New
|
Unknown
|
|||
ntrack |
Triaged
|
Wishlist
|
Unassigned | ||
pidgin (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: network-
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?
affects: | network-manager-openvpn (Ubuntu) → network-manager-vpnc (Ubuntu) |
Changed in pidgin: | |
status: | Unknown → New |
To post a comment you must log in.
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).