On Fri, 2004-10-08 at 23:46, [EMAIL PROTECTED] wrote:
> Yes, inbound is affected even though outbound transfers are suspended.
> The inbound in shaped to 39K. This is what totally confuses me. I thought
> with my script that only traffic leaving source ports 5-51000 & 65437
> should be sh
On Fri, 2004-10-08 at 23:46, [EMAIL PROTECTED] wrote:
> Yes, inbound is affected even though outbound transfers are suspended.
> The inbound in shaped to 39K. This is what totally confuses me. I thought
> with my script that only traffic leaving source ports 5-51000 & 65437
> should be sh
Yes, inbound is affected even though outbound transfers are suspended. The inbound in
shaped to 39K. This is what totally confuses me. I thought with my script that only
traffic leaving source ports 5-51000 & 65437 should be shaped. But it is also
shaping traffic entering my machine on t
>In theory yes, but it is shaping inbound transfers to my server.
>YOu're not doing any other sort of Ingress filters are you??
No
>I dont care about destination port. That line was commented. BUT, incoming
>transfers are being shaped for some reason.
>Could this be shaping on the ISP side??
Is the inbound rate affected even if there are no outbound transfers? Is
the speed actually being "limited" to a certain speed, or are you just
noticing that the inbound/upload traffic is slower than it should be.
The reason I ask is because you're tagging all outbound ftp-data traffic
(ports 500
>Theory is.. You can only shape outbound traffic.
Inbound is via tcp windowshaping etc..
In theory yes, but it is shaping inbound transfers to my server.
>> iptables -t mangle -A MYSHAPER-OUT -p tcp --sport 65437 -j MARK --set-mark 20
>> iptables -t mangle -A MYSHAPER-OUT -p tcp --sport 5:510
