If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

Verify advanced options are sane

Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

Set ping payload size

Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

When you reboot unit payload size goes to "0", so you need to re-set it to work again.

Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

When you reboot unit payload size goes to "0", so you need to re-set it to work again.

Cheers!

I couldn't reproduce that in my test VM. I set the payload to 1, it stuck in real-time, then I rebooted (a few times) and it starts dpinger with payload (data_len) 1 OK.

If you have a way to reproduce the problem, then start a new thread in this forum and we can look into it.

Logged

As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Myst say i was wrong. Was sure it was not sticks first three reboots for me cause mine gateway was always offline at a time. So i did it over and over again. Today i tried it couple of times just to confirm and i cannot reproduce it anymore.

If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

Verify advanced options are sane

Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

Set ping payload size

Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

- Hooo De Hooo, this worked and seems to keep working. Thank You Very Much. Verizon Actiontec modem seems to be the culprit.

I changed my payload to 1 a while back and every thing seem to be working fine, but recently i keep getting these messeges in the log again and my upload seems terrible every now and then very flakey. Can anyone offer any help with this or to why this maybe happening. I have a home virgin media cable connection 200 down and 12 up and this is only part of the log it goes on and on.

If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

Verify advanced options are sane

Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

Set ping payload size

Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

This worked for me after soooo long, I had to disable gateway monitoring for a while

When I got to Status > Monitoring I get this error: Error: JSON not returned. Check to make sure you have an active session. Tried the "verify advanced options are sane" and " set ping payload size" suggestions.

When I got to Status > Monitoring I get this error: Error: JSON not returned. Check to make sure you have an active session. Tried the "verify advanced options are sane" and " set ping payload size" suggestions.