> In my home network, there is a traffic shaper rule that deprioritizes 
> 6881-6999 source traffic, and a separate rule that deprioritizes 
> 6881-6999 destination traffic. All is well for incoming connections, 
> because the incoming Azureus ports in the network are within that 
> port range. However, I think that there is trouble with outgoing 
> connections going to non-standard ports. When I use TCPView, I see

I had exactly the same problem with my Emule. The fact that Emule 
clients could be configure to DO not use the standards ports, made my 
traffic shaper rules almost useless.

Following is the solution I came up with: block *all* the outgoing 
connections as default, and allow only Emule connections to the 
standard Emule ports.

This made sure that, my emule connections where matched always by the 
appropriate traffic shaper rules. The downside is that -- I´m not able 
to connect to emule clients using non-standard ports -- but for me this 
is acceptable.


But still - I ask to the mailing list: Isn´t out there a traffic 
shaping application that can match traffic depending on the type of the 
highlevel-protocol? Something that can recognize "emule" packets, 
"azureus" packets" (as many network analyzer do) instead of classifying 
connections based on the classic sourceip/destinationip 
sourceport/destinationport etc etc?

-Gianluca Bosco


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



----- End forwarded message -----


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.