Messages

Hello all
Did a clean install of 24.1 on a pcengines.ch apu4. Install progressed normally and display was normal. Did not load old config initially and used default password to log on from the console. Using the GUI was normal. Used the GUI to load the old config file previously used on 23.12.5.

Rebooted the machine from GUI. System booted normally but the console display did not progress beyond the SHA display and the keyboard locked. The GUI runs fine and the machine can be controlled from there.

Running Minicom for console access.

Thank you for the reply and apparent solution to the problem. Checking the
systems>settings>administration>console shows that all lines are identical
except for the line "USB based serial - use USB based serial ports" was checked
in my installation of 23.7.6 and not checked in 27.7.5. Removing the check
from this line in 27.7.6 restored the serial console to normal operation.

I am running two apu4d4 pcengines boards. These are used alternatively when opnsense versions
are introduced. I use minicom 2.8 running on an old 32 bit asus eee pc 900 (32 bit debian OS)
for the video terminal serial console.

Running 23.7.5 on one of the apu4d4 and minicom package works fine with the serial console
performing as expected. When the other apu4d4 is run with opnsense 23.7.6 the serial console
performs as expected (displays the boot process steps) until the boot process passes the
botton of the second hash line. At this point the display stops and does not show the log on steps.
Also anything typed  on the serial display is ignored. When running 192.168.1.1 on one of the lans
provides full and normal access. The system seems to be running normally with no obvious faults.

I'd like suggestions on how to diagnose this problem since the serial console is unusable. The
hardware is the same in both cases so it must be a software issue. I don't think it is the apu4d4
boards since they have performed well for a significant period of time.I don't think its the
minicom package since I have successfully used this on pcengines apu2 boards with no problems.

Running 23.1.5_4 on a pcengines apu4d4. I have a problem with the lan connections
disconnecting and reconnecting without a pattern. Don't think the problem is hardware since I have two
apu4d4 the second one in hot spare mode and switching between hardware doesn't seem to help.

Like to know what what logs and diagnostics I should be using to establish reasons for this behavior.
I have not had the problem in previous opnsense versions

Having a similar problem running 22.1.8_1. Lose the IP after running about four/five days. Before that running 22.1.8 there were no problems. As above by cardinal no config changes were made.

I am running with 22.1.8 now. Will have data on possible failure caused by 22.1.8_1 in four or five days service time.

Running 22.1.6 on a pcengines APU.4D4. Recently dropped pfsense 2.6.0 and began using Opnsense 22.1.6. Need direction configuring ports on opnsense for my ooma (VOIP) telephone.OOMA worked fine with pfsense 2.6.0.

OOMA/VOIP IP assigned to by router 192.168.2.94
ports for outgoing UDP/TCP 53, 1194, 1294 must be open
ports for outgoing TCP  80, 110, 443 must be open
ports for outgoing UDP  67,123, 3480 must be open
ports for UDP range 10000 to 20000 must be open
ports for imcoming UDP 10000 to 20000 must be open

further detail can be found at:
https://support.ooma.com/home/advanced-connections-and-service-ports/

I am a new user of opnsense. Constructive comments and suggests would be appreciated.

Franco, thanks for the information. Have inserted the DNS and now get the message on the console during boot:
"Running wireguard-go is not required because this kernel has first class support for wireguard. For information
on installing the kernel module, please visit  https://www.wireguard.com/install". I did not see any information on
that site referencing opnsense 22.1

Like to know if this impacts my install?

Doing a clean install of 22.1 and using https://docs.opnsense.org/manual/how-tos/wireguard-client-mullvad.html
points to "set the DNS to 193.138.218.74. This is the one MulladVPN provides for privacy".
Like to know where that is set in the install since it does not seem to be in the VPN/Wireguard/Local page

Done a 22.1 clean install. Previously using 21.7.8 and loading the old
config file. Getting messages on the console as follows:

Quote
em0:link state changed to UP
em0:link state changed to DOWN
em0:link state changed to UP
em0:link state changed to DOWN
arpresolve: can't allocate llinfo for 70.44.90.1 on em0
em0:link state changed to UP
em0:link state changed to DOWN
em0:link state changed to UP
em0:link state changed to DOWN
em0:link state changed to UP
em0:link state changed to DOWN
arprequest_internal: cannot find matching address
unquote

The above just repeats every few minutes

em0 is my WAN interface. There does not seem to be a problem with the
other interfaces.

Would appreciate guidance on the best steps to diagnose what is going on

I was doing an upgrade to 21.7.7 and somehow managed to lock myself out of the console but am able to use the GUI to get into the dashboard. Hope the question is posted to the correct sub forum.

Perhaps someone can point out how to enable the console.

:-[

Waited 10 days from original post. Now running 21.1.5. Having the same issue as listed at the top of this page. Please advise how to proceed.

Running OPNsense 21.1.4-amd64. After adding the repo mimugmail's community repository then System/Firmware/Plugin run update I get os-adguardhome-maxit (misconfigured). At that point I can not advance to Services and addition of AdGuardHome.

Two questions: A- Like to know why the plug is might be misconfigured. B- How best to modify the configuration file so it is not misconfigured.

Thanks in advance for the help