Since the upgrade from 6.12.3 to 6.12.5, the following services do not listen on the configured (public) IPv6 address:
- SSH
- SMB
- http (Unraid web interface)
I made the following observations:
- ping to the Unraid configured IPv6 is working
- The services mentioned above are not answering to connection requests via the IPv6. IPv4 working fine
-
The file /etc/samba/smb-names.conf contains the following entry:
interfaces = 192.168.2.2/24 0 127.0.0.1 ::1
--> IPv6 is missing -
Adding the following entry to the "Samba extra configuration:" enables IPv6 connections to Samba:
- interfaces = 192.168.2.2/24 0 127.0.0.1 ::1 2a01:124f:acdf:31b1::100/64
-
At "Settings --> Management Access" I see the following:
-
Local access URLs:
- http://[2a01:124f:acdf:31b1:]:0100/ redirects to https://[2a01:124f:acdf:31b1:]:0100/
- The above is obviously wrong. It should be http://[2a01:124f:acdf:31b1::0100]/
-
Local access URLs:
Listing the ports that the server listens on gives the following:
root@zentrale:/boot/config# ss -tulpn | grep LISTEN tcp LISTEN 0 50 127.0.0.1:139 0.0.0.0:* users:(("smbd",pid=18417,fd=35)) tcp LISTEN 0 50 127.0.0.1:445 0.0.0.0:* users:(("smbd",pid=18417,fd=34)) tcp LISTEN 0 1 0.0.0.0:5700 0.0.0.0:* users:(("qemu-system-x86",pid=20299,fd=42)) tcp LISTEN 0 1 0.0.0.0:5900 0.0.0.0:* users:(("qemu-system-x86",pid=20299,fd=41)) tcp LISTEN 0 5 0.0.0.0%br0:5355 0.0.0.0:* users:(("wsdd2",pid=18430,fd=12)) tcp LISTEN 0 5 0.0.0.0%br0:3702 0.0.0.0:* users:(("wsdd2",pid=18430,fd=8)) tcp LISTEN 0 5 0.0.0.0:3551 0.0.0.0:* users:(("apcupsd",pid=6374,fd=5)) tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=28391,fd=3)) tcp LISTEN 0 511 0.0.0.0:80 0.0.0.0:* users:(("nginx",pid=12508,fd=8),("nginx",pid=8709,fd=8)) tcp LISTEN 0 511 0.0.0.0:443 0.0.0.0:* users:(("nginx",pid=12508,fd=9),("nginx",pid=8709,fd=9)) tcp LISTEN 0 1000 127.0.0.1:16509 0.0.0.0:* users:(("libvirtd",pid=19904,fd=14)) tcp LISTEN 0 50 192.168.2.2:445 0.0.0.0:* users:(("smbd",pid=18417,fd=36)) tcp LISTEN 0 50 192.168.2.2:139 0.0.0.0:* users:(("smbd",pid=18417,fd=37)) tcp LISTEN 0 32 192.168.122.1:53 0.0.0.0:* users:(("dnsmasq",pid=20108,fd=6)) tcp LISTEN 0 5 [::]%br0:5355 [::]:* users:(("wsdd2",pid=18430,fd=13)) tcp LISTEN 0 5 [::]%br0:3702 [::]:* users:(("wsdd2",pid=18430,fd=9)) tcp LISTEN 0 50 [::1]:445 [::]:* users:(("smbd",pid=18417,fd=32)) tcp LISTEN 0 511 [::1]:443 [::]:* users:(("nginx",pid=12508,fd=11),("nginx",pid=8709,fd=11)) tcp LISTEN 0 50 [::1]:139 [::]:* users:(("smbd",pid=18417,fd=33)) tcp LISTEN 0 511 [::1]:80 [::]:* users:(("nginx",pid=12508,fd=10),("nginx",pid=8709,fd=10)) tcp LISTEN 0 50 [2a01:124f:acdf:31b1::100]:139 [::]:* users:(("smbd",pid=18417,fd=31)) tcp LISTEN 0 50 [2a01:124f:acdf:31b1::100]:445 [::]:* users:(("smbd",pid=18417,fd=30))
You can see in this listing, that no service of Unraid is listening on IPv6 addresses, but Samba, that I manually added to listen at the configured IPv6 address.
I would appreciate to get this fixed ASAP, as I heavily relay on IPv6 in my network.
Thanks
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.