Open Bug 777229 Opened 13 years ago Updated 2 years ago

Unable to reconnect after ssh tunnel crashed. SOCKS

Categories

(Core :: Networking: Proxy, defect, P5)

17 Branch
x86_64
All
defect

Tracking

()

UNCONFIRMED

People

(Reporter: jan.registracie, Unassigned)

Details

(Whiteboard: [necko-backlog])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Build ID: 20120713134347 Steps to reproduce: I was using the SSH tunnel via Putty as SOCKS proxy. Actual results: Connection to SSH server crashed. Expected results: After I re-established the SSH connection, firefox was unable to load webpages until I changed the port of the SSH tunnel. Same behavior in Windows 7 with Putty and Ubuntu 12.04 on Firefox 14.0.1
Did SSH crash or do you lost only the SSH connection ? My ssh tunnel (with Tunnelier) work fine after a connection loss with Seamonkey trunk.
I don't understand the question. If SSH connection is interrupted for example due to network issue, I'm unable to use the tunnel on same local port. Problem is also present in Firefox 15.
Version: 14 Branch → 15 Branch
2 major releases of Firefox, and bug is still not solved. What's worse, it's still not confirmed by anyone. I'm still unable to re-use the same port for proxy after ssh connection is closed due to network issue.
OS: Windows 7 → All
Version: 15 Branch → 17 Branch
Component: Untriaged → Networking
Product: Firefox → Core
Summary: Unable to reconnect after ssh tunnel crashed. → Unable to reconnect after ssh tunnel crashed. SOCKS
Whiteboard: [nekco-backlog]
Whiteboard: [nekco-backlog] → [necko-backlog]
Priority: -- → P1
Priority: P1 → P3

Bulk-downgrade of unassigned, >=3 years untouched DOM/Storage bug's priority.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5
Component: Networking → Networking: Proxy
You need to log in before you can comment on or make changes to this bug.