1.2.3 to 2.0 upgrade loses vlans/interface configuration
-
Please give full error message and config.xml if possible.
-
Here is the section of the log when it jumps into the interface configuration after the "network interface mismatch"…
*** Start LOG ***
The interfaces will be assigned as follows:LAN -> vr1
WAN -> vr0
OPT1 -> vr2Do you want to proceed [y|n]?y
Warning: Cannot use a scalar value as an array in /etc/inc/config.console.inc on line 322
Warning: Cannot use a scalar value as an array in /etc/inc/config.console.inc on line 323
Warning: Cannot unset offset in a non-array variable in /etc/inc/config.console.inc on line 375
Warning: Cannot use a scalar value as an array in /etc/inc/config.console.inc on line 378
Warning: Cannot use a scalar value as an array in /etc/inc/config.console.inc on line 379
Warning: Cannot unset offset in a non-array variable in /etc/inc/config.console.inc on line 385
Warning: Cannot use a scalar value as an array in /etc/inc/config.console.inc on line 390
Warning: Cannot use a scalar value as an array in /etc/inc/config.console.inc on line 392
Warning: Cannot unset offset in a non-array variable in /etc/inc/config.console.inc on line 399
Warning: Cannot unset offset in a non-array variable in /etc/inc/config.console.inc on line 402
Warning: Cannot use a scalar value as an array in /etc/inc/config.console.inc on line 403
Writing configuration…
Warning: Cannot use a scalar value as an array in /etc/inc/config.lib.inc on line 488Warning: Cannot use a scalar value as an array in /etc/inc/config.lib.inc on line 494
Warning: Cannot use a scalar value as an array in /etc/inc/config.lib.inc on line 495
Warning: Invalid argument supplied for foreach() in /etc/inc/xmlparse.inc on line 211
done.Network interface mismatch -- Running interface assignment option.
Valid interfaces are:
vr0 00:0d:b9:1f:db:90 (up) VIA VT6105M Rhine III 10/100BaseTX
vr1 00:0d:b9:1f:db:91 (up) VIA VT6105M Rhine III 10/100BaseTX
vr2 00:0d:b9:1f:db:92 (up) VIA VT6105M Rhine III 10/100BaseTXDo you want to set up VLANs first?
If you are not going to use VLANs, or only for optional interfaces, you should
say no here and use the webConfigurator to configure VLANs later, if required.Do you want to set up VLANs now [y|n]?
*** End LOG ***
-
I added some more checks for the errors you mentioned to code so you can try with latest snapshots.
But without posting the config i cannot tell.
-
Unfortunately, the new build with the additional debug messages did not help. Still exactly the same errors when the router boots into the image and then restarts assigning interfaces. Please find below the extract of the 1.2.3 config.xml file. Anyone any ideas?
<interfaces><lan><if>vr1</if>
<ipaddr>192.168.100.1</ipaddr>
<subnet>24</subnet>
<media><mediaopt><bandwidth>100</bandwidth>
<bandwidthtype>Mb</bandwidthtype></mediaopt></media></lan>
<wan><if>vr0</if>
<mtu><ipaddr>dhcp</ipaddr>
<subnet><gateway><blockpriv>on</blockpriv>
<blockbogons>on</blockbogons>
<disableftpproxy><dhcphostname><media><mediaopt><bandwidth>100</bandwidth>
<bandwidthtype>Mb</bandwidthtype>
<spoofmac></spoofmac></mediaopt></media></dhcphostname></disableftpproxy></gateway></subnet></mtu></wan>
<opt1><if>vr2</if>
<descr>OPT1</descr>
<bridge>lan</bridge>
<enable><ipaddr>dhcp</ipaddr>
<subnet>32</subnet>
<gateway><spoofmac><mtu><dhcphostname></dhcphostname></mtu></spoofmac></gateway></enable></opt1></interfaces> -
It may not be relevant, but you shouldn't have DHCP client enabled on a bridged interface (OPT = vr2).
(I'm presuming that what the <ipaddr>dhcp</ipaddr> means.)
-
I did change it, but there is no better behavior during upgrade to 2.0 Beta 4 (latest snapshot 101224).
-
Do you see any error messages or warnings during boot? (especially PHP errors or warnings)
-
Please put the config without private info either here or mail to me.
Otherwise we cannot help on this. -
I seen a hint in another post concerning the usage of special characters (Umlaute). I went through my config and finally found one such character. After this correction, the upgrade to the latest Beta 5 went smoothly. I am currently just trying to rebuild the openVPN config which was apparently not converted due to a completely different way of handling certificates (I assume). But otherwise I am now on pfsense 2.0! Thanks for pushing me with hints and questions.
I will report on the outcome as soon as I have further news.
Felix
-
OpenVPN should have been converted. What didn't work?
We have a lot of upgrade code that should be taking care of importing what you have into the new certificate manager.
And also, what field had the special character in it? I assume some kind of description field, but where in the config?
The more issues we can smooth out for people, the better.
-
Dear Jimp,
just sent a PN with the config file. Indeed, the problem was a description field where I use "Büro" instead of "Buero". But unfortunately, other problems were buried. So after messing around for almost a day, I went along and did a manual clean config by copy/paste data from the old config.xml file. 2hours later I had it again up and running. Currently I am just struggling with setting up OpenVPN again since the masks look different and request different information than outlined in the official book…
Felix
-
Yeah importing an OpenVPN connection is a bit more complex now (import the CA, then import the Cert, then re-create the connection) but it can be done. You probably could have fixed that one special character in the original config and re-run the upgrade. I didn't see anything else wrong with the config at a quick glance.
-
I did as you suggested but I was not able to fix it with the import. I also tried to partially import piece by piece over a virgin installation. That did not work out either. Hence I was really lost and needed to have the link up and running again.
But seriously: I don't want to complain. Overall the pfsense router is a great piece of SW on the ALIX boards, and also very low power. This is exactly what I was looking for.
