Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command does not effect incoming traffic #50

Open
puneetpratik opened this issue Aug 21, 2016 · 4 comments
Open

Command does not effect incoming traffic #50

puneetpratik opened this issue Aug 21, 2016 · 4 comments

Comments

@puneetpratik
Copy link

./bin/comcast --latency=300 --target-bw=150 --default-bw=150 --packet-loss=3%

I see that the incoming traffic is having no effect.

@ghost
Copy link

ghost commented Aug 27, 2016

More information? Linux, BSD, Mac, Windows? Version?

@puneetpratik
Copy link
Author

Sorry, I did not get any notification for your comment, thus the delay..

Linux ubuntu 4.4.0-22-generic #40-Ubuntu

@vacuumn
Copy link

vacuumn commented Apr 25, 2017

Looks like when running on linux, only outgoing traffic is blocked, incoming traffic is still enabled:
comcast --packet-loss=100% --target-port=80 --target-addr=8.8.8.8

@dalehamel
Copy link

it looks like tc doesn't do a very good job at ingress shaping, I don't think this is likely to be fixable. Most of the functionality has to do with how the kernel actually sends packets, meaning you're better off to put this on the egress side of things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants