Bug found when deleting interfaces?



  • I ran into it 3 times, each causing me to have to yank the CF Card from my soekris box and re-image it to even get back to a usable system (ouch!!). The short story of this one is that given the configuration in another thread (http://forum.pfsense.org/index.php/topic,14840.0.html) as a starting point, if you attempt to delete an interface without FIRST removing the associated FW,NAT,AND VIP rules that are tied to that interface , pfSense will bomb, and returns the following error on both the web interface as well as the serial console:

    XML error: OPTXXXX at line [nnn] cannot occur more than once.
    (note: the XXXX is verbatim in the error message; the nnn represents a number value that seems to be different depending on which interface I happened to delete at the time.)

    When this error occurs, the GUI is rendered unusable (cannot select menu items, save, or even do a restore / reset to factory defaults; the GUI will return to that same XML error. Additionally, the console menu is also rendered unusable. Any attempted action (e.g. reset factory defaults, configure interfaces, etc) result in the error being presented, and then returning to the menu.  As mentioned, all 3 instances of which this occurred, the only resolution I had was to yank and re-image the boot disk.

    I searched the forums for OPTXXXX and I've only seen one other thread (http://forum.pfsense.org/index.php/topic,8133.msg51296.html#msg51296) with the same error, though my German is a bit rusty (ok, really, non-existent), so I'm at a loss to what's happening here…



  • Same problem here after deleting an OPT interface.

    Can't get the system working again. Need to reinstal. Exactly the same problems after deleting.

    I'm using latest version 1.2.3.

    Need to be addressed.



  • I've experienced this myself yesterday and solved it using the instruction below. Only I logged on to SSH and used the VI text editor to ammend the changes to the XML file, also I did not reboot the whole box but only the webinterface. Other then that the result will be the same.

    Bei mir trat das Problem ebenfalls auf als ich mit VLANs herumspielte (Anlegen und Löschen)
    In der .XML waren dann zwei Einträge vorhanden, einmal: optxxxx und einmal optXXXX.
    Nach händischem Löschen und Zurückspielen/reboot (via WinSCP, das funktioniert dann noch), waren GUI und Konsole wieder erreichbar.

    Translates into:

    In my situation the problem occurs when playing around with VLAN's (adding and removing)
    In the .XML two entry's are created, an optxxxx and an optXXXX.
    After manually deleting this entry and rebooting (using WinSCP, because at this time this is still functional), the WebGUI and console were accessable again.



  • The solution for the time being is to not do that.

    If you're going to be deleting interfaces, make sure you've removed all the rules and VIPs associated with that interface first.  Its a mistake you should really only make once or twice before learning.



  • @submicron:

    The solution for the time being is to not do that.

    If you're going to be deleting interfaces, make sure you've removed all the rules and VIPs associated with that interface first.  Its a mistake you should really only make once or twice before learning.

    Ah lucky me then.. I didn't create anything yet in regards to rules. After creating the OpenVPN interface this error appeared so it looks like I got away with it without breaking stuff ;D



  • ooops!

    i did the same thing just now and was looking for a solution.. i accidently removed an interface without disabling it first.. i ssh'd into the router, and ended up finding backups of the xml file in conf/backups, one directory deeper than the running config.xml. i did an ls -lrt and grabbed the latest backup, and copied it over the existing config.xml. i rebooted the router and it all came up good.. (with the configuration from before) i then disabled the interface THEN removed it.

    Very handy, i did not know it made a backup every time it did a config change! this is a case where that single xml file works swimmingly.



  • Sorry to re-open an old topic, but this behavior has bitten me multiple times….

    To clarify, simply disabling the interface (by clearing the checkbox marked "enable ABC interface") is sufficient to prevent config file break-age when deleting a vlan interface?  ???

    Or is it truly necessary to go through the entire process of removing any interface configurations before deleting?

    Would love to have a steadfast answer on this.

    We run a computer shop.  Our firewall and core router is pfsense on a 1.8ghz P4 w/ 1GB of RAM, with 5 physical interfaces, one of which hosts 16 vlans.  As workbench areas change, the network config often needs to change.  I would love to be able to add/remove vlans as needed without fear…. had to rebuild the box once over this before I learned how to restore the config by hand.

    Thanks folks...  Great system otherwise.  Wouldn't run anything else...  Love it.

    Edit:
    Running release 1.2.3 with 2.0 dashboard installed.


Locked