Re: [tor-relays] Tor 0.4.5.6 and missing IPv6

2021-03-24 Thread David Goulet 
On 11 Mar (19:16:50), s7r wrote:
> On 3/10/2021 5:31 PM, William Kane wrote:
> > Hi,
> > 
> > manually specify IP and port, and set the IPv4Only flag for both
> > ORPort and DirPort.
> > 
> > Reference: https://2019.www.torproject.org/docs/tor-manual.html.en
> > 
> > William
> > 
> 
> I think he has a dynamic IP address which is why, according to pasted torrc,
> the used config is:
> 
> `Address Address my.dynamic.dns.url`
> 
> This is a perfectly normal and accepted use-case. I think this is why it
> complained about not being able to find an IPv6 address, because it was
> resolving a hostname instead of parsing an IP address and most probably it
> did not find any  record.
> 
> Anyway, IPv4Only in the ORPort line is the right config for this use-case
> (where you don't have any IPv6 thus don't want to use IPv6 auto-discovery),
> as David said, most annoying bugs regarding IPv6 auto-discovery were fixed.
> So the suggestion to use IPv4Only in torrc line is not a workaround a bug or
> misbehavior or something, it is a corrected configuration parameter (as per
> manual instructs) and should stay like this even in 0.4.5.7 of course.
> 
> I only find this log message unclear:
> 
> [notice] Unable to find IPv6 address for ORPort 9001. You might want to
> specify IPv6Only to it or set an explicit address or set Address.
> 
> I think it means "... You might want to specify *IPv4Only* to it or set it
> to an explicit address or set configure Address."

Oops.. this fell off my radar, mis-placed in my Inbox :(

Yes but also this was fixed in 0.4.5.7 where we flip the "IPv*Only" option so
in that case it should have read "IPv4Only".

David

-- 
XV9G5n2Z8S7JqTM4GHU9eKrLUI9POwB5m0+OohPUEsM=


signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Active MetricsPort logs "Address already in use"

2021-03-24 Thread David Goulet 
On 23 Mar (23:18:32), Alexander Dietrich wrote:
> > David Goulet  hat am 22.03.2021 13:24 geschrieben:
> > 
> > > Sending GET requests to the address returns empty responses.
> > 
> > You should be able to get the metrics with a GET on /metrics.
> > 
> > Let us know if this works for you!
> 
> The empty 200 response is returned from "/metrics", I guess due to the 
> "address already in use" problem. Requests to "/" return a 404.

At the moment, the only metrics exported are those of onion services. We still
need to implement exporting relay and client metrics.

If you set an onion service, you should get more stuff :) else we have a bug!

Cheers!
David

-- 
XV9G5n2Z8S7JqTM4GHU9eKrLUI9POwB5m0+OohPUEsM=


signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Failed upgrade

2021-03-24 Thread s7r 

Hello,

You have some wrong torrc options.

They used to work because we didn't had a clear logic, there has been a 
lot of improvements made since IPv6 Address auto discovery was implemented.


Please see my corrections in line as well as explanations. Hope they 
make sense.


r1610091651 wrote:

Hi

FYI

So I've upgraded tor package from 0.4.4.6 to 0.4.5.7-1~xenial+1. No 
other changes.

Yet on startup tor is complaining about mis-configuration:

Mar 23 20:55:02.928 [notice] Read configuration file 
"/usr/share/tor/tor-service-defaults-torrc".

Mar 23 20:55:02.929 [notice] Read configuration file "/etc/tor/torrc".
Mar 23 20:55:02.932 [warn] Configuration port ORPort 9443 superseded by 
ORPort :9443
Mar 23 20:55:02.932 [warn] We are listening on an ORPort, but not 
advertising any ORPorts. This will keep us from building a router 
descriptor, and make us impossible to use.
Mar 23 20:55:02.932 [warn] Failed to parse/validate config: 
Misconfigured server ports

Mar 23 20:55:02.932 [err] Reading config failed--see warnings above.

config:
ORPort :9443 NoAdvertise


This is ok, you configured and explicit IP address.


ORPort 9443 NoListen IPv4Only


This is not ok, the NoAdvertise ORPort is explicit  but this 
is wildcard to all interfaces.


IPv4Only either you use it for both NoListen and NoAdvertise ORPort 
either you don't use it at all since you use AddressDisableIPv6.


This line should be:
ORPort :9443 NoListen


AddressDisableIPv6 1


This is OK. Or you can use IPv4Only for both ORPort entries and it will 
have the same effect.



OutboundBindAddress 


This is also OK.



This config is according to spec and worked with 4.4.6.

Seems to be related to thes issues, except for me it's blocking: tor 
fails to start.
https://gitlab.torproject.org/tpo/core/tor/-/issues/40300 

https://gitlab.torproject.org/tpo/core/tor/-/issues/40302 



I had to add 0.0.0.0 as ip to make tor start, although that's not 
documented...

ORPort :9443 NoAdvertise
ORPort 0.0.0.0:9443  NoListen IPv4Only



Please try with my example and remove 0.0.0.0 as it's not our scope, we 
are trying to configure explicit binding IP addresses. Let me know if 
this works for you -- it should be a correct configuration.




OpenPGP_signature
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays