Quote from: wmagin on March 08, 2026, 08:25:39 AMHi all,The shared resources are truly impressive. It's incredibly easy to update and research solutions because Captive Portal and the KEA control agent are running on the same port.
I just come out of a session of getting 400: Bad request answers from my captive portal because I configured KEA DHCP server like discribed at https://docs.opnsense.org/manual/kea.html sprunki binding the control agent to port 8000. The 400 error came because Captive Portal and KEA contrl agent were running on the same port. As it is likely irrelevant on which high port the KEA agent should run it would be helpful for fellows not to run into the same issue if the example would show a port (for example 8080) which is not used by the default installation of OPNsense.
Just as a hint. Does this make sense?
Greetings
Wolfgang
Quote from: dseven on May 27, 2026, 08:34:44 PMHmmm...root@opnsense:~ # pkg info cpu-microcode-intel
cpu-microcode-intel-20260227
Name : cpu-microcode-intel
Version : 20260227
Installed on : Tue May 26 08:34:48 2026 UTC
Origin : sysutils/cpu-microcode-intel
Architecture : FreeBSD:14:*
Prefix : /usr/local
Categories : sysutils
Licenses : EULA
Maintainer : jrm@FreeBSD.org
WWW : https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files
Comment : Intel CPU microcode updates
Options :
RC : off
SPLIT : on
Annotations :
cpe : cpe:2.3:o:intel:microcode:20260227:::::freebsd14:x64
repo_type : binary
repository : OPNsense
Flat size : 30.2MiB
Description :
This port uses the cpuctl(4) microcode update facility to keep your Intel
processor's firmware up-to-date.
Updating your microcode can help to mitigate certain potential security
vulnerabilities in CPUs as well as address certain functional issues that could,
for example, result in unpredictable system behavior such as hangs, crashes,
unexpected reboots, data errors, etc.
root@opnsense:~ #
Quote from: nero355 on May 27, 2026, 11:37:09 PMYou could also just insert a Switch between the ONT and the Router to check if it's not some weird conflict between the two because of the NIC Chipsets :)
Quote2026 May 27 17:34:34 wan_detection info [WAN.6][WDHCP] eth1 arping to x.y.z.1 fail.
Quote2026 May 27 17:55:43 dhcpc.sh info "[WAN.6][WDHCP] bound IP: x.y.z.113"
Quote from: LaForge on May 27, 2026, 11:31:02 PMI have purchased an additional mSata disk to create the install but need some instructions.https://docs.opnsense.org/ is all you need IMHO :)
QuoteI would also like to know how OPNsense and OpenWRT differ from one another and why installing OPNsense might be an advantage?OpenWRT = Linux based
Minimum Interval = 10
Maximum Interval = 30
AdvPreferredLifetime = 60
AdvRouteLifetime = 90Quote from: LaForge on May 27, 2026, 11:31:02 PM1. Why does searching for "OpenSense" get you the netgate form which is for the pfSense product?OpenSense != OPNsense
I then get an admin telling me that I am "unlikely to find much love for OPNSense here on the pfSense forum". The why are they subverting the search results to exploit what must be a common mis-spelling?
Quote2. Why did I have to look for a link in small print at the bottom of the OPNsense website to find this forum?https://opnsense.org/ => Be Involved => OPNsense forum => DONE! ;)