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

Most networks are asymmetric #17

Open
dtaht opened this issue Jan 30, 2015 · 4 comments
Open

Most networks are asymmetric #17

dtaht opened this issue Jan 30, 2015 · 4 comments

Comments

@dtaht
Copy link

dtaht commented Jan 30, 2015

So you really need to emulate 20Mbit down/5 up, 50 down/10 up, 8mbit down 1up. Etc.

@tylertreat
Copy link
Owner

Agreed, this would be ideal.

@ghost
Copy link

ghost commented Jan 30, 2015

At current, it's a slight more strange (at least on Linux thus far, I haven't delved into ipfw quite yet) to affect ingress traffic as it is egress traffic using traffic control. There's ways to do it I have not yet researched, but will be soon after I've finished other work. This is on my personal todo list with regard to this project.

There's something to be said for possibly ditching use of traffic control (on linux) and doing everything in pure iptables rules which might solve this entirely, I still need to look into the ramifications of what would be lost by that switch. Perhaps @tylertreat might know this answer?

@tylertreat
Copy link
Owner

Yeah, using iptables on Linux might be a better long-term solution. I went with traffic control because it was simple and did just what I needed for the initial iteration. Since this is a program meant to simplify these tools, it would be nice to expose some really interesting/useful features out through a simple, easy-to-use interface which is as cross-platform as possible. That's really my goal for it, anyway.

@raek
Copy link

raek commented Sep 23, 2020

You might already have seen this already, but there is a way to use an IFB to "convert ingress traffic to egress" so that tc can be used: https://serverfault.com/a/386791

A limitation is that one IFB is needed per interface, and a fixed number of IFBs are allocated statically at modprobe time. So if the number of interfaces varies, then this might be difficult to use.

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