From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-4322.protonmail.ch (mail-4322.protonmail.ch [185.70.43.22]) by passt.top (Postfix) with ESMTPS id D0C715A026D for ; Sun, 28 May 2023 12:13:03 +0200 (CEST) Date: Sun, 28 May 2023 10:12:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pm.me; s=protonmail3; t=1685268783; x=1685527983; bh=+Q2OU8YLiuBLIGfWYwkxr24nKMFNewYH6yI+ii/GhgA=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=GWsYRl0FGrK1MUyUySxXcLL1CGUdImMaBWyPkxzNkO4BlMuLVmle0c9e6bwTzOYvp w3shX2TRM2KBjwFftayqF2SO0xin9ygL0c/y5CWUvnXCp9diljhzd33jDLwTyv//q6 ZbSsz+k9oX1skVBnwqDnnmuFjRJNJ0cQgelkyfqyOvGbv5mYyyFSxvLPksIGLsxbvD SE2h8i3mhgstbLPyVKQ3ZqvGwd0RZO9HLWOY67MqEiWypUu/55zqqw5paSEDggX4Zy 1Q6xZ2SMhfrA85NUob4NPEaeQOwrBhdKvF4OJ9kO2dGR6ngtPZ6jj3MAoNNKXHelZ2 TJunWYWAWkh2g== To: David Gibson From: Juan Orti Subject: Re: IPv6 UDP not working Message-ID: In-Reply-To: References: Feedback-ID: 45474451:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: YCR5ZFLWBPCJIJZKUEVPXR5BSH64WUCP X-Message-ID-Hash: YCR5ZFLWBPCJIJZKUEVPXR5BSH64WUCP X-MailFrom: jorti@pm.me X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "passt-user@passt.top" X-Mailman-Version: 3.3.8 Precedence: list List-Id: "For users: support, questions and answers" Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: ------- Original Message ------- El domingo, 28 de mayo de 2023 a las 07:23, David Gibson escribi=C3=B3: >=20 > So, we have some special cases related to port 53 - aimed at allowing > the container to contact a nameserver outside. I don't think we > thought much about the case of a DNS server inside the container. So > my first guess would be that those special cases have an error that's > interfering with your use case. If it's possible to try running your > server on a port other than 53 temporarily that would be interesting > to try. Thanks for the suggestion. I've tried moving the listening port of this ser= vice (AdguardHome) to 54 and surprisingly it was still not working on UDPv6= . Testing with a different DNS service (unbound) works fine even when using= port 53. So this is a problem with this specific service. I don't understand why it's not working, as the service listens on the :: a= ddress. Maybe it's using a socket option that it's causing this? I need to = investigate this further. # netstat -putan Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State = PID/Program name =20 tcp 0 0 :::3003 :::* LISTEN = 2/AdGuardHome tcp 0 0 :::54 :::* LISTEN = 2/AdGuardHome udp 0 0 :::54 :::* = 2/AdGuardHome # cat /proc/net/udp6=20 sl local_address remote_address = st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref p= ointer drops 4718: 00000000000000000000000000000000:0036 000000000000000000000000000000= 00:0000 07 00000000:00000000 00:00000000 00000000 0 0 38510801 2= 0000000073476783 0 >=20 > We also attempt to auto-configure those cases from the host's > resolv.conf, so if you could share that it might shed some extra > light. resolv.conf looks correct: # Host: nameserver 192.168.7.1 nameserver fddc:f797:78ef:70::1 search lan # Container:=20 search lan nameserver 192.168.7.1 Thank you.