disable on boot check of config.xml
darzanebor last edited by
Long story short, I'm having some issues on devices with lte dongles as backup.
If device rebooted after configuration and great previous work it's stuck in network interface mismatch bootloop on check of configuration in /conf/ it's too early to search for dongle
So it can't go further with execution of usb_modeswitch in the end etc. etc.
so if i'm absolutely sure that i do have 100% working config 100% of time how do i disable this check on boot?
thank you in advance!!!
You could try running usb_modeswitch as an earlyshellcmd.
You might be able to switch those devices permanently using some other method. Some can.
You can prevent it halting on missing ue interfaces by adding that to this list:
But be aware that can lead to some odd behaviour if it boots up with a missing interface.
darzanebor last edited by darzanebor
Thank you Steve!!!
btw just for my understanding, is the naming of interfaces for such usb sticks permanent, ue?
and if it is, may be that would be great to add ue to that interfaces permanently?
USB Ethernet devices are renamed ue0, ue1 etc, yes.
It's not desirable to stop checking for them though. That is a physical interface. If it is assigned in the config and not present on the system the firewall should stop and ask the user how to proceed. Not doing so ends up in an unknown situation or potentially something worse like if you had multiple ue interfaces and one is unplugged you could start sending private traffic out of the remaining one if that became a different interface.
The other interfaces in that list are those that built on top of a different physical NIC and may not have been created yet at the time of the check like ppp or vpns.
There is no good way to handle this unfortunately. If the modem is in Ethernet mode you have to do something like this to avoid boot failure. If it's in PPP mode pfSense has no problem with the interface or device disappearing but the speed is limited to 3.5G (ish).
It would be great to be able to use one of the other methods like MBIM but there is no driver in FreeBSD, yet.