Jump to content

bonienl

Community Developer
  • Content Count

    8729
  • Joined

  • Last visited

  • Days Won

    51

Posts posted by bonienl


  1. 1 hour ago, danktankk said:

    After disconnect, it just keeps adding connected time

    As long as you keep the WG tunnel in active state on the Unraid server, it is not really disconnected.

    This is also the reason why the time is incremented, because it will tell exactly when the last exchange has occurred.

    • Thanks 1

  2. 9 hours ago, Maddeen said:

    So with this settings it's impossible to get a sleep, correct? 

    Correct, you need to set a spin down time otherwise disks will stay active all the time.


  3. 33 minutes ago, Maddeen said:

    Any ideas?

    Check if the parity disk has a spin down time set.

     

    Do you have any docker containers or VMs running?

    Whenever something is written to the array, the parity disk gets involved.

     


  4. 26 minutes ago, ken-ji said:

    The 2nd way which I am using, is to simply disable IPv6 at the Unraid network configuration level.

    Interesting, never used it this way.

    Thanks for the explanation.

     


  5. The Docker implementation of IPv6 on bridge and host networks is flaky and interferes with the IPv6 routing of Unraid. It is switched off, and IPv6 is made only available for macvlan (custom) networks.

     

    Docker doesn't use SLAAC, it is handing out IPv6 addresses in sequence. The gateway address is ::1, and ::2 will be the first container.

     

    Privacy extensions (RFC4941) are intended to hide your identity when you are on the move. Typically useful for phones, tablets and laptops.

    When you connect "somewhere" you don't want people be able to recognize it is you again (the MAC address of your device reveals your identity).

     

    Servers are stationary and the use of privacy extensions is not meaningful. Some people even argue to not use them at all.

    A server needs a dedicated address which doesn't change. Much like setting a static IPv4 address for a server.

     

     

     


  6. Ok, I had a look again and found a way to make Docker happy.

     

    I'll make an update for the next version and your server should work (including the /128 address).

    • Thanks 1

  7. A small update you may want to make, it is not causing real issues, but your network.cfg file includes eth1 and eth2, which do not exist (anymore).

    Delete these lines

    IFNAME[1]="eth1"
    PROTOCOL[1]="ipv4+ipv6"
    USE_DHCP[1]="yes"
    USE_DHCP6[1]="yes"
    IFNAME[2]="eth2"
    PROTOCOL[2]="ipv4+ipv6"
    USE_DHCP[2]="yes"
    USE_DHCP6[2]="yes"

    And change sysnics to

    SYSNICS="1"

    A reboot is required for the new settings.

     

    Unraid gets a proper IPv6 address, but your router is advertising an additional /128 address, not sure why it is doing this. Check your router config.

     

    This /128 address causes several issues, including Docker which doesn't accept a /128 subnet (invalid CIDR address) and this results in no IPv6 connectivity.

     

    5 hours ago, sjaak said:

    why its not getting the ipv6 dns on it own

    It is because of a limitation in Unraid 6.8. When IPv4 is configured with a static IP + DNS, then IPv6 DNS needs to be static too.

     

    I have changed this behaviour and in Unraid 6.9, IPv6 DNS can be automatic independent of the IPv4 setting.

     

     


  8. Your diagnostics show virbr0 is present.

    virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
            inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
            ether 52:54:00:ad:12:42  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
            ether 52:54:00:ad:12:42  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    Try to re-assign the interface in your VMs

    • Like 1

  9. When there is no IPv6 network shown, it means docker did not create it (usually due to some configuration conflct).

    Can you post a screenshot of your docker settings page, with the docker service stopped and in advanced view?