September 16, 20169 yr I have a HP Proliant system running unRAID, which was previously connected to a switch using the 4 onboard gigabit ports. Recently, I wanted to improve speeds between my main PC and the server, so I bought a cheap set of 2 10GBe NICs on eBay (HP CONNECTX2). I installed one in the server, and one in my PC and connected them. I set up the new network interface in unRAID with an IP of 20.20.20.10, and gave my PC an IP of 20.20.20.5 in Windows on the new network card. This is outside of the main network's range (10.10.10.x). The connection seems to be fine, I can connect to the unRAID server from my PC and I get pretty much the write speeds that I was expecting (350-410MB/s writing to cache). The read speeds don't seem any better, but maybe I can find some tweaks or something to improve that. The problem that I'm having is that the unRAID server seems to be trying to use the new interface to do all of its internal work, like checking for updates for Plugins and Dockers. All of my Plugins show "no update" in the status column, and the Dockers all show that an update is available, but it fails when I try. So is there a better way for me to set up the 10GBe interface in unRAID that would solve these problems, or is there a way for me to tell unRAID to use the onboard interfaces for plugin/docker updates? Windows Settings: http://i.imgur.com/S9OJEIl.png unRAID Network Settings: http://i.imgur.com/nJcvXKn.png Thanks for your time!
September 16, 20169 yr I set up the new network interface in unRAID with an IP of 20.20.20.10, and gave my PC an IP of 20.20.20.5 in Windows on the new network card. This is outside of the main network's range (10.10.10.x). Don't do that. 20.20.20.5 and .10 are not private addresses, you will cause yourself issues by using internet routable addresses like that. https://en.wikipedia.org/wiki/Private_network#Private_IPv4_address_spaces
September 16, 20169 yr Author I set up the new network interface in unRAID with an IP of 20.20.20.10, and gave my PC an IP of 20.20.20.5 in Windows on the new network card. This is outside of the main network's range (10.10.10.x). Don't do that. 20.20.20.5 and .10 are not private addresses, you will cause yourself issues by using internet routable addresses like that. https://en.wikipedia.org/wiki/Private_network#Private_IPv4_address_spaces Ok, I changed it to 10.10.20.10 and .5. I also disabled the NIC and updated to 6.2 stable and everything seems to be working. Thanks for your help.
Archived
This topic is now archived and is closed to further replies.