After now fiddling with default ethernet ports and realising this is one of the really not nice parts of Unraid, I thought I should create as a feature request as it appears nobody else has specifically requested the whole solution.

 

It would be great if the GUI could be improved to include:

 

1 - Assign any interface to any user chosen network designation in the system e.g. ETH0/1/2

2 - Ports could be clearly disabled when required via software (presently they still show up if disabled in hardware - so it's confusing as hell and you're not sure exactly what Unraid will try and do)

3 - The links between port designations to bridges were clearer i.e. ETH0 -> BR1 displayed visually

4 - That the system didn't completely disable the network and lock you out requiring reboots from physical machine when these changes are made (frustrating as hell when trying to work on a headless system)

5 - A default port could be chosen other than ETH0

6 - A default bridge could be selected in the docker settings similar to what can already be done in the VM settings

7 - An existing bridge can have other interfaces in it and not have the ETH0 interface in it (Currently if adding eth1 to the eth0 bridge you cannot remove eth0 via the GUI) - you can create a new bridge but this then requires you change it individually on all the dockers etc)

8 - The host setting in docker has a way of assigning it to an interface / designation - (currently it's stuck to ETH0 causing me grief)

9 - A 'reset network to defaults' option via the GUI without having to delete the file on the USB Stick

10 - Ability to change default route properly - even after running udev rules to fix incorrect eth assignments, disabling cards in BIOS, and deleting the network config entirely, Unraid continues to insist that the original onboard NIC must have the default route.  This shouldn't be this hard.

 

I would say a sort of software switch GUI would be the ultimate way of designing this - QNAP does it so I'm sure there's a ton of already designed open source solutions out there, nevertheless from the above (even if I have gotten one or two of these wrong), there's a bit to improve on in my opinion, that I think could be done quite easily..  Changing these (I'm sure there are others) would make a marked improvement to the networking capabilities of Unraid, which with all due credit for the other features in Unraid in my opinion is quite poorly set up at present.

 

Many thanks.

Edited April 26, 20197 yr by Marshalleq
Clarity

Let's see, because it seems you are not fully understanding the networking details.

 

This is my test server

It has a bonded interface with 4 members (eth0/1/2/3). It has two currently unused gigabit interfaces (eth4/5) and a direct 10G interface (eth6) for server to server backups.

17 hours ago, Marshalleq said:

1 - Assign any interface to any user chosen network designation in the system e.g. ETH0/1/2

Already possible.

17 hours ago, Marshalleq said:

2 - Ports could be clearly disabled when required via software (presently they still show up if disabled in hardware - so it's confusing as hell and you're not sure exactly what Unraid will try and do)

Already present

 

17 hours ago, Marshalleq said:

3 - The links between port designations to bridges were clearer i.e. ETH0 -> BR1 displayed visually

Already present

 

17 hours ago, Marshalleq said:

4 - That the system didn't completely disable the network and lock you out requiring reboots from physical machine when these changes are made

Changes are made for each interface separately and won't lock you out unless you are changing the management interface (eth0/br0) and made a mistake

17 hours ago, Marshalleq said:

5 - A default port could be chosen other than ETH0

Eth0 is the default management port. Any other interface can be freely used

17 hours ago, Marshalleq said:

6 - A default bridge could be selected in the docker settings similar to what can already be done in the VM settings

The default network for a docker container is determined by the container author (set in the XML file). This is either bridge or host, because only these two type of networks exist on every system (come with Docker)

17 hours ago, Marshalleq said:

7 - An existing bridge can have other interfaces in it and not have the ETH0 interface in it (Currently if adding eth1 to the eth0 bridge you cannot remove eth0

Bridging (and bonding) make use of a parent interface and optional members. When enabling bridging for eth0, it becomes the parent and other members such as eth1 can be added or removed.

17 hours ago, Marshalleq said:

you can create a new bridge but this then requires you change it individually on all the dockers etc)

When you change network interfaces, it does require a manual update of the docker containers. Docker containers can not magically change their network assignments. In fact you need to create a new image/container with the appropriate settings to make it work.

17 hours ago, Marshalleq said:

8 - The host setting in docker has a way of assigning it to an interface / designation - (currently it's stuck to ETH0 causing me grief)

The host network of Docker is associated with the management interface of the system, which is eth0 as explained before.

If you want to use a different interface for a container, it is done using custom networks.

17 hours ago, Marshalleq said:

9 - A 'reset network to defaults' option via the GUI without having to delete the file on the USB Stick

Why is this needed? Resetting to defaults can immediately break the GUI connection. Very inconvenient.

17 hours ago, Marshalleq said:

10 - Ability to change default route properly - even after running udev rules to fix incorrect eth assignments, disabling cards in BIOS, and deleting the network config entirely, Unraid continues to insist that the original onboard NIC must have the default route.

Again, eth0 is the management interface. This interface requires a default route otherwise the system is unable to communicate with the outside world and things like system upgrades and plugin/docker installations aren't possible.

 

You can use "Network Rules" to change the interface assigned to eth0 (or any other interface for that matter).

 

I recommend you create a topic under the general help and explain what you try to achieve with your set up.

People can give help and recommendations what to do.

 

Edited April 26, 20197 yr by bonienl

Lol. Thanks for your feedback. I’ll dissect this later and go through it. I expect I will have examples for most as to why it either doesn’t work as you say it does (maybe it should work and doesn’t or does not do what it says it does or some design thing).

Great to dissect this so we can find out the reality. Thanks for your detailed feedback.

My daughter is over from overseas for her birthday party today so probably won’t be for a day or two.

Thanks again.


Sent from my iPhone using Tapatalk