You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, thank you for this project, it is super useful.
On macOS, it seems that throttle works for IPv4 connections, but not IPv6:
$ throttle --up 330 --down 780 --rtt 200
Started throttler: Down:780kbit/s Up:330kbit/s RTT:200ms PacketLoss:0%
$ curl -4 -i 'https://freetestdata.com/wp-content/uploads/2022/02/Free_Test_Data_2.48MB_AVI.avi' --output /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
4 2548k 4 115k 0 0 58873 0 0:00:44 0:00:02 0:00:42 58877^C
$ curl -6 -i 'https://freetestdata.com/wp-content/uploads/2022/02/Free_Test_Data_2.48MB_AVI.avi' --output /dev/null
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2548k 100 2548k 0 0 18.4M 0 --:--:-- --:--:-- --:--:-- 18.4M
I wonder if IPv6 can be supported too? Or at least, have a word in the documentation?
Note: I used it to debug a Node.js script, and since Node 16, I needed to use --dns-result-order=ipv4first for using IPv4 over IPv6, so the connection can be throttled.
The text was updated successfully, but these errors were encountered:
Hi @BenoitZugmeyer sorry for the late answer. I wonder maybe we need to setup the rules differently? Any chance you have the time to take a look? The easiest way to see what commands that runs is: LOG_THROTTLE=true throttle cable
First, thank you for this project, it is super useful.
On macOS, it seems that
throttle
works for IPv4 connections, but not IPv6:I wonder if IPv6 can be supported too? Or at least, have a word in the documentation?
Note: I used it to debug a Node.js script, and since Node 16, I needed to use
--dns-result-order=ipv4first
for using IPv4 over IPv6, so the connection can be throttled.The text was updated successfully, but these errors were encountered: