<![CDATA[Vlan communication on em interfaces]]>I tried updating to the last snapshot last night and lost connectivity across my vlans again. I have to fallback to an April 17 2012 snapshot in order to get my vlans working again. I have tried to update to the latest snapshot a number of times since April, but the results are always the same.

Should I try a clean install of the latest snapshot or is there still a known issue with em interfaces and vlan communication? I have 2 em NICs that are on direct connected vlans with no tagging and they can't communicate with each other either.

LAN (em0) can't talk to Opt1 or any other network connected to the pfsense
Opt1 (em1) can't talk to LAN or any other network connected to the pfsense

Communication works correctly on the April 17 2012 snapshot

]]>https://forum.netgate.com/topic/52898/vlan-communication-on-em-interfacesRSS for NodeFri, 12 Jun 2026 20:31:54 GMTSat, 09 Feb 2013 15:38:28 GMT60<![CDATA[Reply to Vlan communication on em interfaces on Mon, 11 Feb 2013 15:08:40 GMT]]>After manually entering all of my settings from a backup configuration, I believe I found a more concrete answer than 'something in the upgrade path'. I have a multi-wan setup and do load balancing and prioritization across each link. Everything on the clean installed worked fine until I had loaded all of the rules in (which is where outbound gateways are defined). It seems that between the April 17 2012 snapshot that I was running and last weeks, something changed with how internal IPs and directly connected networks are routed when the default rule for an interface does load balancing. I believe the change occurred in a more narrow timeframe as I have had this issue on other snapshots I tried as well, prior to list week, including a Sept 2012 snapshot.

I am not sure how many others have come across this issue, or if you always needed a rule per interface to handle internal/direct connected networks and the snapshot I was using had a bug that ignored that, but it would be good to know what changed in regards to that and why.

Thanks all for reading about my troublesome weekend messing with pfSense snapshots.

]]>https://forum.netgate.com/post/378319https://forum.netgate.com/post/378319Mon, 11 Feb 2013 15:08:40 GMT<![CDATA[Reply to Vlan communication on em interfaces on Sat, 09 Feb 2013 22:39:44 GMT]]>I did a clean install and these issues are resolved. My only guess is the constant snapshot upgrade path broke something along the way.

]]>https://forum.netgate.com/post/378042https://forum.netgate.com/post/378042Sat, 09 Feb 2013 22:39:44 GMT<![CDATA[Reply to Vlan communication on em interfaces on Sat, 09 Feb 2013 18:05:59 GMT]]>You. Have two interfaces without vlan configured?

Vlan Id x untagged on switch means no config on server's interface.

]]>https://forum.netgate.com/post/378019https://forum.netgate.com/post/378019Sat, 09 Feb 2013 18:05:59 GMT