Messages

1

24.7 Production Series / collectd plugin fails to start due to missing symbol: gprt_add_post_log_func

« on: October 27, 2024, 01:10:32 am »

Code: [Select]

# collectd -T
option = ReadThreads; value = -1;
option = Hostname; value = qoton.example.com;
option = FQDNLookup; value = true;
option = Interval; value = 10.000000;
Created new plugin context.
ERROR: dlopen("/usr/local/lib/collectd/network.so") failed: /usr/local/lib/libgcrypt.so.20: Undefined symbol "gpgrt_add_post_log_func". The most common cause for this problem is missing dependencies. Use ldd(1) to check the dependencies of the plugin / shared object.
Error: Parsing the config file failed!
The symbol is missing from the installed lbrary:

Code: [Select]

# nm --dynamic  /usr/local/lib/libgpg-error.so.0.*|grep gpgrt_add
000000000001a040 T gpgrt_add_emergency_cleanup
# ls -l /usr/local/lib/libgpg-error.so.0.*
-rwxr-xr-x  1 root wheel 153312 Jun 20 11:10 /usr/local/lib/libgpg-error.so.0.35.0*


Code: [Select]

# nm --dynamic /usr/obj/usr/ports/security/libgpg-error/work/libgpg-error-1.50/src/.libs/libgpg-error.so | grep gpgrt_add
000000000001a860 T gpgrt_add_emergency_cleanup
000000000001b740 T gpgrt_add_post_log_func
I am on 24.7.7.  How do I force the installation of the updated libgpg-error without shooting myself in the foot?

2

Zenarmor (Sensei) / bulk delete devices

« on: July 20, 2024, 01:19:55 am »

Still not sure how this happened, but zenarmor discovered over 1117 new devices which are actually hosts out on the internet.
It seems I have two options.

1. manually delete each one via lots of mousing and clicking
2. delete all devices, including the ones I have laboriously identified and trusted, and start over, hoping it never happens again.

Am I missing some sane third option?

Prior to this incident, I had been looking on and off of a bulk delete option, as I often get weird devices added, some due to IPv6 dynamic allocations, some I'm not sure where they come from, and I'd like to just select the bunch of them and delete, and see if they come back.

It would also be nice to make bulk assignments to "not trusted" or "trusted".

3

24.1 Legacy Series / lan IPv6 leases attributed to WAN interface

« on: July 07, 2024, 02:12:51 am »

Hi.  Running DHCPv6 on lan interface.  WAN gets IPv6 addresses via DHCPv6.
I have a /48 from ISP but I request a /56 on the WAN.  I get xxxx:xxxx:xxxx:0::/56.

xxxx:xxxx:xxxx:3::1/64 is statically allocated to the lan, and I run DHCPv6 on it handing out ::8000 thru ::87fff.

When I check my leases in the DHCPv6 screen, I find lan devices claimed by WAN interface.

If I edit the entry to assign a different IP6, it "succeeds" but the edited entry disappears.  Not found any more in the leases screen.
Not found in the DHCPv6/lan screen.

Currently, there is no Services/DHCPv6/WAN screen.
Previously, I was using static initialisation of the WAN interface for IP6, and there was a Services/DHCPv6/WAN screen.

I never enabled DHCPv6 on the WAN, as it made no sense.

Anyone else seeing this?