On 08.04.2025 15:32 Uhr Gabx wrote:
Poi sono nati problemi con alcuni clients che utilizzano dispositivi
di traduzione da ipv6 a ipv4 e che ho cercato di risolvere come si
evince a partire da questo post
<20250403202001.41731d6f@ryz.dorfdsl.de>. Ma poi come suggerito da
noel <67f10d0c$1@news.ausics.net> sembra proprio essere a causa di un meccanismo di filtraggio.
Please write in English in news.admin.peering.
I also removed the test groups, such posts don't belong there.
I tried to tell you that your IPv6 setup is NOT working.
The connection is still being rejected.
As I told you, your INN isn't listening on IPv6 (check the ss -tl
output you posted). Unless you fix that, people with IPv6 only (even
with NAT64/DNS64) can't reach your server.
TLDR: If your hostname includes an AAAA (IPv6) record, it must be
functional.
This also applies for the smtp server.
--
kind regards
Marco
Send spam to
1744119165muell@stinkedores.dorfdsl.de
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)