Interface missmatch
-
I have upgraded from September to October 18 snapshot and on restart I keep getting Interface mismatch. I have tried to reconfigure this but it is caught in a permanent loop. I am running the 32bit version on a via system.
Just above that it says starting device manager can't find ukbd0: device busy
I am using interfaces rl0, rl2 and rl3.
-
I found the issue. In the <interfaces>section there was a random <rl3>that got in. Who knows how.</rl3></interfaces>
-
Snort bug. Make sure you uninstall that package and reinstall it.
-
Cool thanks it took me a wail to find the problem that was causing it but at least it is fixed now.
-
Same issue here:
Thanks to this topic, I've fastly found a weird <vr0>in the <interface>section. Removing it, solved the issue. ;Don restart I keep getting Interface mismatch. I have tried to reconfigure this but it is caught in a permanent loop. I am running the 32bit version on a via system.
This also happened to me and because of the infinite loop I was forced to reinstall the pfense box :'(
Here are the steps i've performed:
(10) update using the Web GUI
(20) Auto Reboot
(30) Shell says there is an "Interface missmatch" and ask to configure interfaces
(40) I correcty resetup the interfaces
(50) Shell says "writing config File"
(60) Goto 30 :'(May i suggest a "(55)" step saying something like "I failed to write a valid config file, Would you like to
- Reset the config file: Type X (or a way to go back to the Main Pfsense Menu)
- or try again: Type Return
This would avoid having to fully reinstall the pfsense box, whenever the config file get corrupted…. 8)
BTW May be there is a way to return to the pfSense console setup menu (to be able to reset the configuration to factory default), but I was unable to find it ???
Best regards,</interface></vr0>