Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - chtse53

#1
Updated to 24.7.10_2 and the NAT reflection behavior returns to what is expected.  Not sure what caused the first observed problem with 24.7.10_1.  Anyway, problem is gone.
#2
Some webservers are not accessible inside LAN but accessible from the internet after the update.  Reverting to 24.7.9_1 solved the problem.
#3
I didn't have this WAN_DHCP6 gateway offline problem after update to 24.7.3_1 but it occured after updated to 24.7.4  I tried you trick of check/uncheck the "Disable Host Route" option and didn't solve the problem.  I also tried restarting the cable modem without solving the problem. So far, it appears that no one else is seeing this problem.

Edit:
After reconfiguring WAN interface, DHCPv6, the problem went away.   Looks like the problem was due to misconfiguration.
#4
This is the error message when NetData was running on 23.1.2: "apps.plugin   pid 1433 netdata states parent 1, but the later does not exist." The error message appeared persistently.
#5
After update to 23.1.2, NetData CPU usage jump to ~200% as shown in top. Opnsense is running in a Hyper-V VM. The host overall CPU usage jumped from ~12% to persistently over 50%.  After uninstalling NetData, CPU usage was back to normal.
#6
I have similar problems and the logs looked similar too.  The ethernet detachment of both WAN and LAN occurred around the same time.  I was wondering whether it was due to the driver for my I225v3 NIC (2.5G NIC). However, it looks like the problem occurs with igb# NIC too.  Some previous posts about similar problems mentioned associations with MAC address spoofing, IPS mode which are present in my case.  There could be other possibilities apart from NIC hardware problem. Recently, Suricata logged a lot of "ET DOS Possible NTP DDoS Inbound Frequent Un-Authed MON" attacks and the ethernet detachment incidences appeared to occur sometime after these attacks. Wonder if that could be a trigger for the ethernet detachment incidence.
#7
Mine frequently renews the wan ip address, which didn't change, and caused unbound to restart.
#8
Same issues here.  After uninstalling HAProxy, ACME and certs appeared again as before upgrade.
#9
Turn-out MS Edge Browser also worked after deleting the cookie for my opnsense server.  Just not sure why it affected only the "log file" of Unbound.  I can view other system log files without problem.
#10
Thanks for the info. 

I was using MS Edge browser and got non-responding page on the "log files" tab.  I changed to Chrome browser and it worked.  It could be a browser problem or a cache problem.  I would clear the Edge browser cache and try again.
#11
 # ls -lah /var/log/resolver.log
ls: /var/log/resolver.log: No such file or directory
#12
After upgrading from 22.1.10 to 22.7, the log file page of Unbound DNS was not responding.
#13
22.1 Legacy Series / Re: os-ddclient
July 25, 2022, 02:43:38 AM
Quote from: athurdent on July 24, 2022, 01:01:17 PM
Late to the party, sorry.

Could not find a way to properly set the IONOS API update URL. It just needs to call that custom URL, nothing else. ( https://www.ionos.de/hilfe/domains/ip-adresse-konfigurieren/dynamisches-dns-ddns-einrichten-bei-company-name/ )

Also, even if it worked, no way to update it to a GW group anymore?

I am also using IONOS API.  Since it is as simple as calling a custom URL, I just created a custom cron job to do it. Need not bother about the os-ddclient. 
#14
You are using realtek NICs.  I suppose you have followed the instructions brefore upgrading: "The Realtek vendor driver is no longer bundled with the updated FreeBSD kernel.  If unsure whether FreeBSD 13 supports your Realtek NIC please install the os-realtek-re plugin prior to upgrading to retain operability of your NICs."