* [LARTC] allocating b/w
@ 2004-12-22 7:14 Payal Rathod
2004-12-22 10:36 ` Stef Coene
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: Payal Rathod @ 2004-12-22 7:14 UTC (permalink / raw)
To: lartc
Hi,
A majority of our work inolves ftp to my clients' side over our
slow connection. Now we need to allocate a greater b/w for this
protocol. Is there anyway I can do it using lartc easily?
Any suggestions on this please?
With warm regards,
-Payal
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [LARTC] allocating b/w
2004-12-22 7:14 [LARTC] allocating b/w Payal Rathod
@ 2004-12-22 10:36 ` Stef Coene
2004-12-22 15:50 ` Antonios Chalkiopoulos
` (2 subsequent siblings)
3 siblings, 0 replies; 5+ messages in thread
From: Stef Coene @ 2004-12-22 10:36 UTC (permalink / raw)
To: lartc
On Wednesday 22 December 2004 08:14, Payal Rathod wrote:
> Hi,
> A majority of our work inolves ftp to my clients' side over our
> slow connection. Now we need to allocate a greater b/w for this
> protocol. Is there anyway I can do it using lartc easily?
It can be done, but not so easy. Ftp traffic uses some random ports. But you
can filter ftp traffic if you use iptables to mark all ftp traffic (make sure
you match them all and not only the command traffic). That mark can be used
with the fw filter to put the traffic in a separate htb/cbq class.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread* [LARTC] allocating b/w
2004-12-22 7:14 [LARTC] allocating b/w Payal Rathod
2004-12-22 10:36 ` Stef Coene
@ 2004-12-22 15:50 ` Antonios Chalkiopoulos
2004-12-23 0:13 ` nix4me
2004-12-23 0:58 ` Peter Surda
3 siblings, 0 replies; 5+ messages in thread
From: Antonios Chalkiopoulos @ 2004-12-22 15:50 UTC (permalink / raw)
To: lartc
> From: Payal Rathod <payal-lartc@scriptkitchen.com>
> To: lartc <lartc@mailman.ds9a.nl>
> Subject: [LARTC] allocating b/w
>
> Hi,
> A majority of our work inolves ftp to my clients' side over our
> slow connection. Now we need to allocate a greater b/w for this
> protocol. Is there anyway I can do it using lartc easily?
> Any suggestions on this please?
>
> With warm regards,
> -Payal
Stef Coen already gave you an answer. I 'll show you another path if you wish
to follow. It requires patching the kernel , but then you will be able to do
packet filtering in Layer 7..
e.g.
filter all ftp traffic to HTB class 3:1 (which is 100kbps and can borrow
unsused traffic up to 1000kbps)
see http://l7-filter.sourceforge.net/
Antonios Chalkiopoulos
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [LARTC] allocating b/w
2004-12-22 7:14 [LARTC] allocating b/w Payal Rathod
2004-12-22 10:36 ` Stef Coene
2004-12-22 15:50 ` Antonios Chalkiopoulos
@ 2004-12-23 0:13 ` nix4me
2004-12-23 0:58 ` Peter Surda
3 siblings, 0 replies; 5+ messages in thread
From: nix4me @ 2004-12-23 0:13 UTC (permalink / raw)
To: lartc
Stef Coene wrote:
>On Wednesday 22 December 2004 08:14, Payal Rathod wrote:
>
>
>>Hi,
>>A majority of our work inolves ftp to my clients' side over our
>>slow connection. Now we need to allocate a greater b/w for this
>>protocol. Is there anyway I can do it using lartc easily?
>>
>>
>It can be done, but not so easy. Ftp traffic uses some random ports. But you
>can filter ftp traffic if you use iptables to mark all ftp traffic (make sure
>you match them all and not only the command traffic). That mark can be used
>with the fw filter to put the traffic in a separate htb/cbq class.
>
>Stef
>
>
>
You can also bind ftp traffic to a known range and mark those ports with
iptables. Thats how I do it. Proftpd allows you to set passive ports
to a certain range.
Mark
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [LARTC] allocating b/w
2004-12-22 7:14 [LARTC] allocating b/w Payal Rathod
` (2 preceding siblings ...)
2004-12-23 0:13 ` nix4me
@ 2004-12-23 0:58 ` Peter Surda
3 siblings, 0 replies; 5+ messages in thread
From: Peter Surda @ 2004-12-23 0:58 UTC (permalink / raw)
To: lartc
On Wed, Dec 22, 2004 at 02:14:16AM -0500, Payal Rathod wrote:
> Hi,
Hi.
> A majority of our work inolves ftp to my clients' side over our
> slow connection. Now we need to allocate a greater b/w for this
> protocol. Is there anyway I can do it using lartc easily?
Well, it depends on what you mean by "using lartc" :-)
> Any suggestions on this please?
There is a "helper" match in iptables that does exactly what you need. It's
already over 2 years old so I think any quite recent iptables version should
have it (1.2.11 does).
Use like
iptables -t mangle -A wherever -m helper ---helper ftp -j MARK whatever
> With warm regards,
> -Payal
Bye,
Peter Surda (Shurdeek) <shurdeek@routehat.org>, ICQ 10236103, +436505122023
--
I believe the technical term is "Oops!"
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-12-23 0:58 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-22 7:14 [LARTC] allocating b/w Payal Rathod
2004-12-22 10:36 ` Stef Coene
2004-12-22 15:50 ` Antonios Chalkiopoulos
2004-12-23 0:13 ` nix4me
2004-12-23 0:58 ` Peter Surda
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.