<![CDATA[Intervlan Routing (yes again)]]>I know this topic has been covered more than once and I indeed read a lot about pfsense specifics, but I cannot find anything that works.

So here it goes:

Requirements:

  1. No NAT
  2. working mDNS on ALL interfaces

Hardware is a server with 1 physical NIC running ESXi. The pfSense VM is presented with 3 virtual NICS

em0 (wan) = not used (as avahi excludes WAN from mDNS)
em1.50 (vlan 50) = Test network
em1.200 (vlan 200) = IoT
em2 = uplink to rest of the network

My very basic problem is that I cannot ping between em1.50 and em1.200
I have 2 dummy vm's. One in VLAN 200 and 1 in VLAN50.

However the dummy vm in vlan 50 can get out to my upstream router to the internet. The dummy vm in vlan 200 can only ping the pfsense gw.

The rulebase could be it, but I need some troubleshooting tips. I am pretty solid on Cisco & Juniper.. So ask away

]]>https://forum.netgate.com/topic/161382/intervlan-routing-yes-againRSS for NodeMon, 20 Apr 2026 13:26:37 GMTWed, 24 Feb 2021 20:29:03 GMT60<![CDATA[Reply to Intervlan Routing (yes again) on Wed, 24 Feb 2021 21:59:32 GMT]]>Lessons learned:

Make sure you clean up your old config (or do a re-install).

During a change in virtual NICS a Captive portal setting was mapped to an interface that was not intended to have one.

This isolated 1 vlan from the rest of the network.

Solved.

]]>https://forum.netgate.com/post/967755https://forum.netgate.com/post/967755Wed, 24 Feb 2021 21:59:32 GMT