tor man page doesn't mention isolating between socksports

If I set SocksPort 9050 and also SocksPort 9060, then if I understand correctly, Tor automatically isolates stream requests that come in on the different socksports.

But the man page doesn't mention this level of isolation. Maybe because there is no flag for influencing it?

It sure seems helpful to have a full sentence in the socksport intro stanza explaining what gets isolated by default, and what can be isolated by changing options. Or maybe there is a better place to put that than the socksport section?

changed milestone to %Tor: 0.4.0.x-final

Trac:
Parent Ticket: #22619 (moved)

added 040-backport actualpoints::0.1 component::core tor/tor doc milestone::Tor: 0.4.0.x-final parent::22619 points::0.1 priority::medium resolution::fixed reviewer::catalyst severity::normal status::closed type::defect labels

Here's the documentation:

    **SessionGroup=**__INT__;;
        If no other isolation rules would prevent it, allow streams
        on this port to share circuits with streams from every other
        port with the same session group.  (By default, streams received
        on different SocksPorts, TransPorts, etc are always isolated from one
        another. This option overrides that behavior.)

(It might not be obvious enough, but it is there. I'd love a patch to make it make more sense.)

Trac:
Milestone: N/A to Tor: unspecified

https://github.com/torproject/tor/pull/841

Trac:
Status: new to needs_review

Trac:
Reviewer: N/A to mikeperry

Remove Mike as reviewer, because he's overloaded. We'll work out what to do with these tickets in the weekly meeting.

Trac:
Reviewer: mikeperry to N/A

Trac:
Keywords: N/A deleted, doc added
Milestone: Tor: unspecified to Tor: 0.4.1.x-final

Trac:
Reviewer: N/A to catalyst

Replying to rl1987:

https://github.com/torproject/tor/pull/841 Thanks! Looks good!

Trac:
Status: needs_review to merge_ready

YES, Tor automatically isolates stream requests that come in on the different socksports.

well i was never able, to set the

SessionGroup=123

but this is another issue. Did you try anyway by assigning different SessionGroup per SocksPort?

Documentation fixes go in the alpha series.

Cherry-picked to 0.4.0 and merged forward.

Merged #29121 (moved), #30004 (moved) to 0.4.0, and #29926 (moved), #28806 (moved) to master, then merged forward.

Trac:
Actualpoints: N/A to 0.1
Milestone: Tor: 0.4.1.x-final to Tor: 0.4.0.x-final
Keywords: N/A deleted, 040-backport added
Points: N/A to 0.1

Trac:
Status: merge_ready to closed
Resolution: N/A to fixed

Replying to cypherpunks:

YES, Tor automatically isolates stream requests that come in on the different socksports.

well i was never able, to set the {{{ SessionGroup=123 }}} but this is another issue. Did you try anyway by assigning different SessionGroup per SocksPort?

I'm sorry, I'm not sure what you mean. Would you like to open another ticket? We try to handle one issue per ticket, otherwise they get lost.

Replying to teor:

Replying to cypherpunks:

YES, Tor automatically isolates stream requests that come in on the different socksports.

well i was never able, to set the {{{ SessionGroup=123 }}} but this is another issue. Did you try anyway by assigning different SessionGroup per SocksPort?

I'm sorry, I'm not sure what you mean. Would you like to open another ticket? We try to handle one issue per ticket, otherwise they get lost. Yes, the Problem discovered years ago, is described in this issue #22619 (moved)

Thanks, we will deal with it in that ticket.

Trac:
Parent: N/A to #22619 (moved)

closed

changed time estimate to 48m

added 48m of time spent

mentioned in issue #29926 (moved)

mentioned in issue #30004 (moved)

moved to tpo/core/tor#29121 (closed)