search

magnific0 / wondershaper

Command-line utility for limiting an adapter's bandwidth
GNU General Public License v2.0
1.73k stars 264 forks source link

Up and Down mixed up when using iptables forward #25

Open dasfreak opened 5 years ago

dasfreak commented 5 years ago

Hi,

I am using wondershaper 1.4 to shape traffic of VMs I run. Their "host-only"-traffic is forwarded through vboxnet0 by iptables so that the VMs have internet access. Wondershaper is applied on the virtual network interface like this wondershaper -a vboxnet0 -d 4096 -u 512.

Now if testing the speed in the VM results are 512kbit download and 4096kbit upload. Wondershaper seems to misinterpret up and down in case of forwarding.

Maybe related to: https://github.com/magnific0/wondershaper/issues/6 ?

aratik711 commented 5 years ago

Hi,

I am using wondershaper 1.4 to shape traffic of VMs I run. Their "host-only"-traffic is forwarded through vboxnet0 by iptables so that the VMs have internet access. Wondershaper is applied on the virtual network interface like this wondershaper -a vboxnet0 -d 4096 -u 512.

Now if testing the speed in the VM results are 512kbit download and 4096kbit upload. Wondershaper seems to misinterpret up and down in case of forwarding.

Maybe related to: #6 ?

Any updates on this? Facing the same issue with docker0 eth.

dasfreak commented 5 years ago

Hi, I am using wondershaper 1.4 to shape traffic of VMs I run. Their "host-only"-traffic is forwarded through vboxnet0 by iptables so that the VMs have internet access. Wondershaper is applied on the virtual network interface like this wondershaper -a vboxnet0 -d 4096 -u 512. Now if testing the speed in the VM results are 512kbit download and 4096kbit upload. Wondershaper seems to misinterpret up and down in case of forwarding. Maybe related to: #6 ?

Any updates on this? Facing the same issue with docker0 eth.

I just kept it that way, just wanted to inform the developers.

magnific0 commented 4 years ago

Thanks for the heads up!! That is good to know at least. Open to PR for this bug fix. If it is easy and reliable to detect this case, it should be straightforward to reverse this.