Perfect!!!
Now, it's time to learn about scheduling with application rules...
I'm hoping that will shut out farwarded port requests during specific hours ?
What I've found... (Moderators/D-Link please see last paragraph(s))
Note: that the bottle neck (for P2P/torrents)
is the page size of the active connections. I've seen on TOM'S that the EBR-2310 has an active connection count of 32. (Active connections get swapped in and out VERY rapidly, so that number (32 slots) can act large.
Both the Port Farwarding and Application Rules allow schedules. I'm testing them at the same time, So I don't know if they both work individually (I imagine, as it's only the scheduler that is in charge).
I've set it (the Router) up so that I only Torrent (uTorrent) on a forwarded port between 11pm & 6am.
I've also scheduled uTorrent to throttle WAY back during off hours, and allowing it to go full blast from 11mp-6am. Even though my P2P client (uTorrent) can't use port farwarding, TCP still works via http.
So, at least something is getting done until it (farwarding) gets allowed by the router.
Throttling back active torrents, and connections per torrent (torrent client side) and disallowing port farwarding (via Router) solves the 'active connection' issue with the router, and allows pretty good WAN access for my other three PCs during peek (daytime) hours.
The Connection Queue is
MUCH larger, but STILL a bottle neck.
(The connection Queue is full of messages [packets] in limbo, they are: either wanaby connections or connection packets that are marked for death.)
Looking at the Connection 'Queue' (Viewed Via 'active connections' [misnomer?] of status screen), I've noticed that whenever my torrent client (uTorrent) starts, it broadcasts my farwarded port (sends out on the farwarded port, saying 'I'm Here')... REGARDLESS if the modem has it blocked via the scheduler. I assume that message never gets out when the scheduler says not to... and, I never get any replies, so it must.
ALSO... that 'I'm here' message sits in the router's connect queue waiting to be discarded for the 300 seconds (5 Min.). when I set active torrent's in uTorrent (the client) to 600 (as it was), the connect queue would be flooded to overflowing; thus, halting any other Internet activity.
uTorrent will also RE-broadcast the farwarded port to any new swarm member (local seed/peer) coming on the scene. The Connection Queue seemes almost always topped/tapped out. (I don't know it's size!... anyone?)
All of these 'I'm here' message/packets are 'marked for death'... but they hang around in the connection queue for an alloted time slowly waiting to expire... in the hot confines of our router (wishing, if only I had a life).
So... the bottle necks are the router's Active Connection Max (32), and the Connection Queue (xxx?).What to Do...
uTorrent MUST broadcast the "I'm here" message, or else port farwarding will NEVER work (P2P clients can't know that port farwarding has been turned of or disabled, AND NEVER SHOULD).
The only other thing I can think of... aside from spending hundreds on a new router/network system/setup... is to limit the amount of time that dying packets hang around in the Queue. (I think this is an OS setting... Not the router's.)
Here's the rub... With this OS setting, ALL connections are effected. Anything in the 'active connections' box will be removed that much sooner. Also, packets in the queue that are NOT slated for death will also be removed with just as much speed. (I believe 'active' connections are bumped to the queue in favor of the highest/oldest queued priority item. [once bumped out of active, I don't know what the new queued priority is...?])
I will (for those interested) post the registry key to set the connect timeout, when/if I find it.
(This is not the same thing as - how long it takes IE of Firefox to say that a site timedout..)
NOTE TO ALL & D-LinkTHE SMART THING IS TO HAVE A FIRMWARE UPDATE... to have the router toss those 'waiting to die'/blocked packets away... as soon as possible. There is no reason for them. They will NEVER come back alive. If, someone squeals about not having info of 'slated for death' packets, have a timeout entry the application & port farwarding setups, or even a few second note in the 'Active Connections' is better than them hanging around for the alloted (default 5 minutes) kill time. (As 'Active Connections' is not a dynamic screen.)
THIS IS SOO EASY TO DO, and Increases your product performance considerably (exponential for P2P users)! With the BEFSR41 v3 now dead, you'd have the best low end router for P2P, EVER!! (It was the best, they missed the boat on v4.xx... why I now have this D-Link.)
I REALLY like this router's performance and capabilities (aside from it's P2P shortfalls, which described mod may help, at least in part). The Setup options/capabilities are FAR superior to the Linksys probably even the BEFSX41, at a fraction of the cost. (My BEFSR41 v3 fried during a power short, I replaced with a BEFSR41 v4.3... It was trouble within half an hour... I returned it... Bought this EBR-2310... pocketed $16 and am content... not happy... content that it's the best a few $ will buy... and hopeful that there's a new update coming soon ;-)
The reason I can think of NOT to do this is that you want P2P to stop, and that you're getting a kickback.
The best way to do that is a NEW FIRMWARE UPGRADE... That includes this feature... (I hope Someone is listening ;-)).