Jclendineng

Interesting, it appears that the changes to prevent dupe nics removed the interface rules by accident, I am also seeing changes to the network.cfg file removing the interface Macs so unless I'm missing something it is no longer possible to edit the interfaces directly from config either...correct me if they were moved and I missed it.

FYI it appears interface rules was removed in .10.2 release, so no longer can change to eth0 Edit: Disregard, it appears to be a known bug that many are reporting now, so a fix should be coming, they did not remove it on purpose.

Cool cool I'll check it out. Im lagging 2 10gb connections to my aggregation switch so definitely enjoy reading other peoples experiences with this. IMO 10gb is the sweet spot currently as 40gb isn't quite ready for *most* home users. Back to this, updated to the new patch and my duplicates are still gone so already better then 6.8. Glad a permanent fix is coming. Thanks to all the unraid devs for the hard work.

OK just making sure, I didn't fully understand from your post if you had tried the GUI post-6.10. Mine is now fixed, but maybe as you say its only because I haven't tried to edit.

Maybe the dupes came from editing the network.cfg manually, I don't know that it's recommended. You can try doing it from the GUI, looks like that works and is persistent...I wonder what they fixed? From the reports, they didn't think it was an issue per se so Im assuming they didn't do anything, it was one of the many upstream driver/dependency/kernel updates. In any case I am resting a bit easier knowing that 1 inconsistency is fixed and I don't have to worry about why anymore.

Are you guys saying do NOT use bonding on 6.10? I use bonding to lagg 2 10gbe ports to my aggregation switch. Is that not recommended?

Ill note that it looks like you are using single stream iperf in which case that's normal. Try iperf3 -c server -P8 for 8 streams. Also I would NOT change your MTU that's asking for trouble. 1500 is plenty for 10gb. jumbo Is not needed unless you know what its used for and you need it. Its going to give you trouble down the line. Remember, anything on the network that talks to that needs to have the MTU tuned now and if there is any mismatch you will drop packets. my suggestion is leave it default and save yourself the future problems.

Was this fixed for you in the 6.10.0 Stable? I swear it was still broken in the betas but lo and behold, it is correct for me now. Edit: The only thing I did recently would (should) have 0 affect on networking. I needed to (for long story reasons) use a cache drive nvme in another server, and I had another one I was swapping in. So I set the cache to yes so it moves everything to the array. I then stop the array, disable VMs and Docker and start up again so I can move the system folder domain folder. I then replaced the cache drive, made sure it was up and running, and set the cache to prefer so it copies back to the cache. When that's done I set to cache only as it was before, stop the array, enable Docker and VMs and start up again. I then noticed an issue with my 801ad lagg bond and went to network settings to fix and noticed the bond was screwed up, it had dropped my duplicate nic. So I re-did my lagg, set up the vlans again and started the array. Not sure what any of those steps had to do with network setup except that I did have docker and vm services stopped when I rebooted with the new cache drive so potentially that cleared something in the config that docker or vm manager was doing to create the dupe nic.

I just don't touch it and it seems to work OK. Still shows multiple dupes but that's fine as long as you don't try re-arranging them it works.

A couple of us with same issue, any dual port mellanox nic + onboard nic - basically the same stuff you are seeing. Did you figure out what was wrong? I filed a bug report and they said it was card related, so did you have to flash anything? I have updated to the latest FW and disabled netboot for faster startups. Can recreate with all my dual port cards, single port seems fine, but I only have 1 to test.

OK I filed a bug report, its not an unraid issue, still trying to track down how unraid determines the nic as I received conflict information, that unraid does not use the same Mac for multiple interfaces, and yet a clean install assigns 1 Mac for port 1 and 2 Macs for port 2. ill report back if I find info. im going to stand up a Debian server to see if I see the same result and that will 100% determine if unraid related. Edit: see this:

Welp that's a hard no. I tested with a single port and it flashed fine, put a dual port in and unraid had a hernia. It adds a duplicate Mac every time I reboot so I am going to file a bug report in the bug report section as this hasn't gotten any replies in...almost ever I can replicate though, I tested with a dual port sfp+ card and it does indeed have duplicates in the OS.

Ill take a stab at this, what model of Nic? I had a similar issue with Mellanox ConnectX3 MCX312A that I was able to fix. Duplicate Macs are the result of a bad or improper firmware flash so if you bought them off eBay like that, seller didn't understand how to flash when upgrading firmware Basically I just flashed the static Mac and guid again. https://forums.servethehome.com/index.php?threads/mellanox-connectx-3-en-duplicate-permanent-mac-address-issue.24790/ Im sure that's probably your issue, though I don't know how to flash HP cards (should be some documentation online)

A couple standalone connectors work, barely, there is a lot of play though. Never had that happen.

Dang autocorrect 🤣 fixed. Yes the dacs slide in but don’t lock and slide out easily. I assumed it was not expected so I’ll return…eBay seller probably didn’t test.

Question. I just got mine and none of the SFP+ dacs will lock in. I tested with my other 1 port connectx-3 and it locks fine on all dacs. Does the 2 port lock in for you? I’m assuming I got a bad one.

bump.

I get the same issue on installing plugins...what version are you on? Seems like a RC2 issue

same issues with ryzen, Im not sure this plugin is still supported though...maybe something is coming natively in 6.10...

I need to install a plugin: scan-cli-plugin This is for vulnerability scanning local images. Is there a way to install docker plugins on unraid, or would I need to create a vm and install the linux version of docker there?

Same issue, Fail2Ban does not work in the slightest, not sure why. It is started as a service, the jail is set up properly, the IP is banned, but not dropped/rejected/blocked in any form. Its noce to have a list of IPs I can block manually in my FW but would be nice if fail2ban would work.

Basically this requires a paid license to use? And if so, I see on the AMP site the option to purchase, is this yearly, monthly, etc?

If I install Catalina, am I able to update to Big Sur from inside the VM, or is that not recommended? Thanks!