Messages

1

23.7 Legacy Series / Re: htop installation fails

« on: September 26, 2024, 03:59:51 pm »

To be honest, it was a pain to even find the htop binary/package.  I'm not going to be any help unfortunately...I could never find an easy way to do this either.

2

24.7 Production Series / Re: How to install htop

« on: September 22, 2024, 03:57:28 pm »

pkg add https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/htop-3.3.0_2.pkg also works...for the current version.

3

23.7 Legacy Series / Re: htop installation fails

« on: September 22, 2024, 03:56:03 pm »

Looks like it's here now for current version of OPNsense.

https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/htop-3.3.0_2.pkg

When you need to update it, I "delete pkg htop" and then "add pkg htop <url>".  Just updated using this link and it works as expected.

4

23.7 Legacy Series / Re: htop installation fails

« on: January 02, 2024, 06:24:11 pm »

I just install the pre-compiled version without issue using this command (assuming amd64 platform).

Code: [Select]

sudo pkg add https://pkg.freebsd.org/FreeBSD:13:amd64/quarterly/All/htop-3.2.2_1.pkg

5

23.1 Legacy Series / Re: zabbix how to help

« on: July 02, 2023, 03:16:28 pm »

There is no server component for opnsense.  Zabbix is a large network monitoring package.  It monitors hosts throughout your network mostly using agents that are compiled for different OS's.  That is what is provided with OPNsense...a host (client) agent so you can monitor your OPNsense server.  The Zabbix server is set up using Linux.  See here:

https://www.zabbix.com/download

6

23.1 Legacy Series / Re: zabbix how to help

« on: July 02, 2023, 03:05:55 am »

Zabbix agents of all versions have similar configuration and Zabbix even states you can use different version agents with the server...though you may not have full access to the newer features.  The Zabbix gui i provided by the server component, not the agent.  If you mean you can't see the configuration screen in OPNsense after you add it, refresh your browser page and it will appear under Services...from there you can add your configuration.

7

23.1 Legacy Series / Re: ddclient-devel is broken

« on: April 24, 2023, 04:05:36 pm »

@tidarp5 Thank you!  Much easier than trial and error. 

8

23.1 Legacy Series / Re: ddclient-devel is broken

« on: April 24, 2023, 03:18:27 pm »

Ah yes, I used the interface as the IP source. So that's why it's broken. After trying some other web based source, I found it works correctly with ipify-ipv4. Thanks!

And also for anyone else who use duckdns, the Hostnames needs to have only the sub-domain part of duckdns. For example, if your domain is 'my-domain.duckdns.org' , then just put 'my-domain' in Hostnames field.

Thanks for this.  Just to confirm settings, you're using backend:opnsense, service:dyndns2, both username and password (token), hostname (sub-domain segment only as noted above), check ip method:ipify-ipv4, interface to monitor:WAN, forcessl:checked.

I tried using dyndns as the check ip method and didn't get an error, but also no success message.  To confirm the log messages, this is what I'm seeing now.  (It's confusing I still see ddclient running as I thought backend:opnsense negated the need for that...confirm...?)

Code: [Select]

2023-04-24T09:02:39-04:00 Notice ddclient Flush dyndns status to disk
2023-04-24T09:02:39-04:00 Notice ddclient Account xxxxxxxxxxxxxxxxxxxxxxxxxx [dyndns2 - ] changed

9

23.1 Legacy Series / Re: IPV6 not routing after update to 23.1.5_4

« on: April 24, 2023, 02:52:29 pm »

Stoopid UDM Pro downstream of it that's borked.

A while back, I had an ipv6 issue that was caused by a specific model TP-Link AP (Omada) bug that I attributed to opnsense/freebsd.  Spent a day on it...neglected to run a test scenario using a wired device...or different AP.  It happens.

10

23.1 Legacy Series / Re: Hundreds to thousands of DNS queries for *.in-addr.arpa every second

« on: April 18, 2023, 11:45:43 pm »

Based on your setup, I think you want conditional forwarding turned on.  But that shouldn't be the cause of your issue...so whatever you want.

"If not configured as your DHCP server, Pi-hole typically won't be able to determine the names of devices on your local network. As a result, tables such as Top Clients will only show IP addresses."

EDIT: Also, look here to stop the hourly queries pihole does.
https://docs.pi-hole.net/ftldns/configfile/#refresh_hostnames

11

23.1 Legacy Series / Re: Hundreds to thousands of DNS queries for *.in-addr.arpa every second

« on: April 18, 2023, 11:13:57 pm »

I believe OPNsense should be answering the local ptr requests...not making them.  In pihole settings, DNS, Advanced at the bottom, I have both "Never forward" options checked and use conditional forwarding...make sure to fill in the boxes below that option at the bottom.  You stated you are using opnsense for dhcp, not pihole...make sure you don't use both...it's one or the other of course, just in case I misunderstood your setup.

In unbound, I have register static mappings and dhcp leases checked (you may have other options as well).  Also, I would probably include a DNS in System General for the router itself as that's not going to be passed to hosts via DHCP unless you make that selection to do so.  I found the boot process seemed to be quicker when the router has that information.  Don't use your pihole in case it's offline (just my opinion).  This setup works for me.  I use pihole -> DNSCrypt-proxy for resolution...not unbound (though I use unbound for local host resolution)...otherwise it's a similar setup.  Hope this makes sense and solves your issue.

12

23.1 Legacy Series / Re: 23.1.5 Zabbix Agent deprecated since 31 march 2023

« on: April 15, 2023, 02:54:26 pm »

You need to provide more details.  The included zabbix agent maintained in plug-ins "os-zabbix62-agent" works perfectly well.

13

23.1 Legacy Series / Re: IPV6 not routing after update to 23.1.5_4

« on: April 01, 2023, 10:43:05 pm »

Had a similar problem after update.  Typically, I can resave the WAN interface and it corrects itself.  This time it didn't work.  I then tried restarting radvd and that didn't *seem* to have an effect either.  However, after a few minutes, it then just started working.  I don't know what's going on.  My setup upgraded fine without issue, but a similar server failed to have ipv6 upon update.

14

23.1 Legacy Series / Re: More detailed CPU usage?

« on: March 31, 2023, 03:43:09 pm »

Maybe overkill, but I use zabbix and then can get alerts if monitored processes die or like the recent discussion, ipv6 routing fails.  Alerts for excessive CPU is also a default alert...I haven't seen anything zabbix can't do but I'm just a home user.

Also for OP, there is a process that processes netflow data that does saturate one core briefly as has been discussed here and maybe more on github (flowd_aggregate.py).  Might be it, and there are probably others.

15

23.1 Legacy Series / Re: IPv6 PD Update 23.1.5

« on: March 29, 2023, 07:40:26 pm »

I also see this problem sporadically.  This week on 23.1.4_x for a new build (similar specs to mine below), hosts can't ping ipv6 on the WAN, but saving WAN interface settings clears the problem.  It appears to be a route issue (?) as hosts are all getting IP addresses...did see a message about an invalid route but didn't make note of it.  Also tried saving the LAN interface settings this time but that did not correct it, saving WAN did.  Again, for me this has only happened once or twice in the past months.