[SOLVED] Interface mismatch detected. Please resolve the mismatch...

Started by romain, July 07, 2015, 06:16:16 PM

Previous topic - Next topic
hello there,

i tried to import my config after a complete reinstallation from a backup machine. I forgot to load my specific driver first and at the reboot I get this message :

Interface mismatch detected. Please resolve the mismatch and click 'Apply changes'. The firewall will reboot afterwards.

I review my configuration and reboot many times. But since, I always get the message and everything is correct now. I double check with a ifconfig which is fine.

Do I simply need to remove the file in /var/run to avoid this message ? I don't uderstand why there is an interface mismatch now.

Thank you for your help
Romain

Perhaps you can do a "restore defaults" and then import your config to solve the issue. Please try.

I just tried and even on the Factory Default mode I have this error message.

I'm trying to install opnsense again from scratch

We've changed the configuration handling a little for 15.7. If the driver isn't loaded at bootup (which one, btw.) the interfaces won't show, causing a mismatch. Would you consider using /boot/loader.conf to load the driver on startup to see if the mismatch message disappears?

I use oce.ko driver found in FreeBSD 10.1 release.

I already use loader.conf.

I remove the file in /var/run and everything seems to be fine now.


I removed the empty file interface_mismatch_reboot_needed

Since the removal I didn't get the message back.

Aha, thanks for letting me know. I purged the file generation. If backups are imported that have mismatches, then there is something wrong with your backup.... The console will try to prompt for interface reassignment on reboot in this case now. No more spurious message in the GUI. Thanks!

See: https://github.com/opnsense/core/commit/feb9e72289ddea4e2cc34deeb1a82bae0a598300


hello Franco, did you have time to look after my trouble ? Please let me know if you want me to test anything.

Romain

Hi romain,

the problem of this thread has been fixed in 15.7.2.

If you are talking about VLAN HW filtering, that is still being tested and thus not finalised (we have a preliminary fix in master but it doesn't work as well as it should).


Cheers,
Franco

Oups Sorry. This is not the correct thread. All good so thank you.