new 7800n packetloss lots of it.

[Mooseteets]

just installed a 7800n today and it syncs very fast but whilst using Teamspeak 3 there is constant packetloss of about 2%, if i run a game or torrent program it goes up to about 20%.

i have put on the latest firmware (1.06g) and it has not removed the problem.

http://forums.whirlpool.net.au/archive/1850663

that thread is similar to my problem but there is no solution on there, i did used to have a netgear router that had settings to prevent it being flooded and they used to affect teamspeak in the same way and they had to be tweaked before it would make the packetloss go away, im wondering if this is a similar issue.

the specific settings that stopped teamspeak having ploss were

udp flood
tcp syn flood
icmp ping of death

a screenshot of those settings> http://www.pcwintech.com/files/screensh ... re/015.png

are there any settings like this for the 7800n ?

also its only input packetloss not output (get 1% output ploss but 20-40% input), and seems to come from the router as tracerts/pings to the server im getting ploss from show nothing.

[billion_fan]

Hi

Have you tried to make changes to the intrusion detection??

1. Maximum TCP Open Handshaking Count (Max TCP Open Handshaking Count: This is a threshold value to decide whether a SYN Flood attempt is occurring or not. Default value is 100 TCP SYN per seconds.)

2. Maximum Ping Count (This is a threshold value to decide whether an ICMP Echo Storm is occurring or not. Default value is 15 ICMP Echo Requests (PING) per second.)

3. Maximum ICMP Count (This is a threshold to decide whether an ICMP flood is occurring or not. Default value is 100 ICMP packets per seconds except ICMP Echo Requests (PING)

I hope this helps

[Mooseteets]

hi, thanks for the help, changing the tcp count does affect the amount of packetloss but it does not go away, its even worse with intrusion detection disabled, i have found that adding the utorrent ports to the QOS section and setting their priority to low seems to make it go away though, there is still outbound packetloss at 2% but the inbound has completely gone which was making it unusable.