September 16, 201610 yr unRAID OS Version: 6.2 Description: When setting a static IP and adding a VLAN, the gateway IP is removed. How to reproduce: Set IP assignment as static; set 'Enable VLANS' to yes; enter VLAN number and IP address assignment to 'Automatic'; click 'Apply'. Expected results: Gateway IP field would remain set. Actual results: Gateway IP field is blank. Other information: If the server is started in this condition, unRAID has no network access.
September 16, 201610 yr unRAID OS Version: 6.2 Description: When setting a static IP and adding a VLAN, the gateway IP is removed. How to reproduce: Set IP assignment as static; set 'Enable VLANS' to yes; enter VLAN number and IP address assignment to 'Automatic'; click 'Apply'. Expected results: Gateway IP field would remain set. Actual results: Gateway IP field is blank. Other information: If the server is started in this condition, unRAID has no network access. Can you post your network.cfg file. In addition: when using DHCP on VLANs then you need to ensure your DHCP server doesn't send a gateway setting. You either end up with multiple gateways or no gateway at all. For this it is recommended to use static addresses on VLANs.
September 16, 201610 yr Author unRAID OS Version: 6.2 Description: When setting a static IP and adding a VLAN, the gateway IP is removed. How to reproduce: Set IP assignment as static; set 'Enable VLANS' to yes; enter VLAN number and IP address assignment to 'Automatic'; click 'Apply'. Expected results: Gateway IP field would remain set. Actual results: Gateway IP field is blank. Other information: If the server is started in this condition, unRAID has no network access. Can you post your network.cfg file. In addition: when using DHCP on VLANs then you need to ensure your DHCP server doesn't send a gateway setting. You either end up with multiple gateways or no gateway at all. For this it is recommended to use static addresses on VLANs. network.cfg Before adding VLAN: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="5" BONDNICS[0]="eth0 eth1" BRNICS[0]="bond0" DESCRIPTION[0]="" USE_DHCP[0]="no" IPADDR[0]="192.168.1.154" NETMASK[0]="255.255.255.0" GATEWAY="192.168.1.1" DHCP_KEEPRESOLV="yes" DNS_SERVER1="192.168.1.1" DNS_SERVER2="" DNS_SERVER3="" MTU[0]="" SYSNICS="1" After adding a VLAN: # Generated settings: IFNAME[0]="br0" BONDNAME[0]="bond0" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" BONDING_MODE[0]="5" BONDNICS[0]="eth0 eth1" BRNICS[0]="bond0" DESCRIPTION[0]="" USE_DHCP[0]="no" IPADDR[0]="192.168.1.154" NETMASK[0]="255.255.255.0" DHCP_KEEPRESOLV="yes" DNS_SERVER1="192.168.1.1" DNS_SERVER2="" DNS_SERVER3="" MTU[0]="" VLANID[0,1]="1" DESCRIPTION[0,1]="Home" USE_DHCP[0,1]="yes" VLANS[0]="2" SYSNICS="1" The GATEWAY="192.168.1.1" setting is missing. I can go back and add it after the VLAN is added and it will take.
September 16, 201610 yr The GATEWAY field relates to the main interface (no VLAN). The main interface here is set to "no-dhcp" and none of the fields filled-in. When you use DHCP for VLANs then a gateway field is not displayed, but it is set for that VLAN (if given by the DHCP server). You can verify the routing by telnetting into your system and do: ip route
September 16, 201610 yr Author The GATEWAY field relates to the main interface (no VLAN). The main interface here is set to "no-dhcp" and none of the fields filled-in. What fields aren't filled in? When you use DHCP for VLANs then a gateway field is not displayed, but it is set for that VLAN (if given by the DHCP server). You can verify the routing by telnetting into your system and do: ip route I guess my networking ignorance is going to show, but I don't understand. Without the gateway on the main interface, unRAID cannot connect to the internet and things like dockers can't check for updates. Are you telling me I'm doing something wrong in the setup? ip route with VLAN: 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev br0.1 proto kernel scope link src 169.254.206.15 metric 224 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.155 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Docker can't phone home.
September 16, 201610 yr It will all workout if you move your main connection back from VLAN 1 to the 'untagged' settings... (aka delete VLAN 1)
September 17, 201610 yr Author It will all workout if you move your main connection back from VLAN 1 to the 'untagged' settings... (aka delete VLAN 1) I just fill in the gateway manually and apply the setting and all works. It should accept the setting initially and not remove it. If I set all settings to static, the gateway should be accepted as I set it when I add a vlan. I see the issue as a webgui problem and not a network problem. Did you try to duplicate my issue in the gui? Select all settings as static with the gateway set manually, apply, then set up a vlan and apply. Shouldn't the manual gateway setting I enter stay as I set it? There should not be a dhcp request to lookup the gateway, it should stay as I set it manually. It works when I enter it after the vlan is setup.
September 17, 201610 yr It will all workout if you move your main connection back from VLAN 1 to the 'untagged' settings... (aka delete VLAN 1) I just fill in the gateway manually and apply the setting and all works. It should accept the setting initially and not remove it. If I set all settings to static, the gateway should be accepted as I set it when I add a vlan. I see the issue as a webgui problem and not a network problem. Did you try to duplicate my issue in the gui? Select all settings as static with the gateway set manually, apply, then set up a vlan and apply. Shouldn't the manual gateway setting I enter stay as I set it? There should not be a dhcp request to lookup the gateway, it should stay as I set it manually. It works when I enter it after the vlan is setup. You use a set up which I didn't use before, I have a look and see for any 'improvements'.
September 17, 201610 yr Author That surprises me. I would think that static settings would not be that unusual. Leave it to me to be the odd man out. Thanks for taking a look.
September 17, 201610 yr That surprises me. I would think that static settings would not be that unusual. Leave it to me to be the odd man out. Thanks for taking a look. Your set up is special because you have the main link (untagged) configured as static and created VLAN 1 as dynamic. VLAN 1 is considered the same connection as the untagged connection (i.e. your switch will treat them as the same connection).
September 17, 201610 yr Author How else would I set up the VLANs? I want my server fixed on a static ip address, and the VLAN ip addresses to be assigned by the switch. Would I want to set static ip addresses on the VLANs? Wouldn't it be best to let the switch handle that? EDIT: I think I understand a little better now. I need to set up the ip settings for automatic, and set the VLAN settings to my static ip address. The way I have it, the access to the server is all untagged. I will make some changes and try it out. I would suggest some help be added to the VLAN configuration.
September 17, 201610 yr Ok, hold your horses ... I did some investigation and made a similar config as yours. The thing I could not understand - and wasn't right - is that first time the default gateway field is emptied and a second time the gateway field persisted. It turns out to be a BUG when adding a VLAN (any number) with DHCP enabled on that VLAN. I've made a correction for that. With the above fix your case actually works. You may want to keep it, but until the fix is present you need to manually add the default gateway a second time. Ps. If you are adventurous then the fix is available thru "Dynamix Bleeding Edge" plugin.
September 17, 201610 yr Author Ok, hold your horses ... I did some investigation and made a similar config as yours. The thing I could not understand - and wasn't right - is that first time the default gateway field is emptied and a second time the gateway field persisted. It turns out to be a BUG when adding a VLAN (any number) with DHCP enabled on that VLAN. I've made a correction for that. With the above fix your case actually works. You may want to keep it, but until the fix is present you need to manually add the default gateway a second time. Ps. If you are adventurous then the fix is available thru "Dynamix Bleeding Edge" plugin. That's exactly the situation I ran into.
September 18, 201610 yr Author I'm marking this as solved. It is fixed in the next release of dynamix.
Archived
This topic is now archived and is closed to further replies.