<?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[Stuck while restoring VLANs to new hardware]]></title><description><![CDATA[<p dir="auto">I resolved my issue but decided to post it here just to ask if there was another way, or if this is a bug. (not sure this is the correct category; mods can move it)</p>
<p dir="auto">We had a router failure in our office and grabbed our spare 2100 to use for a few days.  To use a third interface we <a href="https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/configuring-the-switch-ports.html" target="_blank" rel="noopener noreferrer nofollow ugc">isolated port 4</a>.</p>
<p dir="auto">When restoring the config file to a new 4200, I got stuck when reassigning interfaces in the web GUI.  I couldn't delete the VLAN because it was in use on an OPT1 interface (mvneta1, which does not exist on the 4200).  However I could not delete the OPT1 interface using mvneta1.4084 because it had a VLAN attached. Is there a way around that loop?</p>
<p dir="auto">For anyone finding this post later, there are two solutions: one is that Netgate will convert configuration files for you, to/from Netgate hardware.  The other is to edit the .xml file to manually remove the VLAN section and assign the interfaces, then restore.</p>
]]></description><link>https://forum.netgate.com/topic/190706/stuck-while-restoring-vlans-to-new-hardware</link><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Apr 2026 15:20:20 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/190706.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 29 Oct 2024 15:40:42 GMT</pubDate><ttl>60</ttl></channel></rss>