Messages

1

General Discussion / Need to stop opnsense from advertising itself for dns (IPv6)

« on: May 05, 2023, 08:07:04 am »

Hi all,

So, I'm trying to get all devices to use pihole for dns. IPv4 is working perfectly. IPv6 not so much. I have input piholes ipv6 address into the DHCPv6 service page and while it is served, opnsense still includes its own IP address.

My assumption is that by supplying an address in DHCPv6, opnsense should not be advertising its own.

I've seen where people have suggested using Router advertainments as a work around (in my case set it to managed and supply the dns address there) and while that may work here...I'd really like to understand why DHCPv6 isn't behaving as expected.

Lastly, unbound is running on opnsense as pihole uses it as its upstream provider so blocking ports/disabling it is not an option.

DNS flow should look like this:

Device -> PiHole -> Opnsense -> Public DNS

But because Opnsense is providing its address for dns, pihole can get bypassed.

2

General Discussion / Re: NUT

« on: July 19, 2022, 06:52:29 am »

Anyone know if os-nut supports advanced configuration? Specifically looking for the battery delay option that the debian/rhel package of nut has.

3

General Discussion / Re: NUT

« on: July 07, 2022, 03:41:17 am »

So, I cannot disable nut in the general settings because even with the driver enabled it stops working.

Is there a configuration file I can edit for this plugin? In addition to fixing this issue, I also need to set a low battery delay.

My battery backup is technically border line overloaded and will complain about low battery during times of high load. One such occurrence caused opnsense to shutdown...which is weird because I was never on battery backup.

4

General Discussion / NUT

« on: June 29, 2022, 04:03:42 am »

Hi,

I'm getting a re-occuring message in shell that I think is coming from nut:

UPS UPSName is unavailable

My opnsense box is a client only and serves no other machines. My ups is an APC smart-ups 1500RM. Nut is configured using the APCUPSD-driver.
Under general settings I do have nut enabled and all other settings at default.

It looks like the UPSName is coming from general settings. Can I disable nut since I'm using the APCUPSD driver and still get the auto shutdown action on battery low?

5

General Discussion / Re: PHP Memory exhaustion errors

« on: March 12, 2022, 07:58:48 am »

Not yet, usually we keep these on the development branch for at least one release, maybe since this is a relative small fix we can release it earlier, but if that's not the case you can still use patch after an update in the meantime.

Thanks for letting us know this fixes your issue, certainly helps in the release cycle.

Best regards,

Ad

Final Update: Its been 5 days since I applied the patch and the errors have not returned. At this point I'm comfortable declaring the patch the fix for my issue.

Understood on the release. I'll keep an eye on the patch notes and repatch after updates until I see it show up in the patch notes.

6

General Discussion / Re: PHP Memory exhaustion errors

« on: March 07, 2022, 04:54:47 am »

Sounds like a large log file, this https://github.com/opnsense/core/commit/71a8da452cca02412aab8906c2df0140cc434b28 might help, although the prefixes action will likely still take quite some time due to the size it needs to parse.


To apply the patch, the following command should do the trick:

Code: [Select]

opnsense-patch 71a8da4

Best regards,

Ad

Its been 24 hours since I've applied the patch and the memory exhaustion errors have not returned. Previously I was getting the exhausting error multiple times an hour, 24 hours a day. Since the patch was applied it has not returned and thus it would seem to indicate that the target of the patch was indeed my issue.

I plan to continue monitoring closely for a while to ensure the error does not return.

Is there an ETA on the update that will contain this patch?

7

General Discussion / Re: PHP Memory exhaustion errors

« on: March 05, 2022, 10:41:21 pm »

I've applied the patch using the command provided. I'll monitor and report back.

Thanks!

8

General Discussion / Re: PHP Memory exhaustion errors

« on: March 05, 2022, 10:57:35 am »

I'm on 22.1.2.

My unit has 12GB of ram, all of which is available for opnsense to use.


I've sent it via the reporter as well but wanted to check here for more information.

9

General Discussion / Re: PHP Memory exhaustion errors

« on: March 05, 2022, 04:31:42 am »

Interesting. I too have multiple v4 and v6 subnets as well for vlan purposes.

We will have to see if anyone else reports the issue with the same conditions before we call it a pattern.

10

General Discussion / PHP Memory exhaustion errors

« on: March 04, 2022, 02:19:59 am »

Hi, I'm getting a php memory exhaustion error below:

Code: [Select]

[03-Mar-2022 19:47:29 America/New_York] PHP Fatal error:  Allowed memory size of 1073741824 bytes exhausted (tried to allocate 4096 bytes) in /usr/local/opnsense/scripts/dhcp/prefixes.php on line 95
System Information:

Code: [Select]

FreeBSD 13.0-STABLE stable/22.1-n248059-267a40127d5 SMP amd64
OPNsense 22.1.2 92fcdd63e
Plugins os-acme-client-3.8 os-ddclient-1.2 os-mdns-repeater-1.1 os-net-snmp-1.5_1 os-upnp-1.4_2 os-zabbix-agent-1.11
Time Thu, 03 Mar 2022 19:48:18 -0500
OpenSSL 1.1.1m  14 Dec 2021
PHP 7.4.28
Any idea's as to what's causing this? I did update from 21.7.8 to 22.1.2 this past sunday. I'm wondering if one of the plugins above my be to blame as according to the time stamps...these errors started a little bit after I re-enabled those last night.