Problem with interface configuration (Default interface not found)

Started by Seaside, March 30, 2020, 12:58:13 PM

Previous topic - Next topic
Hi!

I'm trying to migrate from Pfsense to Opnsense. My current problem is that I can't add my VLAN interfaces.
I have added the VLANs, but when I assign it to a new interface and reboot, I get the message:

"Default interface not found -- Running interface assignment option"
When that is done my WAN and LAN are swapped and I have to do manual assignment.

The hardware I'm using is a Qotom with 4xIntel nics, I can assign all NICS and boot without problem, but as soon as I add a VLAN via LAN this happens. This setup works fine in pfsense.

I've tried adding delay in /boot/loader.conf.local where I have added the entry:
kern.cam.boot_delay="10000"

But that does not help.

Would be really grateful for any pointers, since I'm really looking forward to start using opnsense!
It's a bit of mess to migrate since I don't want to cut off internet here at home for too long, so
doing dual boot pfsense / opnsense with two different ssd:s.

Regards S

Hi S,

You can set "Prevent interface removal" for your VLANs although it is strange that they would disappear on boot (it suggest there is either a stale entry in config.xml with an unknown interface or that the NICs are detached for some reason, maybe lazy load of drivers?


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

Thanks for the reply!

That helped!

I suspect I have a somewhat strange config after some imports of pfsense config.
I had also the wrong static ipv4 config for the interface.

Change from 10.0.30.1/32 to 10.0.30.1/24

(for Vlan 30).

Regards S.

Could be, wouldn't hurt to revisit your config.xml <interfaces/> section for stale entries just to be sure.


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT