Messages

I read back through my posts in this thread.  And it looks like there needs to be a space between content= and "blocked".   So content=<space>"blocked"  it's hard to see.  That was my issue when I first set this up as well it appears. 

Just checked it. No spaces. Maybe bug in version 21.1.4?

Guess that's def possible, mine works but was working in prior versions.  So maybe it's a setup issue with latest version of monit?  And you are sure you are seeing new events written by suricata since you've setup monit? 

Hey,

I've done the following setting by here: https://docs.opnsense.org/manual/monit.html

If i change something on monit i get email, but i get no mails from suricata if package were "blocked". Dont know where the problem is.

Here my settings:

https://prnt.sc/11bsti8
https://prnt.sc/11bsuvw
https://prnt.sc/11bsw24

Someone any idea where the problem is? There are "blocked" alerts in the "eve.json" because i test it and see it in the logs. Ive restart both services.

Your screenshots look correct to me.  Any weird spaces after or before the file path? 

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

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. 

@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.

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 Expand

# 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 Expand


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


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 Expand

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


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?

Here are my current error logs.

Code Select Expand

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

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

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.   

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 8)

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 Expand

opnsense-patch 45199e3


That's always appreciated, thanks in advance! :)

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