Adding VLAN kills my SSH session [SOLVED]

[rohlando]

While I am green to Unraid, I am trying to add a VLAN to an interface as I have 3 VLANS which I would like to use for Apps.

 

Presently my Unraid Server has 4 NICs, I have tried several different options to get this to work with ZERO success. I have read several of the posts trying to get this to work but every time I add a VLAN to a specific interface, my SSH session to the Unraid host dies after 30 seconds. If I remove the VLANs all works as expected with the exception I am unable to assign a Specific ip within one of the VLANs I would like to use. I am going crazy trying to figure this out and what could be the cause.

 

NIC 1 = IP for Management of Unraid (eth0)

NIC2 = IP for VLANs (eth1) - NOTE: No VLAN Tags setup yet on this interface

NIC3 / NIC4 = (BOND) for 802.3 LAG (LAG setup on the Switch) 

 

SSH to the host, run a pin test - Pings as normal does not break

 

NIC2 = Add VLAN, Either statically assign an ip or let it pull from DHCP.

 

SSH back to the host, run a ping test - Pings for 30 seconds then SSH closes

Reopen SSH back to the host, re-run the ping, same results.

 

Remove the VLAN from the interface, SSH works as Normal.

 

Anyone have any Suggestions because I am going nuts here. Does not make sense.

[bonienl]

What do you configure exactly when you add VLANs?

 

Start with adding VLANs and assign NO address to these.

Adding VLANs also means your switch/router must support this feature (also called tagged and untagged frames). Do you have the right equipment?

Switch/router must be configured properly too.

[rohlando]

Thanks for the response.

 

Yes, I have a pfsense router with a Unifi switch.

 

pfSense sees these VLANS and I use these within the network currently. Unifi also sees these with no issues.

 

As you can see from the Screen Shot, I have it set the way you stated above, however I am unable to assign an IP from the other VLANs to the Docker Container for use. (NOTE: Doing it this way does not cause the SSH to drop. Meaning just doing NONE).

 

I would like to be able to assign my DOCKER App an IP on the VLAN 130 which is 192.168.30.x or the 140 192.168.40.x. 

 

[bonienl]

Also change eth2 to "None".

Next go to Docker settings and switch to advanced view.

Here you can define per interface the subnet and gateway used for Docker containers.

 

Remember that Unraid uses always eth0 as its management interface.

[Vr2Io]

2 hours ago, rohlando said:

NIC2 = IP for VLANs (eth1) - NOTE: No VLAN Tags setup yet on this interface

 

1 hour ago, rohlando said:

pfSense sees these VLANS and I use these within the network currently. Unifi also sees these with no issues.

 

1 hour ago, rohlando said:

however I am unable to assign an IP from the other VLANs

Problem seems on network side, does any device like Unraid ( untag and tag traffic in same ifc ) also work ?

You can rule out problem on Unraid or Network side, by setting the switch (port) accept untag only and then add VLAN in NIC, and try SSH kill or not.

[rohlando]

2 hours ago, bonienl said:

Also change eth2 to "None".

Next go to Docker settings and switch to advanced view.

Here you can define per interface the subnet and gateway used for Docker containers.

 

Remember that Unraid uses always eth0 as its management interface.

That was it!

 

Thank you for your help, very grateful. Still trying out UnRaid, however this helps me move forward. Thanks again!