Import config from 1.2.3 in 2.x
-
Hello,
we´re using two 1.2.3 in carp mode and want to change the hardware, because they are about 3 years old.
The "old" 1.2.3 does not recognise the new NICs, so we installed the 2.x. GUI-Import of the config dows not work.
Are there any chances to import the config (there are about 150 rules and many NATs)?Greets
Fred -
Import of 1.2.3 configurations into 2.0 installs is supposed to work. What version of 2.0 did you install?
Please provide more details about "GUI import does not work". The import reports an error? after the import the system does behave like the 1.2.3 system? (If so, in what way?) etc
-
Hi, sorry, I mentioned that normal import isn´t planned to work as of different structures. So i did not gave the following infos:
It is 2.0-RC3 (i386), built on Tue Jun 21 16:50:25 EDT 2011 on an Intel platform, and I choosed "Restore area: all". The reaction is: "The following input errors were detected: The configuration could not be restored."
Next try was "Restore area: Aliases". No comment, I did a reboot, but no Aliases. Same result with "DNS-Forwarder".
In Config-History:8/8/11 08:25:23 admin: Restored aliases of config file (maybe from CARP partner)
8/8/11 08:20:00 admin: Restored dnsmasq of config file (maybe from CARP partner)I downloaded the actual config from the 2.0, non of the "imported" configs in it.
The backup-file works fine after import in an 1.2.3, it is "Backup Area:All", without package information.
Thanks for any ideas.
Fred
-
You have to restore a 1.2.3 config to 2.0 as a whole - you cannot just import sections when upgrading.
-
You have to restore a 1.2.3 config to 2.0 as a whole - you cannot just import sections when upgrading.
I tried to restore the WHOLE config:
It is 2.0-RC3 (i386), built on Tue Jun 21 16:50:25 EDT 2011 on an Intel platform, and I choosed "Restore area: all". The reaction is: "The following input errors were detected: The configuration could not be restored."The second try was to import just a part.
-
Something about the config file is likely invalid then. Most likely culprit is international characters in the config, but it could be that something else has gotten mangled in the config that made it invalid as well (has it been hand edited at all? copied/pasted into some other format that might have changed the file to something other than plain text?)
Run the config through something like xmllint and it'll probably turn up an error.
If you want me to take a look at it, send me a copy at jimp (at) pfsense [dot] org.
-
Hi,
yesterday i gave it a new/last try.
I imported a 1.2.3 config in an other new 1.2.3 and of course all was fine. Than i tried to import the same config in a new 2.x and: it works.
Different to my previous tries was the target: first it was a 32-bit 2.x from July, yesterday it was a fresh 64-bit.
No idea, wat was wrong. Anyway: i will have a look at it, because we will have to update some machines in the next months.
Thanks for any help.
Fred -
Hello, I was just about to post about a very similar question, hope it's fine chiming in here.
I'm going to set up a new pfSense V2.0 RC3 PC, and plan to import a configuration from another installation which has pfSense 1.2.2 and different network cards (though they are two in both new and old machine).
Is this import scenario supposed to work (of course correcting IPs, network cards settings and other relevant settings after import)?
Thanks,
Mario -
Yes, that works fine. After you restore it will prompt you to reassign the network interfaces, once you save/apply it will reboot with the restored settings.
