bonienl

Community Developer
  • Posts

    10232
  • Joined

  • Last visited

  • Days Won

    65

Everything posted by bonienl

  1. Next release has automatic acknowledgment when life time is zero.
  2. I did a quick test and set the DNSv6 server to the link local address of my router, and this works. This is how my resolv.conf file looks like. # Generated by dhcpcd from bond0.dhcp domain bergware.com nameserver 10.0.101.100 nameserver 10.0.101.200 # Generated by rc.inet1 nameserver fe80::1ae8:29ff:febd:80c7
  3. Thanks for this explanation, I was not aware of this implementation. I have set up a local DNS server (pihole) and configured my router to provide clients with the IP address of pihole as DNS server, this is working fine in combination with DHCP/SLAAC. As far as I know we haven't changed the "dhcpcd" package which is handling all DHCP requests. Not sure why dhcpcd would add the interface name to the IP address, this is clearly not needed (wrong). Perhaps a workaround is to set a static DNS server entry and use the given LL IPv6 address.
  4. When DHCP is used then the server obtains the DNS information from your router. Using a link-local address as DNS server is wrong and your router should be configured with a global DNS server address instead. This could be the IPv6 address of the router itself (if it can act as DNS forwarder) or a public DNS server address. Alternatively you can set a static DNS entry in the Unraid network settings. e.g. 2001:4860:4860::8888 and/or 2001:4860:4860::8844 (google DNS servers)
  5. Thanks, I made a change to address this.
  6. I recommend to disable bridging and use bond1 instead. We have seen that the new macvtap network gives much better performance than bridging. Though your current set up should work without issues.
  7. For upcoming version 6.12.4 I added a new option to specify the life time of notifications. Default is 3 seconds.
  8. How many containers do you have? My main server has 30 containers and display is instantaneous on the dashboard. There are no code changes for the dashboard that would explain a different behavior.
  9. That should work properly (I have 4 NICs), likely a configuration issue. Need to see your diagnostics.
  10. Disabling bridging will change docker to use the bonded interface, including the VLAN networks. This is my docker set up # docker network ls NETWORK ID NAME DRIVER SCOPE b773f11c6dcc bond0 macvlan local a9315eb8f702 bond0.3 macvlan local 5d489327c46b bond0.4 macvlan local d69bccba5929 bond0.5 macvlan local a7b83120a899 bond0.6 macvlan local
  11. Looks like a wrong network configuration, please provide diagnostics
  12. This is docker renaming the interfaces and perfectly normal.
  13. I made a fix for displaying the IPv6 address in network settings. Should be included in the official release.
  14. @sonic6 I like to doublecheck. Can you post the result of (mask your public IPv6 address as needed) ip -6 addr show eth0
  15. This is a display thing, the interface will use your public IPv6 address and works properly. Let me see if can fix that.
  16. They should work as before. Host and bridge networks are not touched. When "host access" is enabled then the IP address of eth0 is duplicated to the macvtap (vhost) interface. The macvtap (vhost) interface has its own MAC address
  17. Thanks for reporting. I made a fix for the next release.
  18. Bridging is only needed when VMs are used, otherwise it can be disabled.
  19. These error messages come from 'netbios' I recommend to disable netbios and use WSD instead for host discovery. See Settings -> SMB settings
  20. You have two wireguard tunnels with the same IP address, that won't work. Delete the duplicate tunnel. We made some additional fixes in the upcoming version. I recommend you use the new version once available, it should work better with WG VPN tunnels.
  21. @SpaceInvader Question: when you change back to DHCP assignment, does the problem come back too?
  22. Wow, great find. Let me digest this and see if I can come with a possible solution. Maybe, maybe not, but at least we have a pointer to work on. Thx
  23. Don't see anything wrong in your diagnostics. How are you monitoring the server? On name or ipv4 or ipv6 address?