@aadder Did you get this working? If not does the acpupsd program work? If you want to used nut for this then connect to the system using ssh and check the permissions on the usb device the ups is connected to. That would be in /dev/usb/ directory. The permissions should be crw-rw---- root uucp

Thanks - doing a bit of looking into this, and seems they are working on it ;)

@adamthemantyler said in Quagga_OSPF: not available in remote repository:

@bmeeks Thank you. Looks like I am running 2.4.5 on my boxes still. What would you say the upgrade path looks like? Would I just have to manually document my OSPF configuration and remove the module.. Then upgrade to 2.5.0 and install FRR?

Or is there some migration path that will move settings over from Quagga for me?

I have some other packages that are out of date too, is it generally a better idea to upgrade packages before a system update or the other way around?

Regards,
Adam Tyler

Sorry Adam, but I don't use either package (Quagga nor FRR), so I wouldn't be of much help. Perhaps someone else will chime in with migration options.

As for updating other packages, ALWAYS update pfSense itself first if an update is available. If you update or install a package after a new pfSense update is posted, and you haven't installed that pfSense update, then installing a package will break your system -- sometimes to the point of needing to reinstall and restore a config backup.

If you want to install a package on an older pfSense version, then you must go to SYSTEM > UPDATE and on the Update Settings tab change the drop-down selector there to the option "Previous stable version (2.4.5 deprecated)", save that change, then install the package. Changing that setting points your package system utility to the correct branch of packages. Note that these older packages will not be updated, though. They will be whatever was the "current" version at the time the new pfSense was released.

There is a dedicated FRR sub-forum on the board here: https://forum.netgate.com/category/79/frr. Perhaps posting your questions in there would generate some helpful replies.

@slim2016 said in Arpwatch Notification : Cron <root@pfsense> /usr/bin/nice -n20 /usr/local/bin/php-cgi -f /usr/local/pkg/suricata/suricata_check_for_rule_updates.php:

@bmeeks @eveready1010

The fix has been posted by Viktor Gurov but the link does not work.

https://gitlab.netgate.com/pfSense/FreeBSD-ports/-/merge_requests/72

That is Netgate's private Git respository. It is not publically available. You will need to wait for the change to be merged into the public Github repo. They have a private internal repo where they do testing of changes before migrating them to the public site. Notice the URL is "gitlab.netgate.com". Anytime you see that "gitlab" portion, that is their private repo.

@gertjan this feed def gets logged in the reports/log files section.

in the test area, I am going to try some more IP feeds.

I must admit that I have never heard before about squeezebox, therefore I have never used it before. Most of the time I listen to music through Spotify using my wireless headphones. I especially like doing so while training, and since lately most of my workouts are done at home, I enjoy using my headphones even more. I understand that your problem is with Avahi, so my basic question is why did you decide to use this app? I get my apps only from https://appcrood.com, who I consider to be trustworthy, and because of that I always get quality.

Why do you think that's a problem or necessary?

Is something actually not working that you expect?

Those URLs are not meant to be browsed by humans, but used by pkg.

Solved.

I did an update from 2.4.5_1 to 2.5.0, and now it works...
It might just be the reboot, but idk

I did the upgade to version 2.4.5_1 and I had no problems (unlike the update to version 2.5 which did not work), after this update I see all the additional packages.
thanks.

@ibbetsion said in Telegraf's built-in ping plugin showing higher latency since v2.5:

Since upgrading to 2.5, the built-in Telegraf ping plugin is reporting results with a higher latency then what I get if I were to ping the same system from the pfsense CLI. And the diff is 2x, sometimes more. This wasn't an issue in 2.4.5x. Is this a known issue?

For more clarity, I'm pinging a system on LAN, so am expecting <0.3ms response time. Telegraf shows >0.8ms, sometimes even >2ms.

@steveb53 said in Quagga OSPF missing in 21.02-RELEASE-p1:

@nogbadthebad HI,
FRR was already in the previous release but its not as user friendly.

Quagga is missing in the current package manager.

If its been dropped, why, if not when might we see it in the newer release. All the pfsense docs refer to Quagga too and not FFR.

Quagga and several other packages were officially retired back in November last year. Here is the entry on Redmine: https://redmine.pfsense.org/projects/pfsense/repository/revisions/85652efd5dfee9f66c7c7f3c97eb1c368f690ae3.

@wyang

Hello!

I dont think the openvpn-client-export install is related to the FRR deinstall. FRR would have been deinstalled by simply switching to the 2.4.5p1 repo.

Now that you have switched back to the 2.4.5p1 repo, I would try reinstalling FRR from the Package Manager. My experience is that the packages that were auto-purged still had their settings saved.

John

https://forum.netgate.com/topic/161050/snort-won-t-start-after-upgrade-to-21-02-on-sg-3100

@allang thanks for this....fortunately not something serious. All fixed.

Thanks from Canada ..... 🍁

Cheers

Tim

@dcd018
Hello Everyone , I face the issue now.
User able to log in without any certificate.....

To the people following this thread, i couldn't make this work.

Steve from Netgate did his best to provide support for this via a ticket that I opened and not even he could understand why APCUPSD was working on my ubuntu box but not on pfsense.

In any event, i decided to give nut a more serious try and got it working. I migrated my ubuntu box from APCUPSD to nut, as a slave, and everything seems to be working fine. At least both, the SG-1100 and the Ubuntu box can monitor the ups and retrieve it's status and parameters.

The key for this was to restart pfSense after installing the nut package. If not, I kept getting an error saying that nut "could not connect to the UPS : Not such file or directory".

This tip was provided in the following webpage https://blog.victormendonca.com/2020/10/28/how-to-setup-ups-on-pfsense/