Messages

Thanks for letting me know. I'll follow the issue there

Hi,
I have 2 IP cameras that are using a static IP address (no dhcp reservations, just a static address).
I can see both of them in the 'Leases DHCPv4' section of the Kea service but according to the UI, both of them have the same MAC address...
I had a look in the Interfaces->Diagnostics->ARP table and the MAC addresses are (correctly) different.
Any idea what's happening?
Thanks

Hi,
I've configured the new DHCP Kea server but when I start it I see this warning in the log:

Code Select Expand



DHCP4_CONFIG_SYNTAX_WARNING configuration syntax warning: /usr/local/etc/kea/kea-dhcp4.conf:238.10: Extraneous comma. A piece of configuration may have been omitted.


I had a look at the file and indeed I noticed that an extra comma was added after the square bracket that closes the
"subnet4" array.

I pasted the file in a JSON linter and it was reported as invalid. I removed that comma and the JSON was marked valid.
I assume that the Kea warning is reporting the same issue..
Thanks for your work

Following the thread, I also think this plugin integration would be cool

Thanks everyone for the support. I'll mark the thread as solved

Hi,
after upgrading to 22.7.7 I noticed this error in the reporter, (this seems to persist even in 22.7.7_1:

Code Select Expand


[04-Nov-2022 09:30:45 Europe/Rome] TypeError: array_merge(): Argument #1 must be of type array, null given in /usr/local/opnsense/mvc/app/controllers/OPNsense/Wireguard/Api/GeneralController.php:93
Stack trace:
#0 /usr/local/opnsense/mvc/app/controllers/OPNsense/Wireguard/Api/GeneralController.php(93): array_merge(NULL, Array)
#1 [internal function]: OPNsense\Wireguard\Api\GeneralController->getStatusAction()
#2 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->callActionMethod(Object(OPNsense\Wireguard\Api\GeneralController), 'getStatusAction', Array)
#3 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->dispatch()
#4 /usr/local/opnsense/www/api.php(24): Phalcon\Mvc\Application->handle('/api/wireguard/...')
#5 {main}
[04-Nov-2022 09:31:03 Europe/Rome] TypeError: array_merge(): Argument #1 must be of type array, null given in /usr/local/opnsense/mvc/app/controllers/OPNsense/Wireguard/Api/GeneralController.php:93
Stack trace:
#0 /usr/local/opnsense/mvc/app/controllers/OPNsense/Wireguard/Api/GeneralController.php(93): array_merge(NULL, Array)
#1 [internal function]: OPNsense\Wireguard\Api\GeneralController->getStatusAction()
#2 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->callActionMethod(Object(OPNsense\Wireguard\Api\GeneralController), 'getStatusAction', Array)
#3 [internal function]: Phalcon\Dispatcher\AbstractDispatcher->dispatch()
#4 /usr/local/opnsense/www/api.php(24): Phalcon\Mvc\Application->handle('/api/wireguard/...')
#5 {main}


Hi,
I would like to ask if anyone knows the max throughput reached by the DEC840 with the WAN interface configured with PPOE. My ISP uses this protocol in conjuction with FTTH. Suppose that the LAN/WAN interfaces are connected to the SFP+ ports and no IDS/IPS are used.
Thanks

Got the same thing, I noticed it a few minutes ago, I'll follow the thread

Hi franco, thanks for your answer. I have many aliases set, but the spike happened even on a fresh install without any aliases set. Is it possible that just the python call causes these spikes? Do you think that this cpu behaviour is normal? I am worried that on high throughputs this behaviour could cause issues. For example consider if I am downloading at gigabit speed and the cpu is on 80% usage. If the script takes 20% of the cpu every minute it would maximize the cpu usage resulting on packet loss. Am I right?
Thanks again.
Best regards

+1 great work!

Hi,
I installed OpnSENSE on an APUe2 platform. It seems to run well but I noticed that every 60 seconds the CPU goes from 1-4% to 30%. This happens when the python "script update_tables.py" runs. Is this normal? The issue was already reported in July here: https://forum.opnsense.org/index.php?topic=18215.msg82722#msg82722 but the user provided only a workaround. This happened to me both on a fresh install without any configuration (only WAN/LAN interfaces) and a full operative instance. I attached a couple of screenshots which show the cpu graph and the process that causes the spike.
Thanks