<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Cannot ping across VLANs on a 2100 when we add WAN2]]></title><description><![CDATA[<p dir="auto">Short version:<br />
We have a netgate 2100 with ports tagged with 2 Vlans. We decided to add an additional WAN2 so took port 4 out of the VLAN tagging (and internal switch) and setup Wan2. We cannot now ping across the two vlans.</p>
<p dir="auto">If we revert to the config backup prior to setting up Wan2 we can ping again.</p>
<p dir="auto">Long version:</p>
<pre><code>VLAN group 	VLAN tag 	Members 	Description 	Action
0                  1              1,2,3,4,5       Default System VLAN
1 		  11              1t,2,5t         VLAN 11 - DATA 192.168.11.0/24
2 		  30              1t,3,5t         VLAN 30 - DATA 10.1.11.0/24
</code></pre>
<p dir="auto">WAN1 has an upstream connection to our internal network on 192.168.77.0/24</p>
<p dir="auto">We can ping across VLANs and out to WAN and things are working as expected.</p>
<p dir="auto">If we then configure WAN2 on Port4 to connect to a 5G router with ethernet connection and as soon as this is done we can no longer ping across VLANs. The Wan connections are working and we can ping out. Port 4 only had VLAN 4084 &amp; Port 5 (2.5Gb uplink) tagged. 4084 being high to denote it was “Special” :slight_smile:</p>
<p dir="auto">Just for fun we plugged in a USB network connection to the 2100’s USB port and we were able to configure this as WAN2 which was working and also VLANs were working fine.</p>
<p dir="auto">Any thoughts on where we are screwing up</p>
]]></description><link>https://forum.netgate.com/topic/190679/cannot-ping-across-vlans-on-a-2100-when-we-add-wan2</link><generator>RSS for Node</generator><lastBuildDate>Tue, 06 Oct 2026 23:49:14 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/190679.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 26 Oct 2024 10:26:00 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cannot ping across VLANs on a 2100 when we add WAN2 on Sat, 26 Oct 2024 16:16:10 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/desquinn">@<bdi>desquinn</bdi></a> Port 4/WAN2 is a unique subnet?</p>
<p dir="auto">The steps in https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/configuring-the-switch-ports.html just isolate the port, it should not affect anything else.</p>
<p dir="auto">Steps 21-22 remove 4 from VLAN group 0 but your text shows it in there.</p>
<p dir="auto">If you configure WAN2 but unplug it what happens?</p>
<p dir="auto">Can you ping from pfSense into each VLAN?</p>
<p dir="auto">Check Diagnostics/Routes.</p>
]]></description><link>https://forum.netgate.com/post/1189232</link><guid isPermaLink="true">https://forum.netgate.com/post/1189232</guid><dc:creator><![CDATA[SteveITS]]></dc:creator><pubDate>Sat, 26 Oct 2024 16:16:10 GMT</pubDate></item></channel></rss>