205b1 and bittorrent stateful packet inspection blocks

I've setup some bittorrent rules and have a question:
I'm getting alot of stateful packet blocks on the ports I've ok'ed for bittorrent when I startup bittorrent. These blocks prohibit bittorrent from d/l'ing or up/l'ing files.

But sometimes I get the stateful packet blocks and up and down loading of files works fine...

I don't know why this behavior is happening...

Is this normal with bittorrent and LnS is working properly doing the stateful packet inspection block or is there some problem or other rule I should create to allow these blocks to be accepted ??

thanks in advance,

 

I downloaded bittorent a month ago and the download contained a
trojan dropper called swicer. It also hyjacked my internet explorer.
Guessing it is calling home?

con

 

clarification....

I've been running bittorent plus v100 rc2 ...

I suppose it could be corrupted but I haven't heard/seen any note of this on net forums...

 

Perhaps too many TCP connections are open at the same time.
Look 'n' Stop is limited to 64. The next 2.05b2 will extend this number to 128.

When it will occur again, open the console, click on "Drivers Logs" and post here the content of the windows, the interesting part should be just after FW: and before FW1: .

Frederic

 

I don’t see extending the number to 128 doing much good, I think the number should be customable for each and every users own habits. I personally love to spend much time continuously downloading and much at once, using many different kinds of p2p Software, very displeased to be “required” to disable Look ‘n’ Stop TCP SPI Feature in order to do what I enjoy doing Online.

In-fact Look ‘n’ Stop is the only Firewall I’m aware of to include TCP SPI with these types of restrictions.