clumsy icon indicating copy to clipboard operation
clumsy copied to clipboard

"inbound and outbound" filter doesn't work?

Open OpossumPetya opened this issue 11 years ago • 6 comments

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.

OpossumPetya avatar Aug 08 '14 08:08 OpossumPetya

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.

jagt avatar Aug 09 '14 18:08 jagt

"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.

jvanegmond avatar Sep 24 '14 06:09 jvanegmond

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

p90user1010 avatar Nov 06 '14 14:11 p90user1010

"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.

basil00 avatar Nov 15 '14 07:11 basil00

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?

drewnoakes avatar Apr 05 '15 12:04 drewnoakes

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

jagt avatar Apr 06 '15 07:04 jagt