search

jagt / clumsy

clumsy makes your network condition on Windows significantly worse, but in a controlled and interactive manner.
http://jagt.github.io/clumsy/
Other
5.27k stars 521 forks source link

"inbound and outbound" filter doesn't work? #6

Open OpossumPetya opened 10 years ago

OpossumPetya commented 10 years ago

If I use only "inbound" or only "outbound" filter it seems to affect the traffic speed. But if I put "inbound and outbound" it goes back to full speed.

jagt commented 10 years ago

Hi Petya. Please take a look at the limitation section. If you're filtering on local packets 'inbound' and 'outbound' are kind of mutual exclusive.

jvanegmond commented 10 years ago

"inbound and outbound" filter will never match any packets because packets are never BOTH inbound AND outbound. What OP might mean is "inbound or outbound" which will match all packets, but I don't see the point of doing that since not filtering will do the same.

p90user1010 commented 10 years ago

Hi Opossum,

I think you're just making a syntax mistake for what you're trying to accomplish, like I did initially. If you're looking to disrupt both inbound packets and outbound packets with Clumsy, I believe the syntax you're looking for is "inbound or outbound". Using "inbound and outbound" is telling the system to only filter packets that are simultaneously inbound and outbound, which is impossible

basil00 commented 10 years ago

"inbound and outbound" is equivalent to "false" (i.e. nothing matches) "inbound or outbound" is equivalent to "true" (i.e. everything matches)

In fact, "inbound" is just another way of writing "not outbound", and vice versa.

drewnoakes commented 9 years ago

What is the distinction between loopback, inbound and outbound? Would a loopback packet be both inbound and outbound? If that were the case, then inbound and outbound would match loopback packets, no?

jagt commented 9 years ago

@drewnoakes I think currently lookback count as outbound. This page has mentioned this and a few other things.