- Community Home
- >
- Networking
- >
- Wireless
- >
- M and MSM Series
- >
- Heavy p2p Kill the router
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2010 04:48 AM
04-07-2010 04:48 AM
Heavy p2p Kill the router
Hi!
i've got a 20 mbit connection and a 3CRWDR101A-75 router with latest firmware. (1.12.01.A (12 Jun 2009 15:23:03).
I works very well, but recently i've discovered that the router slows down really a lot upon heavy peer to peer traffic (i've a small home server which is up 24/7 to serve my lan with mldonkey, with torrents and ed2k).
It happens that
1) pinging router gets high ping: half second and a lot of lost packets.
2) DHCP server takes a lot to serve a client (and often clients goes timeout)
3) stablishing a PPPoE connection takes more than a mite
4) pinging the first OP of my ISP takes up to 1 second
5) router browser interface does not work (firefox goes timeout)
If i just kill mldonkey daemon it works goodly all of a sudden.
I've read about this for othe 20$ routers, and it did not happened to me before (although i've always had high p2p traffic).
I've just begun using DHCP with localdomain name since this happened. (i've setup dnsmasqd to resolve internal network clients name).
What can i do?
Thanks a lot