https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162013-09-17T19:00:35ZpfSense bugtrackerpfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=125162013-09-17T19:00:35ZAdam Thompsonathompso@athompso.net
<ul></ul><p>Sadly, I've just confirmed this... and also confirmed that IT DOESN'T HAPPEN EVERY SINGLE TIME! WTF?!?<br />I changed OPT1/RD_LOM_DIST from 202 back to 3 - no problem.<br />I changed OPT1/RD_LOM_DIST from 3 back to 202 - no problem.<br />I then changed OPT1/RD_LOM_DIST from 3 to 203 - and blew away my LAN/HOMEPRIVATE interface.<br />In config.xml, my LAN interface got changed from lagg0_vlan4 to lagg0_vlan203 while OPT1 remained at lagg0_vlan202.</p>
<p>Things I'm doing differently: all my interfaces are VLAN subifs of lagg0.<br />I can attach my (working) config.xml if needed - once I figure out how to strip passwords. Or I can send it directly to someone if needed, as-is.</p> pfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=125172013-09-17T23:45:28ZShahid Sheikhshahidsheikh10@yahoo.com
<ul></ul><p>I am seeing this too. My workaround has been to fix the assignment from the Interfaces: Assign network ports: Interface assignments tab. As far as I can tell, its always the last two entries that get incorrect assignments.</p>
<p>As far as it not happening every single time - to me it was happening every time when creating new VLANs.</p>
<p>And if you are not paying attention and reboot the firewall then the firewall doesn't come up because of interface assignment mismatch. It sits at bootup at configuring interfaces.</p> pfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=125332013-09-22T21:36:12ZAdam Thompsonathompso@athompso.net
<ul></ul><p>Not verified (and I'm not going to break this firewall <strong>again</strong> just to check it), but I also believe that at some point, editing one of the VLAN subinterfaces changed the LAG members of the parent interface; during debugging, I noticed that one reason my LAG wasn't coming back up was that only em0 was a member. I am 100% certain that em1 was also a member when I started testing, as I had verified LACP partner status on both links from the switch.</p> pfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=154302014-10-30T23:55:42ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Assignee</strong> set to <i>Chris Buechler</i></li></ul> pfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=249742016-02-06T04:56:33ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Category</strong> set to <i>Interfaces</i></li></ul> pfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=250442016-02-08T08:15:30ZPhillip Davisphil@jankaritech.com
<ul></ul><p>This looks like it has been just a plain old dumb bug - <a class="external" href="https://github.com/pfsense/pfsense/pull/2601">https://github.com/pfsense/pfsense/pull/2601</a></p> pfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=250452016-02-08T08:20:11ZPhillip Davisphil@jankaritech.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Fix #3209 editing unassigned VLAN tag can change an assigned interface To reproduce: a) Create V..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/1c32fb7e988fae89cf2da474778f39bcdd8a8656">1c32fb7e988fae89cf2da474778f39bcdd8a8656</a>.</p> pfSense - Bug #3209: editing VLAN tag on OPT interface changes LAN interface insteadhttps://redmine.pfsense.org/issues/3209?journal_id=250552016-02-08T15:55:20ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>Target version</strong> set to <i>2.3</i></li><li><strong>Affected Version</strong> changed from <i>2.1</i> to <i>All</i></li></ul><p>Thanks Phil! never happened to hit that circumstance in trying to replicate this, but that's clearly the issue.</p>