[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #12138 [Core Tor/Tor]: No IPv6 support when suggesting a bindaddr to a PT
#12138: No IPv6 support when suggesting a bindaddr to a PT
-------------------------------------+----------------------------------
Reporter: asn | Owner: (none)
Type: enhancement | Status: new
Priority: Medium | Milestone: Tor: unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-pt, tor-bridge ipv6 | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------+----------------------------------
Comment (by arma):
For context, on this one right now, if I say
{{{
ServerTransportListenAddr obfs4 0.0.0.0:5601
}}}
in my torrc file, then Tor will send this string as-is in an env var to
obfs4proxy:
{{{
Oct 14 03:42:27.000 [notice] sending
TOR_PT_SERVER_BINDADDR=obfs4-0.0.0.0:5601
}}}
and obfs4proxy will reply with
{{{
Oct 14 03:42:28.000 [notice] Registered server transport 'obfs4' at
'[::]:5601'
}}}
and then obfs4proxy will bind to both ipv4 and ipv6 locally.
So at least in this case, obfs4proxy is making its own choices about where
I should bind, even when I told it 0.0.0.0. Maybe this is a feature.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12138#comment:12>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs