On 09 Feb (11:55:12), tschador@posteo.de wrote:

Tonight my Tor relay on Raspberry Pi (buster) was upgraded from 0.4.4.6-1~bpo10+1 to 0.4.5.5-rc-1~bpo10+1 automaticly, but failed to start:

--- [notice] Opening OR listener on 0.0.0.0:587 [notice] Opened OR listener connection (ready) on 0.0.0.0:587 [notice] Opening OR listener on [::]:587 [warn] Socket creation failed: Address family not supported by protocol [notice] Opening Directory listener on 0.0.0.0:995 [notice] Closing partially-constructed OR listener connection (ready) on 0.0.0.0:587 [notice] Closing partially-constructed Directory listener connection (ready) on 0.0.0.0:995 ---

Until then there was no change in my torrc:

ORPort 587 DIRPORT 995

Oh wow, interesting, so your Pi doesn't support IPv6 for some reasons and it failed to start with this config. I have opened: https://gitlab.torproject.org/tpo/core/tor/-/issues/40283 In 0.4.5.x tor, things have changed where tor will try to auto discover an IPv6 and automatically bind to it if only "ORPort <PORT>" is used. In other words, it now binds to 0.0.0.0 and [::] by default. It then publish any discovered _usable_ and _reachable_ IPv4/IPv6. If it doesn't find any IPv6, it will still listen but won't publish any IPv6.

It seems the value [address:] is no longer optional if you're not IPv6 ready [1]:

ORPort [address:]PORT|auto [flags] DirPort [address:]PORT|auto [flags]

So I have to change my torrc to:

ORPort 0.0.0.0:587 DIRPORT 0.0.0.0:995

Another option would have been to add the "IPv4Only" flag to the ORPort line and should have done it for you. Cheers! David -- YrY9JHvSOJpDfyKS5AyL8h/BjZ/SQEkh00q9ek+1BXk=