Hi,
I've recently upgraded to Tor 0.4.5.6. Everything seems to work fine, but in the notices_log file I have a lot of these lines:
[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 don't have IPv6, and any line mentioning IPv6 in the torrc file is commented. Is there anythng I need to do in order to get rid of those notices, or can I just let them be?
Thanks, Marco
Marco Predicatori wrote:
Hi,
I've recently upgraded to Tor 0.4.5.6. Everything seems to work fine, but in the notices_log file I have a lot of these lines:
[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 don't have IPv6, and any line mentioning IPv6 in the torrc file is commented. Is there anythng I need to do in order to get rid of those notices, or can I just let them be?
Thanks, Marco
Hi Marco,
Thanks for running a relay / bridge.
Please paste your entire torrc (without any sensitive data of course). We have some slight misbehavior for the IPv6 auto discovery.
Along with the torrc please state if you have IPv6 of any kind to that box and if yes which kind (tunnel, native, etc.).
Also, you might use `ORPort 9001 IPv4Only` in torrc without any other modifications besides this and see if the error still occurs.
s7r wrote on 3/9/21 3:12 PM:
Please paste your entire torrc (without any sensitive data of course). We have some slight misbehavior for the IPv6 auto discovery.
Here: https://pastebin.com/9VEZD9Zw
Along with the torrc please state if you have IPv6 of any kind to that box and if yes which kind (tunnel, native, etc.).
No IPv6 anywhere around.
Also, you might use `ORPort 9001 IPv4Only` in torrc without any other modifications besides this and see if the error still occurs.
This did the trick! No messages in the last 5 hours, since when I updated torrc and restarted Tor.
Thanks! Marco
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
2021-03-09 21:53 GMT, Marco Predicatori marco@predicatori.it:
s7r wrote on 3/9/21 3:12 PM:
Please paste your entire torrc (without any sensitive data of course). We have some slight misbehavior for the IPv6 auto discovery.
Here: https://pastebin.com/9VEZD9Zw
Along with the torrc please state if you have IPv6 of any kind to that box and if yes which kind (tunnel, native, etc.).
No IPv6 anywhere around.
Also, you might use `ORPort 9001 IPv4Only` in torrc without any other modifications besides this and see if the error still occurs.
This did the trick! No messages in the last 5 hours, since when I updated torrc and restarted Tor.
Thanks! Marco
-- https://metrics.torproject.org/rs.html#details/A4E74410D83705EEFF24BC265DE2B...
On 10 Mar (15:31:37), 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
Yes good advice.
Sorry about this. We believe we fixed most of the issues in 0.4.5 regarding IPv6 address discovery and so the next stable release 0.4.5.7 (next week around Tuesday) will have those and thus should be better with address detection.
Thanks for reporting and sticking with us with these very annoying bugs.
Cheers! David
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 AAAA 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."
Is this suggestion correct David? I mean, it complains about not being able to find an IPv6 address (so most probably there is none to find) but it requires you to specify IPv6Only -- impossible, since you don't have any IPv6. I don't think it makes sense, or are my thoughts too mixed up? If yes, could you do a fast PR since it's something trivial or should I file a ticket on gitlab? This should make it in 0.4.5.7 if yes of course.
@s7r:
You are right, I did not read his torrc.
Relays on randomly rotated (most ISP's have adopted a 24 hour lease model) IP addresses are disruptive to long term connections anyway (this is partially mitigated by not assigning them the stable flag, but still) so in my opinion OP should just rent a KVM machine for ~10 bucks with two static IPv4 and IPv6 addresses, it would greatly increase the value of his tor relay if he also pays attention to network diversity while choosing a DC.
Just my opinion :p
William
2021-03-11 17:16 GMT, s7r s7r@sky-ip.org:
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 AAAA 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."
Is this suggestion correct David? I mean, it complains about not being able to find an IPv6 address (so most probably there is none to find) but it requires you to specify IPv6Only -- impossible, since you don't have any IPv6. I don't think it makes sense, or are my thoughts too mixed up? If yes, could you do a fast PR since it's something trivial or should I file a ticket on gitlab? This should make it in 0.4.5.7 if yes of course.
William Kane wrote on 3/11/21 6:36 PM:
@s7r:
You are right, I did not read his torrc.
Relays on randomly rotated (most ISP's have adopted a 24 hour lease model) IP addresses are disruptive to long term connections anyway (this is partially mitigated by not assigning them the stable flag,
I need dynamic dns because this particular node is hosted at my home dsl connection. The IP usually lasts several weeks or months. I have the stable flag.
but still) so in my opinion OP should just rent a KVM machine for ~10 bucks with two static IPv4 and IPv6 addresses,
That's obviously a good idea, but I like to keep an eye on my hardware too. And I don't mind mixing my own traffic with that of a middle node.
Bye, Marco
s7r wrote on 3/11/21 6:16 PM:
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."
Yes, a clearer message in the logs would have greatly helped to point me towards the obvious, easy solution.
Thanks for all your work on Tor.
Bye, Marco
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 AAAA 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
tor-relays@lists.torproject.org
-
David Goulet -
Marco Predicatori -
s7r -
William Kane