NUT package (2.8.0 and below)
-
@dennypage Thank you for your suggestion.
Do i need to search through 1212 posts to find the executable ?
-
When its ready, you see it here, signaled as "an update has arrived" :
There will be a yellow sign after the "i".
-
@dennypage Hi!
Thank you for the tips, I am going through the serial drivers.
In the UPS settings page the serial port is a drop down menu and /dev/cuau0 and /dev/cuau1 is the 2 option, theres nothing else.
SO this case can't understand your hint regarding the 6100.Sofar I had no luck... Would you suggest and USB-B to USB-A cable? ( the UPS has the usb port similiar to printers do)
Kind regards,
-
@zeemaffin said in NUT package:
In the UPS settings page the serial port is a drop down menu and /dev/cuau0 and /dev/cuau1 is the 2 option, theres nothing else.
SO this case can't understand your hint regarding the 6100.The 6100 has two hidden/unconnected serial ports on the motherboard. These will show up as cuau0 and cuau1. That there is not another option strongly implies that the serial emulator chip is not supported by FreeBSD.
Sofar I had no luck... Would you suggest and USB-B to USB-A cable? ( the UPS has the usb port similiar to printers do)
Absolutely. If the UPS has a native USB interface, it would always be preferred over a serial emulator cable.
-
@abs0new said in NUT package:
Do i need to search through 1212 posts to find the executable ?
LOL.
It's from earlier this year.
-
HI Denny!
News!
With the USB cable I see the UPS via the command usbconfig, however its not showing up in the graphical interface dropdown menu.
I mean the cuau 0-1 shows up only, but the usbus0 wont.Would you suggest a restart of the firewall, or is there another package I need to be able to use the usbbus for this purpose?
Sorry for the dummy questions.Kind Regards,
Maffin -
@zeemaffin said in NUT package:
With the USB cable I see the UPS via the command usbconfig, however its not showing up in the graphical interface dropdown menu.
I mean the cuau 0-1 shows up only, but the usbus0 wont.With a regular USB connection, there isn't a pulldown to select the port. I expect that you still have "Local Serial" set as the UPS Type.
Change the UPS Type to be "Local USB". The Driver field then has a list of usb drivers that are available. Always try "usbhid" before trying anything else.
-
@dennypage Jesus I feel so dumb right now :D
Thank you for your help!!!
I wont sturggle next time for sure.... now I have to make the timeouts and the other stuff :D
-
@zeemaffin Timeouts? Do you mean for NUT? If so, I recommend that you don't configure any times unless you are trying to address a specific problem.
-
@dennypage Happy Halloween! NUT 2.8.1 is out, when will we see it in pfSense?
-
I gave up waiting for a NUT 8.1 release a while back. The new NUT package is based on nut-devel (git) rather than the nut-2.8.1 release version. At the moment, they are effectively the same thing, but I'm currently thinking to stay with nut-devel until I see how stable the 2.8.1 release actually is.
If you like detail, you can read Redmine issue #14795, and pull requests #1295, #1296, #1310.
The new pfSense NUT package should start with 23.09.
-
@dennypage so if the current nut-2.8.0_23 package from pfSense still loses connectivity with my CyberPower CP1500AVRLCD3, the 2.8.1 release won't be better ?
-
@vizi0n The current version of the pfSense NUT package is 2.8.0_2, and depends upon NUT 2.8.0. The next version of the package will be 2.8.1, and depends upon the current Git version of NUT, which is the same as NUT 2.8.1.
For clarity, the issue in NUT 2.8.0 isn't that USB connectivity is lost, which is common with the CyberPowers, but that the USB driver crashes when it attempts a USB.
And yes, the USB issues introduced in NUT 2.8.0 are addressed in NUT 2.8.1.
I expect staff has been very busy with 23.09, but now that it has been released I expect the NUT package will be released soon.
-
Yikes, I just stumbled on this thread and sure hope we see that update soon.
Reading earlier in the thread I'm not clear, is the "user=root" to ups.conf AND "interruptonly" to driver arguments going to help the USB Cyberpower situation? Or if I want it fixed now I need to dig up the developer version someone mentioned earlier? I haven't actually found that post yet, still looking.
For me my USB cyberpower was mostly reliable under 2.6.0, I thought I had my packages up to date but maybe not. Upgraded to 2.7.0 and NUT fell apart, disconnect alerts from pfsense, AND all the devices that were listening to NUT over the LAN. I was contemplating rolling the whole pfsense install back to 2.6.0 but now I can see that isn't going to help.
-
@JonathanLee I switched from snmp to USB and have had no problems at all on a CPF1500LCD (if I recall the model right off the top of my head). Prior I was using snmp which connected to the cyberpower software running on a Windows machine (via network - you can configure the software to act as an snmp server).
But, both methods gave me 0 drops ever. I only switched to USB a couple weeks ago but 0 disconnects so far.
-
@Maxburn You can either grab the prior usbhid-ups executable (from Feb), or you can wait until the new package appears. It's been accepted, just waiting on it to show up in packages on 23.09.
-
@dennypage
I am so excited .... and I just can't hide it....I can't wait for the new update
-
D dennypage referenced this topic on Nov 9, 2023, 4:06 PM
-
Beginning with 2.8.1, I am transitioning NUT support to a new thread, which can be found here.
Please continue to post issues related to 2.8.0_2 and below to this thread.
Also, I am actively seeking people to test the new 2.8.1 pfSense NUT package prior to general release. I would appreciate any help you can offer. Thanks!
-
S stephenw10 moved this topic from pfSense Packages on Apr 2, 2024, 6:44 PM
