Topics

Hi,

I'm currently experiencing (I think) some hardware issues. My machine freezes and is fine after a reboot. Since everything is frozen the only error messages I get are whats on screen when the machine dies (there is nothing in the logs.)

At first I thought it was the SSD, but SMART statistics look fine.



Since I thought it could be the sata cable I replaced the sata cable and used a different connection on the motherboard. But the problem only seems to be getting worse. At first the machine only froze once a week, now I'm down to daily issues. These are the error messages from two different occasions:






The specs of my software and machine
Software version:
OPNsense 22.4.3_1-amd64
FreeBSD 13.0-STABLE
OpenSSL 1.1.1q 5 Jul 2022

Hardware:
Motherboard: Asrock Rack X470D4U
Processor: AMD Ryzen 5 3500X
RAM: Kingston KSM26ED8/16ME
SSD: Intel DC S3520 2,5" 480GB

All suggestions are welcome since I find the issue really hard to troubleshoot.

Hi,

I recently bought a Netgear LB2120 in order to have a simple way to have a backup internet connection. I got everything working. The Netgear is in bridgemode and the WAN4G interface I created on the OPNsense is getting a public IP, is able to ping and I've been able to add it to a gatewaygroup. However once a day the gateway fails. Turning on and of the interface fixes the problem.

First i thought this had to do withd DHCP lease time so I've been tinkering with that by adding dhcp-lease-time 14400 to DHCP client configuration -> Advanced -> Option Modifiers at the bottom of the interface settings. Tinkering around with this did not help. I also unchecked Disable State Killing on Gateway Failure in the advanced firewall settings.

Then I stumbled onto this (I'm using a T-mobile SIM) https://community.t-mobile.nl/4g-voor-thuis-568/faq-4g-voor-thuis-technische-vragen-269795.

They state on the forum that every 24 hours T-mobile gives a physical/datalayer disconnect. "The WAN DHCP client should be able to detect such a disconnect and request a new IP immediately." This seems consistent with the problems I'm experiencing. Can anyone give me some pointers on how to make OPNsense request a new IP? Or switch the interface off an on again in case of failure?

Cheers! 

I finally got around to implementing IPv6 on my network. It works great on all subnets and I score good on the connectiontest on internet.nl and test-ipv6.com. It works on Debian, Android, iOS, MacOS and Windows. However the RADVD log registers an error around every five minutes:

2021-09-29T15:03:30   radvd[80798]   sendmsg: Network is down   
2021-09-29T14:56:25   radvd[80798]   sendmsg: Network is down   
2021-09-29T14:51:31   radvd[80798]   sendmsg: Network is down   
2021-09-29T14:47:39   radvd[80798]   sendmsg: Network is down   
2021-09-29T14:39:50   radvd[80798]   sendmsg: Network is down

I'm currently running:
OPNsense 21.7.3_1-amd64
FreeBSD 12.1-RELEASE-p20-HBSD
LibreSSL 3.3.4

My ISP provides me with a /48 via DHCPv6 through the IPv4 PPPoE tunnel. On my WAN interface I selected DHCPv6 as IPv6 Configuration Type and checked the following options

Request only an IPv6 prefix *checked*
Prefix Delegation size 48
Send IPv6 prefix hint *unchecked*
Use IPv4 Connectivity *checked*
Use VLAN priority *Disabled*

On the LAN interface (and others) I selected Track Interface as IPv6 Configuration Type and selected the following options:

IPv6 interface: WAN
IPv6 Prefix ID: (whatever the VLAN of that particular interface is to make it more recognizable)
Manual configuration *unchecked*

Anyone has any idea what could be wrong? Everything seems to be in working order, so troubleshooting is a bit tough. Any help would be appreciated. Thanks!

Hi all,

I feel stupid for asking, but I've looked everywhere. I've managed to get NUT working (on version 21.7.1) via the SNMP driver. When I click the diagnostic tab I see my UPS and the data related to the UPS. When the UPS goes on battery the event is logged in the system log.

But how do I change the behaviour of the appliance? For example, if I would like the router to shut down when the battery capacity is low, or after it's been on battery for X number of minutes? My TrueNAS also uses the SNMP driver and NUT, but has a lot more options and I've managed to get it working there. The UPS wakes up all the devices once power is restored via WOL. Hoping you can help me out :) 

Hi everyone,

I switched ISP and now connect (on version 21.7.1) through PPPoE and automatically get a static IPv4 address assigned on the WAN interface and as far as I understand by design don't get an IPv6 address on the WAN interface. Because IPv6 is handled through the PPPoE-tunnel via DHVPv6 Prefix Delegation.

I assign every other internal VLAN a /64 via the Track interface setting and track the WAN interface. Depending on if I enable the "Request only an IPv6 prefix" option on the WAN interface, the WAN interface does get a link local address.

This all seems to works like charm. Clients on the LAN and other VLAN's get a IPv6 address, the interface itself (LAN etc) gets an IPv6 address. Clients register the interface (IPv4 and IPv6) as DNS server. Life is good.

This does however create a problem for unbound and upstream DNS, since the WAN interface is selected as the outgoing network interface, IPv6 Nameservers can't be used (since WAN does not have an IPv6 address). If I try to enable them the unbound log's get flooded with this message:

error: outgoing tcp: bind: Can't assign requested address

I found these posts already, all related to my problem:

How to use own IPv6 DNS server with a track LAN interface?
https://forum.opnsense.org/index.php?topic=19144.0

DNS over TLS with ipv6 forward-addresses - can't get it working
https://forum.opnsense.org/index.php?topic=19851.0;prev_next=prev#new

DNS Servers with ipv6 addresses not usable with LL ipv6 gateway addresses
https://forum.opnsense.org/index.php?topic=19746.0

They all offer insights, but I can't seem to get it working. Hopefully someone will be able to help me out  :).