It's not line 221 of the config, but line 221 of rules.debug, which appears to be a generated file based on the XML restore file.
No matter how we go about restoring on the 2.0 platform from backups made on the 1.2.0 platform (i.e., backing up specific portions from 1.2.0 -- aliases, firewall rules, nat -- and restoring them individually on 2.0; restoring only specific portions of the larger config) the same errors occur. The only way I was finally able to get around this was by setting up another 1.2.0 machine (I used a Parallels VM), restoring the 1.2.0 config, upgrading to 2.0, then exporting that config and restoring the desired portions (aliases, firewall rules, nat) to the desired server. Sam Pfanstiel S4F, Inc. supp...@s4f.com 888-390-2224 On Sep 28, 2011, at 9:30 PM, Chris Buechler wrote: > On Wed, Sep 28, 2011 at 9:06 PM, Sam Pfanstiel <s...@s4f.com> wrote: >> I am trying to move from one pfSense server, which is in production and >> running 1.2.0, to a newly configured server that is running a fresh install >> of 2.0. However, the backup from the 1.2.0 server will not "restore" on the >> 2.0 server. I am receiving errors that resemble: >> >> 02:05 - [filter_load]There were error(s) loading the rules: >> /tmp/rules.debug:221: syntax error >> >> It sounds like the XML rule format from the 1.2.0 config are not compatible >> with how 2.0 expects to see it. Is there a conversion utility that will >> output a configuration file with the appropriate syntax? >> > > That's automatically handled. There is a problem of some sort in the > config causing that, what's on line 221 in that file? > _______________________________________________ > List mailing list > List@lists.pfsense.org > http://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
