Messages

Für einen Noob gar nicht mal schlecht   ;)

Und danke für den Beitrag im Monit How-To  :)

Bei den DHCP Leases könnte Dir dieser Thread vielleicht weiter helfen.

Hmm, scheinbar ist die ixgbe Dokumentation nicht aktuell, da der Code für 82599 im aktuellen FreeBSD enthalten ist.

Code Select Expand

# grep -lr 82599 /usr/src/sys/
/usr/src/sys/conf/files
/usr/src/sys/modules/ixv/Makefile
/usr/src/sys/modules/ix/Makefile
/usr/src/sys/dev/ixgbe/ixgbe_common.c
/usr/src/sys/dev/ixgbe/ixgbe_api.h
/usr/src/sys/dev/ixgbe/ixgbe.h
/usr/src/sys/dev/ixgbe/if_ixv.c
/usr/src/sys/dev/ixgbe/ixgbe_phy.c
/usr/src/sys/dev/ixgbe/ixgbe_type.h
/usr/src/sys/dev/ixgbe/ixgbe_dcb.c
/usr/src/sys/dev/ixgbe/ixgbe_82599.c
/usr/src/sys/dev/ixgbe/ixgbe_dcb_82599.c
/usr/src/sys/dev/ixgbe/ix_txrx.c
/usr/src/sys/dev/ixgbe/if_ix.c
/usr/src/sys/dev/ixgbe/ixgbe_mbx.c
/usr/src/sys/dev/ixgbe/ixgbe_common.h
/usr/src/sys/dev/ixgbe/ixgbe_vf.c
/usr/src/sys/dev/ixgbe/ixgbe_api.c
/usr/src/sys/dev/ixgbe/ixgbe_dcb_82599.h
/usr/src/sys/dev/ixgbe/ixgbe_82599.h

Du könntest mal schauen ob es schon einen Bug Report gibt.
Wenn nicht würde ich einen erstellen. Entweder bei OPNsense oder direkt bei FreeBSD.

Vielleicht hilft Dir aber das hier weiter:
https://lists.freebsd.org/pipermail/freebsd-net/2010-July/025873.html

Sieht so aus als ob die Karte nicht unterstützt wird:
Siehe ixgbe(4)

HARDWARE
     The ixgbe driver supports the following cards:

     o   Intel(R) 10 Gigabit XF SR/AF Dual Port Server Adapter
     o   Intel(R) 10 Gigabit XF SR/LR Server Adapter
     o   Intel(R) 82598EB 10 Gigabit AF Network Connection
     o   Intel(R) 82598EB 10 Gigabit AT CX4 Network Connection

Mail: Mailserver response error -- 553 Relaying disallowed as monit@subdomina.example.com

A mail server responsible for domain a.com should never relay mails from user1@b.com to user2@c.com.
Probably your sender address monit@subdomina.example.com is wrong. Does the account monit exists at zoho?

Better set it to the mail address of the login username.
You can set it in your Alert Settings.
Add from: user@domain.tld to the Mail format setting.

Unfortunately a complete reset is not possible.
But I've integrated a 'Import System Notification' button.
Actually, that's what you wanted, right?.
To reset Services and Tests simply remove them and afterwards reinstall the plugin.

https://github.com/opnsense/plugins/pull/563

Monit itself is a great plugin, but the OPNsense implementation has some inconsistencies IMO.
Let's start with this: if it cannot notify the user, the plugin is almost useless (I'm sorry if it sounds harsh).

Monit is a monitoring software and the os-monit plugin is a UI to the Monit configuration.
I've tried to implement the most options 1:1. So you'll find the same options as from the Monit documentation but not all in the UI.

1. The alerting (general settings) page has features specific to a general email client (like "Secure Connection"), but it cannot take hostnames, making it unusable with most public email servers.

As you know it's already in progress.

2. There is no easy way to select the OPNsense notification system. Once you have edited the Monit server settings (with plugin-validated settings - but inexistent email servers -> because of a misspelling for example), and you want to get back to the OPNsense notification system, according to https://forum.opnsense.org/index.php?topic=7103.msg32293#msg32293, you have to uninstall the plugin, export the entire OPNsense backup, edit the xml and delete the monit section, then import the backup. Just not practical and also dangerous.

The OPNsense notification system has nothing to do with the os-monit plugin.
OK, it's confusing from the users view but it's planned to integrate the plugin in core and replace the old notification system.
Would a "Reset to Defaults" Button help?

If we had a Munin expert here...
Writing OPNsense plugins is such a simple thing.  :D

You could write a script that to check the CPU temp and add it to Monit as described in the Monit HowTo (look for the CheckIPMI.sh script).

CheckCPUTemp.sh

Code Select Expand

#!/bin/csh

set MaxCPUTemp = 75

set NumCPUs = `sysctl -n kern.smp.cpus`
set CurrentCPU = 0

while ( $CurrentCPU < $NumCPUs )
   set CPUTemp = `sysctl dev.cpu.$CurrentCPU.temperature | awk '{print $2}' | awk -F. '{print $1}'`
   echo "CPU $CurrentCPU temp: $CPUTemp"
   if ( $CPUTemp >= $MaxCPUTemp ) then
      exit 1
   endif
   @ CurrentCPU = $CurrentCPU + 1
end
exit 0

My install runs with Proxmox 5.1 with virtio disk and virtio network interfaces without problems.
You could also try scsi with Virtio SCSI controller.

Maybe your install image is broken.
Are the checksums correct?

Monit imports the notification settings only on install and only if you have no Monit config from a previous install.

To remove the plugin and it's configuration uninstall it and create a backup of the OPNsense config.
Edit the backup XML and remove the <monit> section. Then restore it.
Please test this procedure before doing this on a production system.  ;)

The IP restriction comes from the plugin.
I add this to my todo list  :)

I'm not a DHCP expert but I think you could create a script and add it to the Monit as described in the Monit HowTo (look for the CheckIPMI.sh script).

CheckDHCP.sh

Code Select Expand

#!/bin/csh

set MaxLeaseCount = 500

set LeaseCount = `grep -c "binding state active" /var/dhcpd/var/db/dhcpd.leases`
echo "LeaseCount: $LeaseCount"
if ( $LeaseCount >= $MaxLeaseCount ) then
   exit 1
endif
exit 0

Thank you for the feedback.
And yes, it's better to see problems before the customers do.  :)

And no errors on the interface? I guess there aren't any.  ;)

Hmm, 360Mbps is not Gigabit. Could be that the problem is not on the Broadcom cards.
How do you measure the throughput?