April 19, 20251 yr Using Unraid 7.0.1. I was working on setting up LAG (not working so far), and noticed the interface defaulted to IPv4 only. I use IPv6 sometimes, so I set it to IPv4+IPv6. Later I noticed that file sharing was broken for some clients. All clients could ping the Unraid server at T440.local, but one Windows client gave only Error 53 when I tried "net view T440". Another windows client gave the shares list. From the system that failed I was able to get the shares list by reference the server by IP. "net view \\192.168.1.4" All clients could ping the server at the IP. The failing system could ping T440.local as IPv6, but forcing IPv4 failed: c:\>ping /4 t440.local Ping request could not find host t440.local. Please check the name and try again. I changed the network interface on Unraid back to IPv4 only, and shares are working consistently for all Windows clients again. c:\batch>ping /4 t440.local Pinging t440 [192.168.27.4] with 32 bytes of data: Reply from 192.168.27.4: bytes=32 time<1ms TTL=64 Reply from 192.168.27.4: bytes=32 time<1ms TTL=64 Why?
April 19, 20251 yr Community Expert unriad requires some additional settings. By default Unraid v7 has dsiable ipv6. Can be found in docker inspect commands and other settings through out unraid... 1. Unriad network settings. Network protcal needs to use both IPV6 and IPV4 2. secondary docker settings for bridge... Settings > Docker -You want host access enabled and preserver. I prefer macvlan over ipvlan with is fine... some docker need adational lan idenity. 3. VM settings regarding network Setting > VM Manger note the Default Network Source. it may say vhost0 ... You don't want to be on virbr0 as that will tell VM to use the libvirt internal dhcp and router and be given a dhcp IP from the VM hyper-V virtual switch/router.... 4. VM xml setting on the nic and optional Unraid script need to enable ipv6 cross traffic... #!/bin/bash # Delay before starting sleep 10 # Apply sysctl settings apply_sysctl_settings() { echo "Applying sysctl settings..." sysctl -w net.ipv6.conf.all.forwarding=1 sysctl -w net.ipv6.conf.br0.accept_ra=2 sysctl -w net.ipv6.conf.br0.accept_ra_rt_info_max_plen=64 echo "Verifying sysctl settings..." sysctl net.ipv6.conf.all.forwarding sysctl net.ipv6.conf.br0.accept_ra sysctl net.ipv6.conf.br0.accept_ra_rt_info_max_plen } apply_sysctl_settings due to underlying changes in the docker system and VM system unraid to maintain connectivity disabled ipv6 over the docker in favor of IPV4 traffic to guarantee the ability for things to talk and connect. If you run a service such as windows samba, it will often use ipv6 over ipv4 first... On UnRaid. Running the above script with user script plugin. re-enables the Linux system control variables to enable ipv6 across interfaces. Furth Unriad uses libvirt domain xml configurations... Review: https://libvirt.org/formatnetwork.html In the VM note your xml code... a Default example: <interface type='bridge'> <mac address='ac:87:a3:5b:17:2f'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> you may need to add adational data to your VMs Nic to be able to grab a IPV6 address.
April 20, 20251 yr Author @bmartino1 at this point I am not using Docker at all. Currently I'm working with a simple disk array with shares. I'm trying to understand why enabling IPv6 causes the Unraid system to be unreachable by its local name "T440.local" and the shares to become unavailable by the share name T440. Disabling IPv6 causes these names to work again.
April 20, 20251 yr Community Expert this has to do with default unraid configurations and how windows defaults to using ipv6 when available. as unraid will not forward the traffic and will prefer and default to ipv4. There are additional samba options you could use as well. As I have fought this issue before... I usually end up running a registry edit on windows to re-enable unsecure anonymous and guest authentications... Sometimes the default unraid samba server doesn't use or accept ipv4 and windows saw a ipv6 address and tried to use a ipv6 for unraids samba share... Even if you are not using docker the above will assist in setting some additional option for how unriad uses the interfaces and accepts bridge traffic. You are experiences a dns/netbios issue... you can try running a dns server like pihole / adguard and use the FQDN ot he ipv4 address to fix name resolutions.. or use the windows host file... Regardless this is a misconfiguration somewhere and could even be caused by your router... USeing the IEEE RFC standards the interal at home search domain should be .home.arpa unraid depending on mixed networks (apple mdns) will default to .local when your router may be using .localdomain or .lan https://www.rfc-editor.org/rfc/rfc8375.html this mean the ipv6 search domain is different so t440 machine is actual FQDN may be t440.lan etc... etc... Hard to pinpoint where and when it broke due to underline default configurations. see forum thread.
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.