Problem "Network interface mismatch"on pfSense Beta 2.0 while importing settings

toomeek

I'm going to compare XML from 1.2.3 with 2.0 and report results.

EDIT: grabbed XML from 1.2.3 to text editor. Question: how does pfSense recognize missmatch of interface? Even I cannot find MAC adress there..


         <interfaces><lan><if>re2</if>
                        <ipaddr>192.168.1.1</ipaddr>
                        <subnet>24</subnet>
                         <media><mediaopt><bandwidth>100</bandwidth>
                        <bandwidthtype>Mb</bandwidthtype></mediaopt></media></lan>
                 <wan><if>re0</if>
                         <mtu><ipaddr>82.x.x.x</ipaddr>
                        <subnet>1</subnet>
                        <gateway>82.x.x.x</gateway>
                        <blockpriv>on</blockpriv>
                        <blockbogons>on</blockbogons>
                         <disableftpproxy><dhcphostname><media><mediaopt><bandwidth>100</bandwidth>
                        <bandwidthtype>Mb</bandwidthtype>
                         <spoofmac></spoofmac></mediaopt></media></dhcphostname></disableftpproxy></mtu></wan>
                 <opt1><if>re1</if>
                        <descr>DSL2</descr>
                         <bridge><ipaddr>81.x.x.x</ipaddr>
                        <subnet>32</subnet>
                        <gateway>81.x.x.x</gateway>
                         <spoofmac><mtu><enable><disableftpproxy></disableftpproxy></enable></mtu></spoofmac></bridge></opt1></interfaces>  
         <staticroutes><route><interface>lan</interface>
                        <network>10.1.1.0/24</network></route></staticroutes>

EDIT: I successfully imported settings to 1.2.3, even if there was "Network interface mismatch" while importing. After router reboot it seems to be working - Welcome message appears, all interfaces have their IP.
So assuming THERE IS PROBLEM with Beta 2.0 version while importing settings.

jimp

The network interface matching is done by the network card device name. So in the config section you posted, it expects to find re0, re1, and re2. If it doesn't find one of these, it would say there was a mismatch.

There are no current known issues with importing configurations to 2.0. There may be something specific in your config tripping the error, but it's hard to say without seeing the config at the point when the error occurred.

If you were running OK and then changed a setting, and then saw the error, that could be different. It may be the change you made that caused a problem with the config, and the network interface mismatch was just a side effect of the real error.

toomeek

Anyone else has problem with importing setting from 1.2.3 to 2.0? Please confirm. I'm still getting this.

simby

I have problem with boot panic

jimp

@TooMeeK:

Anyone else has problem with importing setting from 1.2.3 to 2.0? Please confirm. I'm still getting this.

Can you send me your config privately so I can run some tests with it, to see if it's something specific to your config?

You can mail it to me at jimp (at) pfsense (dot) org

@simby:

I have problem with boot panic

That has nothing to do with this thread. There are already threads for the boot panic issue on amd64.

geewhz01

I have this same problem. A upgrade from 1.2.3 works fine upon the first boot, but once it finishes the upgrade if you reboot again then it comes up with the network interface mismatch each time. If I install 2.0 and import the settings I'm getting the same interface mismatch. I have not changed any settings before rebooting when the error comes up. Even if I try to assign the interfaces after reboot it keeps in a loop with interface mismatch.

Andy

jimp

@geewhz01:

I have this same problem. A upgrade from 1.2.3 works fine upon the first boot, but once it finishes the upgrade if you reboot again then it comes up with the network interface mismatch each time. If I install 2.0 and import the settings I'm getting the same interface mismatch. I have not changed any settings before rebooting when the error comes up. Even if I try to assign the interfaces after reboot it keeps in a loop with interface mismatch.

Please e-mail me a copy of your 1.2.3 configuration so I can try to replicate the problem. Send it to jimp at pfsense . org.

geewhz01

@jimp:

@geewhz01:

I have this same problem. A upgrade from 1.2.3 works fine upon the first boot, but once it finishes the upgrade if you reboot again then it comes up with the network interface mismatch each time. If I install 2.0 and import the settings I'm getting the same interface mismatch. I have not changed any settings before rebooting when the error comes up. Even if I try to assign the interfaces after reboot it keeps in a loop with interface mismatch.

Please e-mail me a copy of your 1.2.3 configuration so I can try to replicate the problem. Send it to jimp at pfsense . org.

It has been sent. If you need anything else please let me know.

Thanks,
Andy

jimp

OK I think I fixed this.

If you had the load balancer configured, the upgraded monitor IPs were accidentally getting created as interfaces. So the next reboot had interfaces that really didn't exist and had no physical hardware associated, so it believed there was a mismatch.

Hopefully the next new snapshot dated after this post (note: Not the one building now, the one after it!) should include the fix.

geewhz01

Ok thanks. I'll test tomorrow :).

Thanks,

Andy

toomeek

Finally ;) hehe
I hope my 1st post was helpfuly.

geewhz01

@geewhz01:

Ok thanks. I'll test tomorrow :).

Thanks,

Andy

This is fixed for me. THANKS!!!!