1.2.3 to 2.0 upgrade loses vlans/interface configuration
-
It might be the same problem from this thread: http://forum.pfsense.org/index.php/topic,28202.0.html
I have that guy's config but haven't had a chance to look it over yet.
-
lol…. jimp. that's my post. i thought you had forgot about it, but apparently not. sorry for the double post's. won't happen again.
-
yeah… not sure where my brain was. Probably lost between 50 tabs. %)
-
I merged the threads together so it wouldn't be a duplicate. :-)
-
Looking back and this and trying it out, my ALIX upgrades fine with VLANs. I suspect you were hitting this issue due to having the snort package installed:
http://forum.pfsense.org/index.php/topic,28543.msg150170/topicseen.html#msg150170And that should be fixed now on newer versions of snort.
-
i was thinking the same as snort cocked up on resetting to the original slice but…..
i've tried again tonight and no success.
i've cleaned out my packages and package config and at one stage thought it was down to an old vnstat package but......on a reboot
"invalid argument supplied for each() in /etc/inc/util.inc on line 708" and there ain't no line 708 -
At this point I would just do a fresh image of the card with 2.0 and restore your configuration. Something has to have gotten corrupted somewhere along the line.
To be safe, I'd remove the package data from the backup file.
-
aha…...
are you saying i can do a fresh install and then use my 1.23 config to bring the v2 to how it was under v1.23? i didn't realise that you could do that.if so, can't i just temporarily configure a lan at the moment after the upgrade and then import the 1.23 config?
-
If that was a recent snapshot, that error would suggest that you have no interfaces section in your config.xml at all when it is happening or that there was an error parsing config.xml.
-
yeah, backup the config, write out a card with 2.0, drop that in and connect to LAN, then restore config, and when it reboots it will be ready with all your other configuration. Still not sure I'd trust packages in that scenario just yet but it might be safe.
-
just checked and there are interfaces there. i'll keep ploding on just to see incase it helps anybody later on but any help or pointers would be appreciated.
-
Maybe something invalid got into your config.xml somehow so that it wasn't able to parse it? Something could somehow be going wrong with the config upgrade process, making a configuration that causes it to error out when parsing. If this is happening, I think it would cause the equivalent of having a blank config.xml.
-
ummm….
i'll probably have to go to a fresh v2 as jimp says but that's giving up to me so i wanna keep trying. i notice when it boots up it looks for packages, says it reinstalling packages and then says done. and there's no packages there in the gui or when you run pkg_info.
what i did try was clearing all my backups & cache out and then upgrade to v2.
still the same so i then name the interfaces vr0, vr1 & vr2 (thinking i'd get it going and then do the config import) but then i got:
cannot use a scalar value as an array in /etc/inc/config.console
cannot unset offset in a non-array variable in /etc/inc/config.console -
Have you kept a backup of the working configuration from before the upgrade so that you can reproduce this at any time?
-
yes, i backup using an "all" & "all without packages" config. still the same result.
-
sorry to bring this up again but i'm looking for advice as we draw ever closer to v2.
i tried this again the other night (with latest snapshot) and still had the same issue. so i suppose the only way i'm gonna get v2 going is with a fresh install.
problem is, pfsense is configured with 5 vlans, ipsec tunnels etc and i don't want to lose the config or start from scratch.can i do a fresh install and then restore from config?
i'm thinking of doing multiple backups eg one for packages, one for firewall, one for ipsec etc and restoring them (if i can) one by one in case there is anything in there.
would this be the way to go?i don't want to buy another industrial grade cf card so i may use a normal cf just to see if it goes prior to switching over to the working card.
-
Please email me your config that won't upgrade. cmb at pfsense dot org
-
sent the config. thank you for your time with this.
-
I see exactly the same behavior at my side: after the upgrade the boot process asks for assigning interfaces which fails due to the "scalar problem". I was working for some time with 1.2.3 but had problems with voip phone disconnects and since nothing helped so far my last resort was giving 2.0 Beta 4 a try. But as reported, no luck so far. I would be really happy to get some help with the upgrade process…
Thanks a lot!
-
Please give full error message and config.xml if possible.
