bonienl

Community Developer
  • Posts

    9669
  • Joined

  • Last visited

  • Days Won

    67

bonienl last won the day on June 28

bonienl had the most liked content!

Retained

  • Member Title
    when will then be now - soon™

Converted

  • Gender
    Male
  • Location
    Netherlands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

bonienl's Achievements

Veteran

Veteran (13/14)

1.5k

Reputation

9

Community Answers

  1. Thanks for investigating. Are the strings "AAAA...." fixed or these may change per installation?
  2. It works fine when using a static IP address assignment for Unraid. Using DHCP may cause a race condition, and the shim network is not created when your DHCP server is slow in responding.
  3. It works fine when using a static IP address assignment for Unraid. Using DHCP may cause a race condition, and the shim network is not created when your DHCP server is slow in responding.
  4. Do you use DHCP or a static IP assignment for your server, use static.
  5. I use ipvlan extensively without any problems. Loosing internet access seems to point to something happening in your network set up outside Unraid.
  6. Jul 2 00:47:27 Unraid kernel: Hypervisor detected: VMware Can you run Unraid natively. In this setup the network interfaces are not being detected by udev and hence no rules file is created, this results in random selection each time the system is started.
  7. Unraid 6.10.3 has a regression error which breaks the cumulative parity check operation. Will be fixed in the next release. Thanks
  8. I made a fix for this, should be available in the next version. Thx.
  9. I made a fix in uploading binary files using Dynamix File Manager, please update.
  10. I made a fix in uploading binary files using Dynamix File Manager, please update.
  11. I made a fix for the upload of binary files using the Dynamix File Manager, please update.
  12. When you enable "Host access to custom network" a routing trick with more specific routes for the same IP subnet (br0) is introduced to fool Docker and make access possible, something which Docker does not allow for security reasons. The first question to ask: do I really need host access? In general this is NOT required, but there are some specific cases which need it. Have you tried and tested to run your containers without host access enabled? Because br0 and shim-br0 is actually one and the same machine (your Unraid box) but announced twice, it can be that certain network equipment, e.g. certain firewalls, do not like this situation and prohibit communication. In such a case you'll need to look into that device configuration and see if exception rules can be set.
  13. Good to hear you solved your issue, just want to say that I am using custom networks extensively without any problems. Usually these kind of issues are a combination of things, including the network equipment in use.