NUT package (2.8.0 and below)

dennypage

This topic is for information on the new NUT package.

The new package, version 2.7.4, has been released. If you have the prior 2.3.X package installed, it is recommended, but not required, that you uninstall the old package before installing the new package. This will ensure that all files from the prior package are removed.

The new package brings an all new gui and alignment with current NUT architecture. It supports configuration for all UPS types that the FreeBSD NUT distribution supports, including local USB, local serial, remote SNMP, remote NUT and apcupsd servers.

After installing the new package, NUT status and settings can be accessed in Services / UPS. The new widget can be added to the dashboard by selecting UPS Status.

Background information can be found in the beta test topic here: https://forum.pfsense.org/index.php?topic=114871.0

Version history:

2.7.4_1 Fix repo/build issues.
2.7.4_2 Fix repo/build issues.
2.7.4_3 Remove orphaned NUT menu entry on upgrade.
2.7.4_4 Allow mixed case for serial port (/dev/cua[uU]?).
2.7.4_5 Add support for NUT's "dummy" driver.
2.7.4_6 Add support for power kill following shutdown (requires pfSense 2.4.3).
2.7.4_7 Allow operation with remote clients that require user "monuser" such as Synology.
2.7.4_8 Update links. No functional changes.
2.8.0_2 Update to NUT 2.8.0. PHP 8.1 support.

dennypage

If you want to allow access to the NUT daemon from other hosts, there are two options available. You can either use a port forward in the firewall rules, or you can add a listen directive to upsd.conf.

Option 1: To add a port forward, go to Firewall / NAT / Port Forward, and create a port forward with the following attributes:

Interface: The interface you want to allow access from, usually LAN
Protocol: TCP
Destination: The firewall address matching the interface, usually LAN address.
Destination port: The port you want to use for access, usually 3493
Redirect target IP 127.0.0.1
Redirect target port: 3493

In general, this option is simpler because you can easily restrict access by adding a Source Address to the NAT rule.

Option 2: To add a listen directive to NUT, go to Services / UPS / Settings. Use the Display Advanced button to show the Advanced settings section. In the section for upsd.conf, add a line like:

LISTEN 192.168.1.1

where 192.168.1.1 is the address of the interface you want to allow access from. You can also specify IPv6 addresses with the listen directive. Note that if you use this option, you will need to use firewall rules to restrict access to specific source addresses.

It is important to choose one option or the other. DO NOT DO BOTH AT THE SAME TIME.

Regardless of which option above you choose, you will also need to add a user entry in upsd.users. To add the entry, go to Services / UPS / Settings. Use the Display Advanced button to show the Advanced settings section. In the section for upsd.users, add lines like:

[remoteuser]
password = mypassword
upsmon slave

Allowing remote access to NUT on the firewall should not be done casually. If you do allow remote access, it is a good idea to restrict access to trusted source addresses only.

th3r3isnospoon

Cross post from the beta…

Hello All,

Thank you for the work on this.

After installing the new version, I no longer see it listed in the services menu (neither NUT nor UPS). I tried the install on two different pfSense FW's running 2.3.2 (pfsense amd64 and nanobsd) and right now it doesn't work on either box.

When I do a full reinstall it says this:

Upgrading pfSense-pkg-nut...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
pfSense-pkg-nut-2.7.4_1 [pfSense]

Number of packages to be reinstalled: 1
[1/1] Reinstalling pfSense-pkg-nut-2.7.4_1…
[1/1] Extracting pfSense-pkg-nut-2.7.4_1: …....... done
The nut package is not installed.

Deletion aborted.XML error: PKGINFOLINK at line 8 cannot occur more than once

Cleaning up cache... done.
Success

I tried a full uninstall and reinstall but the service is nowhere to be found. It shows that the package is installed, I just can't do anything besides that. Any ideas?

Thanks,

-th3r3isnospoon

dennypage

FYI, I pulled the package from the factory download apart, and there are indeed two pkginfo lines in the file usr/local/share/pfSense-pkg-nut/info.xml. The second occurrence of the pkginfo line is not present in github, but appears in the version downloaded by the package manager. I have an email in to ask if anyone knows how this got added.

dennypage

The issue has been tracked down to a specific problem with a branch of the repo. I'm sure it will be fixed soon.

Thank you for your patience.

w0w

The fun is that I have successfully reinstalled NUT in VM, and doing the same steps on production caused error posted above. Strange.

dennypage

Is the VM using beta.pfsense.org as its repo? You can check with "pkg -vv".

w0w

Yes, you are right. I just forgot that changed repository some time before. It's just beta.

esquire1968

After updating to 2.7.4_1 I can't find the Service! Where can I download the previous version or how can I repair this Version.

Thx!
Thomas

w0w

@esquire1968:

After updating to 2.7.4_1 I can't find the Service! Where can I download the previous version or how can I repair this Version.

Thx!
Thomas

https://forum.pfsense.org/index.php?topic=114871.msg645613#msg645613

AR15USR

Well me too. Installed the new package and its gone. Maybe you should pull this update till this problem is fixed…

dennypage

@AR15USR:

Maybe you should pull this update till this problem is fixed…

I don't have access to pull the package from the servers.

It's correct in the development branch of the repo, which is why beta works. There appears to have been a merge problem in moving between the development branch and the 2_3_2 branch which resulted in a duplicate line in the xml file. I don't have access to modify the 2_3_2 branch, or update the package servers. If I did, I would fix the issue.

I have an email in, but don't know if anyone will be available over the weekend to update the package servers.

AR15USR

@dennypage:

@AR15USR:

Maybe you should pull this update till this problem is fixed…

I don't have access to pull the package from the servers.

It's correct in the development branch of the repo, which is why beta works. There appears to have been a merge problem in moving between the development branch and the 2_3_2 branch which resulted in a duplicate line in the xml file. I don't have access to modify the 2_3_2 branch, or update the package servers. If I did, I would fix the issue.

I have an email in, but don't know if anyone will be available over the weekend to update the package servers.

Gotcha, hopefully it will get fixed shortly..

AR15USR

It sure is flooding my logs now though:

Aug 6 14:39:40	kernel		uhid0: <cps 0="" 1="" or1500lcdrm1u,="" class="" 0,="" rev="" 1.10="" 2.00,="" addr=""> on usbus0
Aug 6 14:39:39	kernel		ugen0.2: <cps> at usbus0
Aug 6 14:39:37	kernel		uhid0: at uhub1, port 5, addr 1 (disconnected)
Aug 6 14:39:37	kernel		ugen0.2: <cps> at usbus0 (disconnected)
Aug 6 14:39:31	kernel		uhid0: <cps 0="" 1="" or1500lcdrm1u,="" class="" 0,="" rev="" 1.10="" 2.00,="" addr=""> on usbus0
Aug 6 14:39:30	kernel		ugen0.2: <cps> at usbus0
Aug 6 14:39:28	kernel		uhid0: at uhub1, port 5, addr 1 (disconnected)
Aug 6 14:39:28	kernel		ugen0.2: <cps> at usbus0 (disconnected)
Aug 6 14:39:21	kernel		uhid0: <cps 0="" 1="" or1500lcdrm1u,="" class="" 0,="" rev="" 1.10="" 2.00,="" addr=""> on usbus0
Aug 6 14:39:21	kernel		ugen0.2: <cps> at usbus0
Aug 6 14:39:18	kernel		uhid0: at uhub1, port 5, addr 1 (disconnected)
Aug 6 14:39:18	kernel		ugen0.2: <cps> at usbus0 (disconnected)
Aug 6 14:39:12	kernel		uhid0: <cps 0="" 1="" or1500lcdrm1u,="" class="" 0,="" rev="" 1.10="" 2.00,="" addr=""> on usbus0</cps></cps></cps></cps></cps></cps></cps></cps></cps></cps>

on and on…

dennypage

If you are comfortable with the command line, you can fully delete the package with the following command:

pkg delete pfSense-pkg-nut

If you need a functioning package right away, you can update the package using the beta switch switch as w0w describes in the beta thread, or you can PM me with an email address and I will send you a package which is functionally the same as the release version.

AR15USR

Well got this result, but it has disappeared off the Installed Packages list. However my logs are still being flooded…

[2.3.2-RELEASE][xxxx@xxxxx.lan]/root: pkg delete pfSense-pkg-nut
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
	pfSense-pkg-nut-2.7.4_1

Number of packages to be removed: 1

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling pfSense-pkg-nut-2.7.4_1...
The nut package is not installed.

[1/1] Deleting files for pfSense-pkg-nut-2.7.4_1: 100%nut-2.7.4_1:   0%
The nut package is not installed.

AR15USR

OK I did the install from the development branch and it still didn't show up afterwards. So I uninstalled and switched back to Stable.

I'll be waiting for the update/fix to show in the Stable…

w0w

Are you sure that you are looked for "UPS" in Services menu instead of "NUT"?

Just because "development trick" still working for me on VM and production.

AR15USR

@w0w:

Are you sure that you are looked for "UPS" in Services menu instead of "NUT"?

Just because "development trick" still working for me on VM and production.

Ah, there it is. See it now, thanks…

dennypage

The repo issue has been fixed. The package version has been updated to 2.7.4_2.