<?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[WAN uplink on LAN ports]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I have the SG-2100. I have a multi-WAN config so I have to use one of the "internal" switch ports on the SG-2100 as WAN-uplink. The port is on its own VLAN.</p>
<p dir="auto">How safe is this compared to a dedicated interface like the WAN-port?</p>
<p dir="auto">Is it a problem while booting? I mean before pfsense software is loaded as it is a switch port.</p>
<p dir="auto">Best Regards<br />
Frode</p>
]]></description><link>https://forum.netgate.com/topic/190489/wan-uplink-on-lan-ports</link><generator>RSS for Node</generator><lastBuildDate>Wed, 13 May 2026 12:51:57 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/190489.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 11 Oct 2024 23:18:17 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to WAN uplink on LAN ports on Sun, 13 Oct 2024 15:57:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/frodet">@<bdi>frodet</bdi></a> All interfaces are treated equally on pf. A wan interface  has also gateway configured.<br />
While booting you just have a layer 2 switch, with no configured ip anywhere, so it doesn't exist to the ip world. As in all managed l2 switches, you need management process to boot to be able to touch anything.<br />
In this case, it is pf itself that must boot up first.</p>
]]></description><link>https://forum.netgate.com/post/1187863</link><guid isPermaLink="true">https://forum.netgate.com/post/1187863</guid><dc:creator><![CDATA[netblues]]></dc:creator><pubDate>Sun, 13 Oct 2024 15:57:18 GMT</pubDate></item></channel></rss>