Messages

106

23.7 Legacy Series / Re: Either Unbound or the latest patch (23.7.xxxx) broke my connection

« on: December 03, 2023, 08:31:34 pm »

Hmm anyone know how I can interpret this error:

2023-12-03T19:58:27   Error   unbound   [24652:3] error: reading root hints /root.hints 2:6: Syntax error, could not parse the RR's type

107

23.7 Legacy Series / Re: Either Unbound or the latest patch (23.7.xxxx) broke my connection

« on: December 03, 2023, 08:14:38 pm »

Right....

I can now say I still have this problem with Unbound. It just hanged at 100% on one core (of . I had to kill-9 to get it to release and stat to behave again. Trying restart the process from GUI just do not work.

No I do not know what is wrong... I would love to build a monit watchdog so kill-9 and restart when it hits CPU above 99% on one core.... Anyone know how to write such a thing?

108

23.7 Legacy Series / Re: [CALL FOR TESTING] Unbound DNS over TLS without explicit CA bundle

« on: December 03, 2023, 08:12:09 pm »

Well the egg timer just stopped so now I know that the problem with 100% CPU in one core is not related to this fix.

109

General Discussion / Some different errors in general log file - do I need to care?

« on: December 02, 2023, 10:02:16 am »

So I seem to have a few different errors in the general log file. One of them "unknown dhcp option value 0x78" I have been told is not relevant - it would be nice if one could remove those errors, but I do not know how?

However my question is more: Do I need to care about any of the other lines from the log? After all, everything works....

Code: [Select]

Date Severity Process Line

2023-12-02T04:22:15 Error dhclient unknown dhcp option value 0x78
2023-12-01T22:22:16 Warning igmpproxy select() failure; Errno(4): Interrupted system call
2023-12-01T22:22:16 Warning opnsense /usr/local/etc/rc.linkup: dhcpd_dhcp4_configure() found no suitable IPv4 address on opt2(igb2)
2023-12-01T22:22:15 Error dhclient unknown dhcp option value 0x78
2023-12-01T22:22:12 Critical dhclient exiting.
2023-12-01T22:22:12 Error dhclient connection closed
2023-12-01T17:07:54 Error dhclient unknown dhcp option value 0x78
2023-12-01T11:42:32 Error dhclient unknown dhcp option value 0x78
2023-12-01T05:42:33 Warning igmpproxy select() failure; Errno(4): Interrupted system call
2023-12-01T05:42:32 Warning opnsense /usr/local/etc/rc.linkup: dhcpd_dhcp4_configure() found no suitable IPv4 address on opt2(igb2)
2023-12-01T05:42:32 Error dhclient unknown dhcp option value 0x78
2023-12-01T05:42:28 Critical dhclient exiting.
2023-12-01T05:42:28 Error dhclient connection closed
2023-12-01T02:56:06 Error dhclient unknown dhcp option value 0x78
2023-11-30T21:19:23 Error dhclient unknown dhcp option value 0x78
2023-11-30T15:19:23 Warning igmpproxy select() failure; Errno(4): Interrupted system call
2023-11-30T15:19:23 Warning opnsense /usr/local/etc/rc.linkup: dhcpd_dhcp4_configure() found no suitable IPv4 address on opt2(igb2)
2023-11-30T15:19:23 Error dhclient unknown dhcp option value 0x78
2023-11-30T15:19:19 Critical dhclient exiting.
2023-11-30T15:19:19 Error dhclient connection closed
2023-11-30T15:13:36 Warning igmpproxy select() failure; Errno(4): Interrupted system call
2023-11-30T15:13:36 Warning opnsense /usr/local/etc/rc.linkup: dhcpd_dhcp4_configure() found no suitable IPv4 address on opt2(igb2)
2023-11-30T15:13:35 Error dhclient unknown dhcp option value 0x78
2023-11-30T15:13:32 Critical dhclient exiting.
2023-11-30T15:13:32 Error dhclient connection closed

110

General Discussion / Re: Loss LAN connection after every reboot.

« on: December 02, 2023, 09:51:06 am »

I only applied that patch that franco supports in the message AFTER every update (until I find out that it is permanently resolved).

However, after what you write I need to understand one challenge that you have: When you write that "can ping google" from OPNsense terminal - is that connection to OPNsense established on the same device that has no internet connection? If so then your challenge is within DNS and not the interface itself (although restarting the interface might solve the issue it is not the interface in it self thas creates the issue). To solve my DNS challenges I did so by installing another patch that, again, franco supplied in the thread about DNS-over-TLS testing: https://forum.opnsense.org/index.php?topic=37243.0

111

General Discussion / Re: MONIT to monitor all running "Services" and email when stoped?

« on: December 01, 2023, 07:52:12 pm »

Ah - I think I got it a bit better, however the igmpproxy does not have a pid - but someone else on this forum already solved that kind of, so I copied that for igmpproxy.

Thanks!

112

General Discussion / MONIT to monitor all running "Services" and email when stoped?

« on: December 01, 2023, 05:58:40 pm »

So I am trying to figure out (that is to learn) how to setup Monit to send me an email when one (or more for that matter, on email per services I guess) service fails(/stops).

But I can not wrap my head around how to do that. From the attached picture you can see all the services I am currently running - how do I in one Monitor instance (/row?) enable this? I can not test on stopped process as far as I am aware - and PID file will change from time to time. What or maybe more accurate where did I turn wrong?

113

General Discussion / Re: Loss LAN connection after every reboot.

« on: December 01, 2023, 05:49:12 pm »

Wonder if you stumbled onto the same challenge I had - here is a test if so:
https://forum.opnsense.org/index.php?topic=36807.msg180150#msg180150

114

23.7 Legacy Series / Re: Either Unbound or the latest patch (23.7.xxxx) broke my connection

« on: November 30, 2023, 10:02:11 am »

FWIW....

After I applied the patch that franco requested to be tested: https://forum.opnsense.org/index.php?topic=37243

I had no issues with Unbound - this is a bit unexpected, but I am happy anyway. My problems seems to be solved (and now I will run away and grab that egg timer until next challenge presents itself!).

115

23.7 Legacy Series / Re: [CALL FOR TESTING] Unbound DNS over TLS without explicit CA bundle

« on: November 30, 2023, 09:58:18 am »

Still running as expected, no problem, and no 100% CPU Core process runaway stuff. This just works!

116

23.7 Legacy Series / Re: [CALL FOR TESTING] Unbound DNS over TLS without explicit CA bundle

« on: November 29, 2023, 12:25:59 pm »

I guess it might be a bit to early to say this, so I say it anyway and are ready to bit the dust later...

With this patch applied, Unbound works and behaves as expected. No more, for the moment I guess I need to add, max running Unbound process that load one core to 100%. It just behaves as expected. I have been waiting for this some time now, so well I guess I need to start that egg timer...

117

23.7 Legacy Series / Re: Unbound crashing

« on: November 27, 2023, 06:44:45 pm »

After reading this thread I can only say I think I have this issue also. When my OPNsense installation hits 100% unbound in one (of eight) cores, there are multiple unbound running. I will se if I can find anything more usable on my side....

118

23.7 Legacy Series / Re: Either Unbound or the latest patch (23.7.xxxx) broke my connection

« on: November 27, 2023, 03:46:32 pm »

Sorry, but I spoke to soooooooooon....

Yes Unbound works, but it pins one (of 8 ) cores to 100% load all the time, no matter what. Something is running hard in that Unbound process....

So I am back on DSN Masq....

119

23.7 Legacy Series / Re: Either Unbound or the latest patch (23.7.xxxx) broke my connection

« on: November 27, 2023, 01:46:35 pm »

Okey, well, I have found what was error in my configuration, and it is not what I expected....

Short "executive summery" is: Under Services, Unbound, Access Lists there is a "Default Action" drop down selection. This was for some fuggly reason selected to BLOCK - that was the error in my case. Replaced with ALLOW - problem gone, and now I am running Unbound, DoT, DNSSEC and Block Lists. And maybe something more.

The thing I can not get my head around is WHY that was changed in my config. I just can not think I have changed that my self.

So I went back in my config files, to one from 2023-08-07 - before the upgrade thingi started. There are NO records in my config backup file at all about Access Lists. So clearly, until someone points me in the right direction, I have to think that this BLOCK selection was part of the upgrade process - and not something I did or have done. If this is how the upgrade "disabled" Unbound, then this is the Ghost In the System. My current guess is that it is.

120

23.7 Legacy Series / Re: Either Unbound or the latest patch (23.7.xxxx) broke my connection

« on: November 27, 2023, 10:34:55 am »

Nope - no matter what I do Unbound just refuses to resolve any names.

I disabled DNSSEC
And then disabled DoT
And then disabled BlockLists

It seems to be ghost in the system when it can not even work empty so to speak.

Is there any easy way to kind-of-restore-default to only Unbound settings, like hacking the config file and just remove everything - is that doable to make a "cold reset" so to speak so I know that I am not fighting anything old that just "hangs-around-the-corner-that-I-forgett-or-can-not-see" thing?

Edit: Worth noting in all this: This config Used to work, and did so for what 6 months since last change (and it worked before that to). So I find it very strange that it all of a sudden, just because of upgrade of OPNsense, and most likly Unbound, it just stops resolving names. It is at least one ghost in the system......