Messages

1

19.7 Legacy Series / Re: PPPoE Suricata log flodding

« on: October 23, 2019, 10:38:11 pm »

Hello,

I am using version OPNsense 19.7.5_5-amd64 and I am seeing the same behavior as you, lots of messages like that:

Oct 23 17:15:20   suricata: [100176] <Error> -- [ERRCODE: SC_ERR_NETMAP_READ(264)] - Error reading data from iface 'pppoe1': (55u) No buffer space available
Oct 23 17:15:20   suricata: [100176] <Error> -- [ERRCODE: SC_ERR_NETMAP_READ(264)] - Error reading data from iface 'pppoe1': (55u) No buffer space available
Oct 23 17:15:20   suricata: [100176] <Error> -- [ERRCODE: SC_ERR_NETMAP_READ(264)] - Error reading data from iface 'pppoe1': (55u) No buffer space available

Best regards,
Andre

2

19.1 Legacy Series / Re: Dpinger not starting after upgrade

« on: February 04, 2019, 11:26:11 pm »

Do you really want it to only send an ICMP packet once every 30 seconds?

Thanks! I changed the Probe Interval from 30 to 20 and both Dpinger services started now.

3

19.1 Legacy Series / Re: Dpinger not starting after upgrade

« on: February 04, 2019, 03:19:38 pm »

Here are the values I use for the first Gateway:
Latency thresholds From: 400 To: 700
Packet Loss thresholds From:20 To: 40
Probe Interval: 30

Value for the second Gateway:
Probe Interval: 30

4

19.1 Legacy Series / [SOLVED] Dpinger not starting after upgrade

« on: February 04, 2019, 02:17:38 am »

After the upgrade to 19.1 my Gateways are been detected as Offline as the Dpinger service don't start. (I use Apinger before)

I don't look further because I am afraid to lost connection with this OPNsense box as I upgrade this server remotely.

Anyway I see that if I removed the information in the advanced section of the gateway, in the case of the secondary gateway the Probe Interval, the Dpinger service started normally.

I use two gateways in a Failover configuration, and temporarily I set up the gateway with the primary connection as always online setting the box "Disable Gateway Monitoring".

In the primary gateway, that I don't test as I don't want to risk lose connection and that I leave the monitoring disabled I have several options in the advanced section customized, like Latency thresholds, Packet Loss thresholds, and Probe Interval. Probably these are the reasons that the service Dpinger are not starting.

Any idea if these advanced configurations are not working with Dpinger or this is a problem caused by the upgrade and I need to reinstall and load the configuration files?