Mr.win7

Hi @JorgeB and @bonienl, could you please share us the progress or plan about the issue? Though we can manually flush the IPv6 address, I still want the Unraid to flush it automatically.

Thanks for your command! at least I don't need to restart.

Thanks JorgeB and bonienl! I've suffered from the issue for a really long time. The behavior about IPv6 was changed for several times and it become worse each time(sigh

Hi JorgeB, do you have any status can be shared about the progress?

tower-diagnostics-20240229-0911.zip

Would you please have a look on my newest update? The issue still exists.

repro it on 6.12.8. The issue still happens. tower-diagnostics-20240229-0911.zip

Updating. Let me try to repro it tomorrow at my local time.

Our ISP will assign a new ipv6 prefix for the home network periodically, and also do it when the router restart. Every time the prefix changes, From dhcpcd log, Unraid will set the route to right value but won't update its own ip. I have to restart the unraid server as a workaround. Any approach to prevent it? I'm using 6.12.6. I tried both SLAAC and DHCPv6 for my router and none of it works for unraid, while the other systems (Windows and Debian) works well. The diagnostics is attached. tower-diagnostics-20240228-2308.zip

Anybody know about that?

Recently I found that I can access the docker service via ipv6 but the webgui and smb can't. We found for docker, it listens the port like: tcp6 0 0 :::30000 :::* LISTEN 20925/docker-proxy But for webgui, it behaves like: tcp6 0 0 1234:5678:90ab:cdef:8888 :::* LISTEN 5198/nginx: master But my network environment is dynamic and the ipv6 address has changed after server started for a while. How could I set the smbd and nginx to listen all the ipv6 addresses like docker?

From 8.22 to now the problem didn't happen again. Seems 12.4 fix the problem. Thank you for your work!

Sure, will updating and have a try.

Thank you @ljm42 But IPv6 is important for me. I've run the fix common problems plugin and it didn't show any useful suggestion about this. Here is my syslog. I think the problem is related to the nginx. Could you please have a look about it? Also, I'm anxiously to wait the new release (maybe 12.4? laugh) to fix it. Do you know any estimate ETA for it? syslog

Have tried some times and after the ipv6 address disappeared, I can never get the diagnostics. Even cannot see the output "Starting diagnostics collection". Maybe some command is stucked and may related to the ipv6 addresss disappear. Here I collect the diagnostics before ipv6 get broken. @ljm42 Could you please also have a look? tower-diagnostics-20230725-1026.zip