Email Server stops responding after being pinged by 3.0rc3

RouterOS The Dude
1

The closest topic to our problem was the HP printers hanging after being probed by The Dude; but it’s not quite the same problem.

We have The Dude on a 10.0.0.0 network and it was set up to ping an email server on a public IP address going through a NAT router. As soon as the email server was pinged it stopped responding to any and all IP traffic from the 10.0.0.0 NAT router. As soon as the public IP address on the NAT router was changed, we were able to ping the email server again through the router. We have experienced the same behavior with both a linux-based NAT router and a Mikrotik Routerboard set up as a NAT router. The email server is running the Blue Quartz software by Nuonce.

Any suggestions would be much appreciated :slight_smile:.

Oh, we will be installing version 3.1 soon to see if this behavior will go away but it has been happening in 3.0rc3 and our previous version of 2.2 (stable).

2

Dude uses standard ping, you can open “Probes” and see what kind of packets is used for the Ping service.
In case your e-mail server stops responding by standard ping, the problem should be looked on the server itself, as any other device can generate the same packet and ruin your server.