Thanks for the info... I believe your solution works fine with the older limewire stuff but I just got hold of a limewire pro client and it works a bit differently. Seems to use random distributed ports and random other service ports to do its dirty work - none of the traffic generated by the limewire pro client showed up as p2p traffic in 2.9.46.
If it doesn't get caught as p2p traffic in the ros "p2p detection criteria" then I wouldn't really be able to use the settings you suggest to control that traffic. Again, I realize it works on the older stuff but I wanted to address if there was a way to handle the newer ways they are passing traffic.
I think in the end the only way to handle it would be to control/queue/prioritize everything you know about and throttle the rest. But that still leaves them using other service ports for their p2p service. They are playing dirty
I guess if I just wanted to block it all i could block all their IP space, but I have a feeling they have circumvented that problem too some how.
Thanks for your time -Scott