Leaderboard

Popular Content

Showing content with the highest reputation since 06/09/21 in Report Comments

  1. For Unraid version 6.10 I have replaced the Docker macvlan driver for the Docker ipvlan driver. IPvlan is a new twist on the tried and true network virtualization technique. The Linux implementations are extremely lightweight because rather than using the traditional Linux bridge for isolation, they are associated to a Linux Ethernet interface or sub-interface to enforce separation between networks and connectivity to the physical network. The end-user doesn't have to do anything special. At startup legacy networks are automatically removed and replaced by the new netwo
    8 points
  2. Manged to catch this today. With the lightest of google searches it looks like it may be a bug/regression in the kernel. I very well could be wrong but maybe? https://askubuntu.com/questions/1293945/20-10-complete-system-freeze-with-general-protection-fault-smp-nopti https://www.spinics.net/lists/linux-nfs/msg78091.html https://www.spinics.net/lists/amd-gfx/msg48596.html Jun 12 14:00:01 thelibrary kernel: Jun 12 14:00:44 thelibrary kernel: general protection fault, probably for non-canonical address 0x1090000ffffff76: 0000 [#1] SMP NOPTI Jun 12 14:00:44 thelibr
    2 points
  3. Hey, I just upgraded and made a post about this over here. Just to keep things simple i'm going to roll back. (I don't need any of the new features or NVidia driver support). But is there a timeline of when this will be fixed? -Thanks
    1 point
  4. Changed Status to Solved Changed Priority to Other
    1 point
  5. I'm not sure how true this is, but I was under the impression that it was broadcast traffic, in conjunction with static IPs that was causing macvlan to s*** the bed and cause kernel panics. Now I'm not sure if this is true with every vendor, but Ubiquiti switches/routers do not route broadcast packets between networks (so I was told/read), which was the idea behind creating vlans for docker containers with static IPs. I also think it was thrown out there that certain network adapters may be more prone to this than others. This is a very good point since it could b
    1 point
  6. I went this route and even created user defined bridge networks on a completely different NIC and still had the same issues. I suspect you'll see the issue resurface in a week or so, as this is exactly what happened to me. I have not tested using VLANs, but moved any containers needing their own IPs off of Unraid and haven't had issues for months.
    1 point
  7. What service is it? Out of curiosity at this point really. What about adding another NIC (if your motherboard doesn't already have 2 or more LAN ports?) That could be a very cheap $15 card for a gigabit NIC. https://amzn.to/3zfpmzF (referral link) I beleive that way you could keep the same IP address, but give it its own network interface instead?
    1 point
  8. Thanks for the solution works great!
    1 point