On Friday 16 April 2010 04:06:37 Xi Shen wrote: > On Fri, Apr 16, 2010 at 2:55 AM, Stroller > > <strol...@stellar.eclipse.co.uk> wrote: > > How are you connecting to the net? > > yes, i connect to the net through a router. and i share the router > with my roommates. > > > Are you sure this isn't the router? Have you tried switching it off and > > back on again? (seriously) > > i do not think so. if it is the router has the problem, all people > using that router will suffer the same problem. but it is only me have > this problem.
Not necessarily, it might have a limited NAT-table per host, rather then a single one. > > > There is a tendency in BitTorrent to fill up the NAT tables of routers > > with insufficient RAM. I cannot explain why this would appear not to > > affect ping. > > my BT client use a fix port to connect to the net, and i guess it > cannot configure the NAT table of the router. The NAT-table is automatically filled with all the running connections to the outside world. This table is how the router keeps track of which packets need to be forwarded to which machine behind the NAT-router. Not all routers clear the cache quickly enough and most have a tendency to get filled with these. It's exactly because of this that I refuse to use a "plug-n-pray" router and use a Linux box for this purpose. I would still try Stroller's suggestion and turn the router off and on (But leave your computer running). It will only affect the connection briefly and if it resolves the issue, it will then be clear the problem is the router. If the problem then still exists, the issue is somewhere else and we can try to find it. -- Joost
