Vlans on LACP routing out incorrect interface

[croiad]

Hi!

We have a server setup with 4 nics that have been configured in a LACP LAGG setup with a L2 Cisco switch that has an upstream link to pfSense for routing. We have a handful of vlans configured on TrueNAS with LAGG0 set as their parent device. These have been configured with only the network and not a direct IP (vlan100 172.16.100.0/24,vlan200 172.16.200.0/24, etc). We have one vlan designed for appliances configured with an IP to access the GUI (vlan11 172.16.11.3/29). This works correctly and the GUI is accessible. There are about 15 jails on the system that are all using various addresses from the configured vlans but not the appliance vlan11. These are all accessible on the network and working, yet not quite correctly.

In pfSense we are seeing the different vlan traffic all coming from the vlan11 interface. It appears this may be happening due to TrueNAS using the default gateway for vlan11, but all of the jails have their own default gateways configured? Source network is still correct though, so an entry looks like this -

This device on vlan50 is a jail on the TrueNAS with this setup -

Any advice or direction on this would be greatly appreciated.

 

[Patrick M. Hausen]

I would try to create the bridge interfaces statically, too.
I.e. create bridge50 with vlan50 as the only member and so forth. Then assign the bridge interfaces to your jails.

You will probably need to disable autostart for all jails, then reboot the system, so it will come up with no bridge interfaces automatically created.

HTH,
Patrick

 

[croiad]

Hi Patrick, thanks for the reply.

I actually had tried the bridges following a guide here in the forum, but I had not rebooted. It appears the reboot was the missing item though! Thanks again for the reply, everything appears to be working correctly now.