Messages

I run on a Fitlet2 and cannot maintain serial console connection after the OS boots.  I am trying to deduce if OPNsense is lacking some driver I need to load or what.

I enabled serial console redirection in the BIOS as well as a setting that keeps it enabled after the OS loads.  I can see the POST and get into BIOS over a serial putty session.  Once the bootloader starts the OS, before I get the OPNsense ascii art splash screen, the serial session stops updating.

I also tried an Ubuntu Server USB boot image and after grub picks the OS, the serial console stops updating. 

I am looking for anyone that has successfully maintained a serial session on a Fitlet2 after OPNsense loads. 

[If you are using a Dynamic DNS address, make sure you go to System: Settings: Administration and put that dynamic DNS address in the "Alternate Hostnames" field]

I have a softphone app on my smartphone that connects to a cloud based PBX.  The PBX is a common Broadsoft platform.  If I open the app at home, behind my OPSense firewall, I get errors that it cannot register to the PBX.  If I turn off wifi or get on any other wifi network, it registers fine.  I've been hunting the solution off and on for weeks.  I was looking in the wrong direction since I assumed it had to do with some network topology nonsense on my end.  The solution turned out to be super simple.  I found it in the very last sentence of this article.

"If you are using a Dynamic DNS address, make sure you go to System: Settings: Administration and put that dynamic DNS address in the "Alternate Hostnames" field."

That's all I did.  I added my DynDNS hostname to that field and it was fixed. 

[I was able to SSH in and successfully run the installer that way.]

This is just an FYI for anyone who runs into this issue.

I got the a segmentation fault error doing a clean install of 20.1 on a J3455 Fitlet2.  The error appears when I hit "Accept these settings" at the very beginning of the graphical installer. 

This was while using a directly attached monitor and keyboard.  I did some research and found this article which pointed me in the direction of the root cause having something to do with integrated graphics.  The command in that article doesn't do anything.  I then found somewhere else, I think on this forum, that I can bypass this error by installing via SSH. 

I booted from the USB stick and assigned interfaces and IP to the LAN.  I was able to SSH in and successfully run the installer that way.

I had been running OPNSense on this hardware for years and doing in-place upgrades without a hitch, including all the way to 20.1.8.  I did a ton of experimentation without saving my good config so I just wanted to start fresh with a clean build. 

Just a reminder for Fitlet2 users, update to the latest BIOS and disable all 3 SCC components in the South Bridge settings. 

I also just got it working on my Fitlet2 as well.  I'll recap what I had to do in case it helps anyone else.

• Update BIOS to FLT2.0.40.01.00 using the crappy instructions on the Fitlet2 wiki.  The missing step in their instructions is that once you get to the SHELL prompt you have to mount the file system by typing

Code Select Expand

FS1:  Then you can run the command that actually updates the BIOS:

Code Select Expand

flash flt2.bin

• Change BIOS settings to facilitate FreeBSD.  These Fitlet2 wiki instructions are also clumsy.  The OS setting is on the main page of the BIOS and the UFS setting under SCC is not present, but that seems to not matter.


• I used the VGA memstick installer for OPNsense 18.1.  I used rufus to write the stick.  I am not sure if any settings here matter, but I remember selecting MBR instead of GPT before I selected the image file.  Might be irrelevant.


• I followed the advice summed up in jelly-ck's post above, setting the 4 required hints to boot on this hardware.  I had to do all 4 and no others.  I was already familiar with these steps from working with pfsense. I am not proud to say how many times I've typed them.


• I ran the installer then rebooted, once again doing the 4 hints so it would boot all the way.  At the console, I set an IP and went to the web interface from another PC.  I made the hints permanent in the Tunables area that Franco points out above.  This worked great, and I like not having to directly edit the loader.conf.local file.  I applied the tunables and rebooted.  Worked like a charm.


• I pulled the hdmi and keyboard cables out and did a headless reboot from the web GUI.  Works great.  Cold boot to interface reply is 30 seconds.  Very happy.

Good luck!