Messages

226

21.1 Legacy Series / Re: Proper way to officially request a feature?

« on: March 23, 2021, 07:57:54 pm »

Here https://github.com/opnsense/core/issues/new?assignees=&labels=&template=feature_request.md&title=

Make sure to fill out the extended information about use case, motivation and alternatives as they help speed up the triage process and request being picked up eventually.


Cheers,
Franco

Awesome thanks @Franco

227

21.1 Legacy Series / Proper way to officially request a feature?

« on: March 23, 2021, 05:57:57 pm »

Have a few features I'd like to request but not sure the proper way of going about it.  Is it just a post here, or a post on git hub?  Some other form? 

Thanks for the guidance. 

228

General Discussion / Re: Help getting NUT working with CyberPower UPS

« on: March 22, 2021, 05:01:48 pm »

@genesysguy editing the ups.conf file fixed it.  It works now.  I had some extra lines too.

Now that it's added I assume OPNsense will now power down if the battery gets critical? Didn't see any config for that part so assume that's predefined somewhere else.

229

General Discussion / Re: Help getting NUT working with CyberPower UPS

« on: March 22, 2021, 04:52:42 pm »

I did a fresh install yesterday and ran into the same issue with my Cyberpower UPS.

When I looked into the ups.conf file located at /usr/local/etc/nut, I noticed that opnsense was adding several (3) configs for the ups in the file.  I removed the configs that didn't pertain and was left with:

# Please don't modify this file as your changes might be overwritten with
# the next update.
#
[CP1500PFCLCD]
driver=usbhid-ups
port=auto


After saving and rebooting, it worked.  But since there isn't a widget for the UPS like in pfSense, I'm wondering why I wasted so much time mucking with it.

This might explain something too, my config file is pretty much blank.

Code: [Select]

# Please don't modify this file as your changes might be overwritten with
# the next update.
#
MODE=standalone
~
~


You are looking at nut.conf, not ups.conf

Correct, nut.conf

EDIT: I'm dumb I misread what you posted. 

Code: [Select]

root@OPNsense:/usr/local/etc/nut # vi nut.conf
# Please don't modify this file as your changes might be overwritten with
# the next update.
#
MODE=standalone


230

General Discussion / Re: Help getting NUT working with CyberPower UPS

« on: March 22, 2021, 04:13:19 pm »

I did a fresh install yesterday and ran into the same issue with my Cyberpower UPS.

When I looked into the ups.conf file located at /usr/local/etc/nut, I noticed that opnsense was adding several (3) configs for the ups in the file.  I removed the configs that didn't pertain and was left with:

# Please don't modify this file as your changes might be overwritten with
# the next update.
#
[CP1500PFCLCD]
driver=usbhid-ups
port=auto


After saving and rebooting, it worked.  But since there isn't a widget for the UPS like in pfSense, I'm wondering why I wasted so much time mucking with it.

This might explain something too, my config file is pretty much blank.

Code: [Select]

# Please don't modify this file as your changes might be overwritten with
# the next update.
#
MODE=standalone
~
~


231

General Discussion / Re: Help getting NUT working with CyberPower UPS

« on: March 22, 2021, 02:45:39 am »

Dang, unfortunately my ups is USB only, surprised that's been broken so long.

The current version on github seems to work fine, but without a release since 2016 it's almost impossible to update the FreeBSD package.

How can install the version from github?  Any downsides to sideloading like that?

232

General Discussion / Re: Help getting NUT working with CyberPower UPS

« on: March 22, 2021, 02:44:49 am »

Here are my current error logs.

Code: [Select]

2021-03-21T21:43:01 root[43795] /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
2021-03-21T21:43:00 upsmon[94899] upsmon parent: read
2021-03-21T21:42:58 upsmon[95263] UPS [CyberPowerUPS]: connect failed: Connection failure: Operation already in progress
2021-03-21T21:42:27 upsmon[95263] UPS [CyberPowerUPS]: connect failed: Connection failure: Operation timed out
2021-03-21T21:42:04 root[81548] /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut

233

General Discussion / Re: Help getting NUT working with CyberPower UPS

« on: March 21, 2021, 09:00:24 pm »

Did you reboot the opnsense?  It seems to have to do a reboot with the UPS plugged in to detect it.  Then it is using the USBHID as UPS type.

It works for me on my CyberPower CST135XLU which is about 3 years old, so don't know why it wouldn't work for you.  The key is even on pfsense it requires a reboot.

I did reboot.  I'm getting errors in the system log as well.  When I get back home I'll post up my syslog errors.

Sent from my IN2025 using Tapatalk

234

General Discussion / Re: Help getting NUT working with CyberPower UPS

« on: March 21, 2021, 07:32:40 pm »

NUT and the USB HID driver are broken on FreeBSD because they are using an unsupported legacy API. According to information I got on their mailing list they have implemented the new API, but since they have not tagged a release since 2016, that code has not made it into any FreeBSD package, yet.

Your best bet (IMHO) is to get a network card for your UPS if available and use SNMP.

Dang, unfortunately my ups is USB only, surprised that's been broken so long.   

235

General Discussion / Help getting NUT working with CyberPower UPS

« on: March 21, 2021, 07:19:44 pm »

Finally decided to connect my ups to my firewall via USB and setup NUT to gracefully shut it down during power outages.  Seemed pretty simple using the documentation here https://docs.opnsense.org/manual/how-tos/nut.html, but my diagnostics tab stays blank like it's not connected.  I verified that my ups is supported using the USBHID driver https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500AVRLCD.html, so I'm thinking I'm just missing some simple something. 

Edit: Just noticed the Nut Daemon isn't running and won't start for some reason.

Anyone have any pointers and/or any shell commands I can run to help troubleshoot the issue?

Thanks

236

21.1 Legacy Series / Re: Dashboard problem after update to 21.1.3

« on: March 14, 2021, 09:27:26 pm »

goto the shell and issue the following command:


opensense-patch 45199e3


Refresh your browser.


Fixed.

The command you posted has a typo. Should be "opn" instead of "open".   

Code: [Select]

opnsense-patch 45199e3


237

21.1 Legacy Series / Re: New traffic widget broken in Firefox

« on: February 24, 2021, 09:39:11 pm »

That's always appreciated, thanks in advance!

Done. https://github.com/opnsense/core/issues/4750

238

21.1 Legacy Series / Re: New traffic widget broken in Firefox

« on: February 24, 2021, 08:32:11 pm »

https://github.com/opnsense/core/commit/8b9764fa86

# opnsense-patch 8b9764fa86

On a sadder note: no bugs related to this raised in the issue tracker so far...


Cheers,
Franco

I don't have a github account but I guess I can  create one to report a bug, if that's helpful .

239

21.1 Legacy Series / Re: New traffic widget broken in Firefox

« on: February 24, 2021, 06:14:19 pm »

Broken in Chrome. Works in Edge .

Wow that looks goofy.  Mine are just blank in firefox.  My Chrome doesn't look all janky like that.  Really strange.

Sent from my IN2025 using Tapatalk

240

21.1 Legacy Series / New traffic widget broken in Firefox

« on: February 24, 2021, 05:09:43 pm »

Looks like the new traffic widget in 21.1.2 look like it isn't working in Firefox for some reason.  Seems to work ok in other browsers, anyone else seeing this or is it just something in my specific Firefox?