[Pidgin] #2825: Pidgin cannot reconnect after changing networks
Pidgin
trac at pidgin.im
Tue Nov 13 16:12:19 EST 2007
#2825: Pidgin cannot reconnect after changing networks
---------------------------+------------------------------------------------
Reporter: novakyu | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: pidgin (gtk) | Version: 2.1.1
Resolution: | Keywords:
Pending: 0 |
---------------------------+------------------------------------------------
Comment (by novakyu):
*bump*
The bug is still present in 2.2.2. And I can confirm that this is
unrelated to shutdown/hibernation.
Example: at my work, I have access both to wired internet and wireless
internet. I usually use the wired internet.
First, I connected to AIM and Google Talk through the wired internet
(pidgin is configured Not to autodetect my IP (why does it need this
feature anyway? For file transfers?), and configured to connect through a
SOCKS proxy).
Then, I disconnected the wired network and brought up my wireless device,
connecting to a different router that has a different public IP. Then
pidgin could not connect to either AIM or Google Talk (I tested my
internet connection with a web browser that uses the same SOCKS proxy).
And, this time, I didn't restart pidgin, but switched back to my wired
network (bringing down the wireless device), then pidgin can connect to
AIM and GoogleTalk just fine.
I believe the bug is related to whether pidgin gets the internet
connection through the same network device as when it was started up (and
originally made the connection?). But, why should it matter? I
specifically made pidgin use a SOCKS proxy (at localhost:8000) hoping
these hardware differences would be abstracted out, but it doesn't seem to
work, so far.
--
Ticket URL: <http://developer.pidgin.im/ticket/2825#comment:5>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list