Strange behavior behind Tomato router

[1bird2]

DDWRT does all that and it does it better.

Won't get into "mine is better than yours" argument. But, DDWRT does NOT do it all -- out of the box. You should check your info. There are many open source (and free) plug-ins you can add to DDWRT, to allow some of the things that Tomato does. I will just leave it at that.....

[Darrena]

I fixed my issue with Tomato by setting:
Advanced->Conntrack / Netfilter->UDP ->Unreplied to 10 seconds from 30 seconds

[bwarden]

I fixed my issue with Tomato by setting:
Advanced->Conntrack / Netfilter->UDP ->Unreplied to 10 seconds from 30 seconds

That's a good idea. Due to unrelated issues, I reset my Tomato router today, and had to clean up the mess again. I did the following at the console to avoid a flash write:

# cat /proc/sys/net/ipv4/ip_conntrack_udp_timeouts
30      180
# echo 0 0 > /proc/sys/net/ipv4/ip_conntrack_udp_timeouts
# cat /proc/sys/net/ipv4/ip_conntrack_udp_timeouts
0       0
# echo 30 180 > /proc/sys/net/ipv4/ip_conntrack_udp_timeouts
# cat /proc/sys/net/ipv4/ip_conntrack_udp_timeouts
30      180

And it worked...

You can check the current states via:

# cat /proc/net/ip_conntrack