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

How to properly slow down traffic on Raspberry? #180

Open
wawanUnic opened this issue Mar 19, 2024 · 1 comment
Open

How to properly slow down traffic on Raspberry? #180

wawanUnic opened this issue Mar 19, 2024 · 1 comment

Comments

@wawanUnic
Copy link

Hello.
Tell me how to properly slow down traffic on Raspbian?
I only use a wired connection.
I do this (Raspbian on Raspberry Pi):

  1. I checked the read-write speed before the experiment:
    beforeRead
    beforeWrite
  2. Installed iptables, iproute2 (with tc package)
  3. Installed tcconfig curl -sSL https://raw.githubusercontent.com/thombashi/tcconfig/master/scripts/installer.sh | sudo bash
  4. Set the traffic limit to eth0 with the command from the example:
    sudo tcset eth0 --rate 100Kbps
  5. I checked this installation with the command from the example:
    {
    "eth0": {
    "outgoing": {
    "protocol=ip": {
    "filter_id": "800::800",
    "rate": "100Kbps"
    }
    },
    "incoming": {}
    }
    }
  6. I check the read-write speed via FTP:
    afterRead
    afterWrite
    Nothing changed...

Question for the experts: what am I doing wrong?
Are there other working means to slow down traffic?
Maybe the Raspberry Pi needs a different solution?
Thanks for answers.

@thombashi
Copy link
Owner

Thank you for your report.

The reason the tc settings don't work is probably because you're using FTP.
Currently, tcconfig can only set protocol={ip|ip6}.
This does not work for FTP.
By making protocol=all configurable, it may be possible to enable tc settings for FTP as well.

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

No branches or pull requests

2 participants