-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: NUT plugin w/ UI #374
Comments
|
Maybe a new challenge for @mimugmail ? :) Thank you for the request, |
|
Challenge accepted :) |
|
Take a look at: https://gist.github.com/djzort/6944d5b1a6b19ec2cbfbc691503e65e2 I just pulled the sections out of a back up. End lines got mutilated by Gist... sorry. |
|
Please use something like pastebin :) |
|
I meant nut.conf and upsd.conf in /usr/local/etc ... I need them for templating |
|
upsd.users.txt Renamed to .txt so GH will accept them. The passwords i believe are just generated by the plugin so that it can admin the running daemon |
|
Ok, seems fairly easy. Give me two weeks and then I'd please you to test intensively as I don't have an APC here to test :) |
|
i can just send you a small one if you like. |
|
@djzort whats the UPS type you are using? Since you are the first user using the UI there will be only one (yours) but easily extendable :) |
|
The UPS I use are all APC. They tend to be the least terrible. They all use the usbhid-ups driver. This is a generic usb driver though which supports UPS devices from a range of manufacturers. See also http://networkupstools.org/docs/man/usbhid-ups.html |
|
@djzort can you send me a screenshot of the status overview? Last two weeks were quite busy, but I think this should be done til mid december ... |
|
@djzort sorry, I'm a little late .. can you send me a copy of your nut.conf and tell me user the daemon runs (ps aufx) |
much like the spoon, there is no nut.conf |
|
@djzort would you test the package please? ATM it supports only your driver and is missing a status view. |
|
@mimugmail just tell us when we should close it. |
|
@djzort were you able to test it? |
|
@djzort ?? some kind of feedback would be cool .. also when don't find the time ATM. |
|
Ive been totally flat out and trying to find a UPS not in production to test this with - obviously with zero success so far |
|
@djzort ok, so we'll leave this one open and let the plugin in devel. |
|
As requested on [IRC:] nut.conf upsd.conf |
|
Hi, I'm a new OPNsense user coming from pfsense and the NUT plugin is something I was using before. I installed the plugin from cli, enabled NUT, selected standalone mode. After saving setting, I checked on cli, ups daemons doesn't seem to start on my box. |
|
Yay, new Beta tester! Can you reboot and then send me the system.log if it doesnt work? |
|
@mimugmail yes, here is my system.log after reboot. |
|
Hm, but this looks good? To be honest I'm not really familiar with the tools, but there should be a cli command to ask the daemon of the current ups status ..
|
|
Yes, I tried upsc commands with no success. Tried to list UPS on the opnsense host: $ upsc -l opnsense Tried to get info from the MyUPS connected to my opnsense box: $ upsc MyUPS@opnsense Listing all ups daemons loaded on my opnsense box: $ ps aux | grep ups or $ ps aux | grep nut -> no daemon seems to be loaded |
|
Is this a test system where I can have a look at? |
|
One thing I noticed: when the ups name was containing " " and "-"s it didn't work, but as soon as I changed it to "apcups" it worked correctly. |
|
Will be fixed in next Version
Florian <notifications@github.com> schrieb am So., 8. Apr. 2018, 19:33:
… One thing I noticed: when the ups name was containing " " and "-"s it
didn't work, but as soon as I changed it to "apcups" it worked correctly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#374 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATfeoec1My9Ky0ZQ8jrJmSIU7KHphtlyks5tmkncgaJpZM4QcwNO>
.
|
|
It would also be great if one could configure what address/interface uspd was bound to. |
|
You mean other than localhost, so other systems can reach upsd on the
Firewall?
Florian <notifications@github.com> schrieb am Mo., 9. Apr. 2018, 02:34:
… It would also be great if one could configure what address/interface uspd
was bound to.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#374 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATfeoS9NxF0fjoDfhI71ZUOgWMSYczxNks5tmqx5gaJpZM4QcwNO>
.
|
|
@mimugmail Yes, that's what I was thinking. I have home automation software using the UPS status as an indicator for a power outage. If I manually change the upsd.conf it's going to be overwritten, unfortunately. |
|
Can you Upload all configs without passwords? |
|
Now I got an own UPS for testing. After installation I had to reboot the firewall to get connected to the UPS: |
|
@flounderscore: If you want to be able to access the NUT server on your opnsense from your local net, you can add the following rules on the firewall: Firewall / Rules / LAN: Proto | Source | Port | Destination | Port | Gateway Put the rule just after the anti lockout one. Firewall ./ NAT / Port Forward: If | Proto | Address | Ports | Address | Ports | IP | Ports Save and restart firewal. You should be able to get info from other computers on your LAN. |
|
Good idea, so I dont have to add this function :P
nmaster2042 <notifications@github.com> schrieb am Sa., 14. Apr. 2018, 18:47:
… @flounderscore <https://github.com/flounderscore>: If you want to be able
to access the NUT server on your opnsense from your local net, you can add
the following rules on the firewall:
Firewall / Rules / LAN:
Proto | Source | Port | Destination | Port | Gateway
IPv4 TCP | LAN net | * | LAN adresse | 3493 | *
Put the rule just after the anti lockout one.
Firewall ./ NAT / Port Forward:
If | Proto | Address | Ports | Address | Ports | IP | Ports
LAN | TCP | * | * | LAN address | 3493 | 127.0.0.1 | 3493
Save and restart firewal.
You should be able to get info from other computers on your LAN.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#374 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATfeoSZxfE81vM64I-JJQaLC8XrgEEoCks5toigIgaJpZM4QcwNO>
.
|
|
@nmaster2042 Is that working for you? I had tried that before and it was not working (slight difference: I have LAN + WLAN -> bridge). Edit: You are correct, it is working perfectly. When I initially tried it from a jail that was bound to a virtual ip, it did not. |
|
@flounderscore : sorry I'm replying too late but yes it's working for me. @mimugmail : Why not add in the plugin a checkbox for auto create of these 2 rules for users who want to access their UPS info from their LAN ? |
|
@nmaster2042 I'll integrate a listen directive .. first there has to be a diagnostics page. |
|
It works for me too with the NAT Rule - thank you very much! |
|
With 18.1.7 you get version 0.5 of NUT plugin. You now have a working setup for most UPSses in standalone mode, also netserver via NAT and netclient is also available. There's a diagnostics tab refreshing every 2 seconds with the current printout of the UPS. Please try it intensivly as it seems pretty good for a 1.0 release :) |
|
Looks good an stable to me - THANK YOU SO MUCH! |
|
Sorry, please check that 0.6 is installed, otherwise the GUI will freeze when the UPS is not available |
|
PS: 0.6 is not bundled with 18.1.7 |
|
how can I update? Via GUI is no update available (still 0.5 installed). |
|
wait 30 minutes, the hotfix we needed to do will update it to 0.6 luckily |
|
Hello there, I see that this plugin is on version 1.0, but the GUI is freezed, too, when saving the configuration from the plugin page. I have a Eaton Ellipse ECO 800 connected via USB to a OPNsense virtual appliance (v18.7). It is detected on The GUI gets freezed until I kill the process from CLI: It seems that the processes are launched from the GUI, every time I access to the plugin webpage, which causes many and many calls to Maybe I am missing something, but I think that it does not require so much configuration, at least from GUI. I can test whatever you need, this is a test environment (but without access from internet). Thanks! |
|
Is your UPS supported by the driver? |
|
I think so, because it is included in |
|
I'm not sure if this also means usbhid is the correct driver. |
|
Yes, I've checked it on https://networkupstools.org/stable-hcl.html, too: EDIT: Maybe it is a cable problem, as stated on networkupstools/nut#515 . It seems that Eaton provides a very bad USB cable... Let me test it later (I have no other USB type B and need to buy a new one). |
|
Well, it was related to VMware passthrough. So I can not help anymore here because my OPNsense is a virtual machine. |
|
@fichtner please close ... |
|
since this seems to be the closest to what i am looking for, i am commenting here - up to you guys to reopen this issue or not. when enabling it through the firewall gui, there is no option to define the driver (its hardcoded in usr/local/opnsense/service/templates/OPNsense/Nut/ups.conf ) maybe we should have an option on the ups type page for USB where we can select/manually input the driver instead of hardcoding 1 driver? |
|
@thutex thx for your input. Can you open a new issue with your driver? |


I think everyone is familiar with NUT, the open source UPS software that supports just about everything http://networkupstools.org/
pfSense has a sufficiently decent plugin and UI for it (https://doc.pfsense.org/index.php/Nut_package)
It would be great to get something similar in OPNsense, it is one of the missing features stopping us from migrating our fleet of pfSense firewalls.
The text was updated successfully, but these errors were encountered: