Upgrade process from old version of m0n0wall



  • So, I'm working on an old install of m0n0wall, 1.21 to be exact (Built Jan 1st, 2006, soon to turn 7 years old.)  What would be the best upgrade path to try to keep the settings intact?  Mostly worried about the mapped ports and such, I really don't want to type them in and I'm prone to typos.

    I have lots of hardware sitting around and a VMWare cluster for building easy intermidiatary machines, but in the end it'll be it on hardware, probably embedded on CF (maybe USB key.)  Current system is on CF, if that matters.

    I understand that there can be upgrade paths that allow the config of m0n0wall to be imported in to pfSense, but with such an old version of m0n0wall, does anyone know if there is there a preferred path.  Such as do I do the various upgrades of m0n0wall first, then import it to the current pfSense builds, or find a matching vintage pfSense, import the config, then upgrade pfSense?  Or something in between?

    I'm building the virtual m0n0wall instance of the same version now, so I can go all sorts of different directions, I'm just wondering if anyone has any insight or opinions?


  • Rebel Alliance Developer Netgate

    AFAIK, older versions of m0n0wall might actually import more accurately than newer ones. I haven't tried it in a while, but you should really just be able to restore a m0n0wall config.xml directly into pfSense without any adjustments.



  • @jimp:

    AFAIK, older versions of m0n0wall might actually import more accurately than newer ones. I haven't tried it in a while, but you should really just be able to restore a m0n0wall config.xml directly into pfSense without any adjustments.

    Oooh, I'll try



  • @matguy:

    @jimp:

    AFAIK, older versions of m0n0wall might actually import more accurately than newer ones. I haven't tried it in a while, but you should really just be able to restore a m0n0wall config.xml directly into pfSense without any adjustments.

    Oooh, I'll try

    Well, I think it worked, all too well.  I was working on it remotely (RDP to a Windows host inside the network), had the interfaces islanded in VMWare on vSwitches with no live external network.  Upon booting I saw a time process taking a while, so I figured I'd give the WAN port network on my LAN so that it might hit a time server, I swapped it over to my regular LAN.  This was all well and good, it got an IP via its local DHCP client.  I imported the XML backup from m0n0wall and it asked about an interface mismatch and asked me to re-assign them since my m0n0wall had an OPT interface (not that it was doing anything) and my VM version only had LAN and WAN.  I checked the console and WAN on the top on EM1 and LAN on the bottom on EM0.  I matched that up to the web interface and clicked save.  Then I lost RDP, looking back, they were in a different order, LAN was on top on the web interface, so I just put the LAN interface live on my LAN and since the import seemed to work perfectly, it has the same Gateway address as my physical m0n0wall router.

    I can ping the m0n0wall router's external interface fine, but I can't get to anything inside and I don't put the web login on WAN.  I'll have to check on it when I get home, but considering what happened, I think it probably worked.


Locked