Monitoring for Dead Getways

[edtude]

This would be a nice feature if it worked properly. I am using the latest build of WinGate, and am using two different ISPs. One thru a cable modem, and the other thru a Motorola Canopy system. As I have stated in earlier posts my cable modem connection in the Network window of WinGate continually cycles Dead/Alive/Dead/Alive even though the link is healthy and working fine. Now I find that on the Canopy link Wingate will periodically report the Canopy link as dead as well. When this happens I can look at the properties for this link and actually see traffic passing thru the link. All I need to do to get this link to come back alive is unplug the CAT5 cable and plug it back in. The problem is that Wingate when it 'thinks' the link is dead of course does not route traffic to that port. I have disabled the Monitor for Dead Gateways and hopefully this will sewrve as my work around. Any thoughts?

[genie]

Dead gateway detection algorithm is based on ARP packets - if a gateway for some reason fails to reply to an ARP packet (due to high load, for example) - this gateway is deemed dead until the next check cycle. We are planning to extend gateway check algorithm in the next version.

[edtude]

Do we have any idea when this might be?

[edtude]

Is there anyway I can get some kind of fix for this problem, or at least an idea of when it will be fixed? This problem is not a once a week occrurence, it happens way too often thru out the day. I did check, there is no Gateway for the internal NIC. Can I get some help please!