<![CDATA[Upgraded from 2.0.3 to 2.1.1, no connection between LANs]]>Hi,

I've just updated from 2.0.3 to 2.1.1 and now my different LANs have no visibility between them. Before upgrading I could ping and connect to IPs from different subnets without problems, now I can't. What could have changed for this to happen?

Thanks.

]]>https://forum.netgate.com/topic/67524/upgraded-from-2-0-3-to-2-1-1-no-connection-between-lansRSS for NodeMon, 20 Apr 2026 09:33:37 GMTSat, 05 Apr 2014 19:01:43 GMT60<![CDATA[Reply to Upgraded from 2.0.3 to 2.1.1, no connection between LANs on Sun, 06 Apr 2014 13:48:32 GMT]]>Hmm, are you sure about that Phil? It could be that my 2.1.1 boxes are upgrades and I haven't noticed a change in behaviour but I thought the default setting was enabled for the negate rules.
I have them disabled in Advanced: Firewall/NAT: because I prefer to set rules for everything I want to allow.

Steve

]]>https://forum.netgate.com/post/453098https://forum.netgate.com/post/453098Sun, 06 Apr 2014 13:48:32 GMT<![CDATA[Reply to Upgraded from 2.0.3 to 2.1.1, no connection between LANs on Sun, 06 Apr 2014 10:48:50 GMT]]>You probably have policy-routing rules that are pushing all the traffic out the gateway or gateway group/s.
In older pfSense versions, the code underneath put rules to pass local traffic before the policy-routing rules.
Now you need to do it yourself. Add rules at the top of each LAN-style interface like:
Pass protocol all, source LANnet, destination LAN2net

]]>https://forum.netgate.com/post/453083https://forum.netgate.com/post/453083Sun, 06 Apr 2014 10:48:50 GMT