Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #444
Closed (moved) (moved)
Open
Issue created Jun 03, 2007 by weasel (Peter Palfrader)@weasel

connecting to a hidden service port that does not exist kills existing connections

This is either a bug in the hidden service, or in the client code, I don't know which.

Symptoms: If you have a connection established to a hidden service on some port, and then open a new connection to a port that it does not listen on your already existing connection is torn down.

e.g.: socat TCP4-LISTEN:4242,fork SOCKS4A:localhost:37lnq2veifl4kar7.onion:6667,socksport=9050 & telnet to localhost 4242, log on to IRC.

socat TCP4-LISTEN:4343,fork SOCKS4A:localhost:37lnq2veifl4kar7.onion:80,socksport=9050 telnet localhost 4343 -> irc connection dies.

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking