"Quote from: pfry on September 30, 2025, 05:29:42 AMWhy do you ask?I was just wondering if there were any functions that OPNsense used that benefited from AVX-512? I remember that AES-NI is used, but I could not remember the other.
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.
Pages1
#1
Hardware and Performance / Re: CPU Extensions & Technologies (Instruction Sets) : AES-NI, AVX-512, etc.
September 30, 2025, 04:13:02 PM #2
Hardware and Performance / CPU Extensions & Technologies (Instruction Sets) : AES-NI, AVX-512, etc.
September 29, 2025, 04:25:03 PM
Please forgive my poor websearching abilities. Is there any benefit to having AVX-512 in the context of OPNsense? Did I get that mixed up with AES-NI?
#3
General Discussion / Re: Problem: Modem - OPNSense MAC Binding? Dynamic IP WOW ISP USA
August 28, 2025, 02:20:20 PM
Other home-users who have ISPs with dynamic IPs, does OPNSense automagically adjust and acquire a new IP assignment for you (after a blackout/servicing/what-have-you)? Is there some setting I'm not seeing?
If I am connecting my modem (in bridge mode) to my OPNSense box, what is the order of booting & timing for doing so?
Is there a function/button in OPNSense to tell it to "REFRESH" its DHCP settings/assignment from the modem/ISP?
Interfaces -> Overview -> WAN "Reload" ...what does that do specifically?
If I am connecting my modem (in bridge mode) to my OPNSense box, what is the order of booting & timing for doing so?
Is there a function/button in OPNSense to tell it to "REFRESH" its DHCP settings/assignment from the modem/ISP?
Interfaces -> Overview -> WAN "Reload" ...what does that do specifically?
#4
General Discussion / Problem: Modem - OPNSense MAC Binding? Dynamic IP WOW ISP USA
August 27, 2025, 02:31:03 PM
Hi,
I tried websearching the issue. This is my first experience using my own PC firewall/gateway/router. I hope it is a setting issue.
I have a small Lenovo 1-litre PC with a 4-port Intel NIC. My router is a Motorola MG8702. My ISP is WOW!. I am in the United States.
OPNsense 25.1.7_4-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16
When I first set up the system a few months ago, I first encountered the issue. When booting the OPNSense system with the modem in bridge mode, the system absolutely refused to (not sure the technical term) "bind" to the modem and be granted the IP address -long stall and timeout when it was booting through the "configuring WAN" (don't remember exact term) bit. So, it would finish booting, but not have a WAN connection. I tried different ports on both pieces of hardware, and rebooting/restarting both systems over a dozen times. I ended up calling Motorola, thinking it was a MAC binding issue. The chap said everything should be automatic on that system and walked me through rebooting it with a Linux live distro (I should be ashamed that I did not try that). The same Lenovo (OPNSense) system, worked fine booting a Linux live distro and letting the modem bridge the IP to it. So all I had to do was just reboot the system into OPNSense, and it worked perfectly.
Two months later, my ISP went down while they expanded in the neighborhood. I assume I got a new (dynamic) IP. The system needed to be restarted. I was back to the initial problem. OPNSense refuses to acquire/bind to the modem. I have to drag a monitor, keyboard, mouse, and Linux live USB distro into the room to boot a live distro to get the PC & modem to bind. Boot into Live Linux distro. Check that the Internet works. Reboot into OPNSense. Fine.
This seems like an OPNSense issue or modem compatibility issue. Surely I am not the only one to experience this?
I tried websearching the issue. This is my first experience using my own PC firewall/gateway/router. I hope it is a setting issue.
I have a small Lenovo 1-litre PC with a 4-port Intel NIC. My router is a Motorola MG8702. My ISP is WOW!. I am in the United States.
OPNsense 25.1.7_4-amd64
FreeBSD 14.2-RELEASE-p3
OpenSSL 3.0.16
When I first set up the system a few months ago, I first encountered the issue. When booting the OPNSense system with the modem in bridge mode, the system absolutely refused to (not sure the technical term) "bind" to the modem and be granted the IP address -long stall and timeout when it was booting through the "configuring WAN" (don't remember exact term) bit. So, it would finish booting, but not have a WAN connection. I tried different ports on both pieces of hardware, and rebooting/restarting both systems over a dozen times. I ended up calling Motorola, thinking it was a MAC binding issue. The chap said everything should be automatic on that system and walked me through rebooting it with a Linux live distro (I should be ashamed that I did not try that). The same Lenovo (OPNSense) system, worked fine booting a Linux live distro and letting the modem bridge the IP to it. So all I had to do was just reboot the system into OPNSense, and it worked perfectly.
Two months later, my ISP went down while they expanded in the neighborhood. I assume I got a new (dynamic) IP. The system needed to be restarted. I was back to the initial problem. OPNSense refuses to acquire/bind to the modem. I have to drag a monitor, keyboard, mouse, and Linux live USB distro into the room to boot a live distro to get the PC & modem to bind. Boot into Live Linux distro. Check that the Internet works. Reboot into OPNSense. Fine.
This seems like an OPNSense issue or modem compatibility issue. Surely I am not the only one to experience this?
Pages1
