Re: altq on what interface on a bridged setup
> At 11.55 08/11/2004, you wrote: > > > [router]-->[ext_if]-->[inf_if]-->[LAN] > > > bridge > > > > > > Should I only apply queueing on the ext_if? > > > >The problem is when datas are knocking at the door of a NIC, they're > >already here, and it's too late to preserve bandwidth. > > > >So, it's better to use queueing on internal interface of your bridge for > >ingoing datas (which are going to the LAN), even if your lan is certainly > >faster than a Web connection. > > Hi all, > > if I have to shape ingoing AND outgoing datas on a trasparent bridge, > is it ok to apply queueing to both interfaces, ignoring > the FAQ raccomandation? How that said Alexandre - when you have incoming data in your router that is to late to queuing that trafic. But using altq with ecn for that trafic you could slow down incoming stream , and in result you have good shaping for bigger streams (eg. transfer from ftp server, downloading sth. from www) and worser for small packets like ICMP-Ping >From OpenBSD FAQ (about ECN) : "Explicit Congestion Notification (ECN) works in conjunction with RED to notify two hosts communicating over the network of any congestion along the communication path. It does this by enabling RED to set a flag in the packet header instead of dropping the packet. Assuming the sending host has support for ECN, it can then read this flag and throttle back its network traffic accordingly. " Maybe somebody know how ECN work exactly? Darek
Re: altq on what interface on a bridged setup
Kenneth Oncinian wrote:
So does this mean that I need to define and use 2 queues?
Yes, that's what I do. One queue for outbound and another for inbound
although I seem to recall someone (Henning?) saying that you
could give the queues the same name thus making them at least look
like only one queue.
ex:B
altq on $ext_if priq bandwidth 768Kb queue { http0, default }
queue http0 priority 10
queue default priq(default)
altq on $int_if priq bandwidth 768Kb queue { http1, default }
queue http1 priority 10
queue default priq(default)
pass out quick on $ext_if proto tcp from any to any port 8080 queue http0
pass out quick on $int_if proto tcp from any port 8080 to any queue http1
Yes, this looks fine to me except i would use $int_if:network instead of
'any' where applicable and use keep state, ie:
pass out ... from $int_if:network to any port 8080 queue http0 keep state
pass out ... from any port 8080 to $int_if:network queue http1 keep state
---
Lars Hansson
Re: altq on what interface on a bridged setup
Hi Lars,
Thank you for the response,
No, you apply queueing to both BUT you can only
queue outgoing traffic *on that interface*.
So on ext_if you'd queue outbound traffic and
on int_if you'd queue inbound traffic.
Note that you cant really queue traffic that is
being sent *to you* directly since by the time
the packet get to your machine it's already
gone over the wire. All queueing that applies
to inbound traffic is indirect.
So does this mean that I need to define and use 2 queues? One for
$ext_if and one for $int_if and apply queueing to the outgoing traffic
on that interface? or use 1 queue and define both outgoing data on
both interface to that queue?
ex: A
altq on $ext_if priq bandwidth 768Kb queue { http, default }
queue http priority 10
queue default priq(default)
pass out quick on $ext_if proto tcp from any to any port 8080 queue http
pass out quick on $int_if proto tcp from any port 8080 to any queue http
or
ex:B
altq on $ext_if priq bandwidth 768Kb queue { http0, default }
queue http0 priority 10
queue default priq(default)
altq on $int_if priq bandwidth 768Kb queue { http1, default }
queue http1 priority 10
queue default priq(default)
pass out quick on $ext_if proto tcp from any to any port 8080 queue http0
pass out quick on $int_if proto tcp from any port 8080 to any queue http1
?
regards,
Kenneth
Re: altq on what interface on a bridged setup
Kenneth Oncinian wrote: I read that you should only queue on your outgoing interface. Does this rule also apply on a bridged setup? So in my setup: [router]-->[ext_if]-->[inf_if]-->[LAN] bridge Should I only apply queueing on the ext_if? No, you apply queueing to both BUT you can only queue outgoing traffic *on that interface*. So on ext_if you'd queue outbound traffic and on int_if you'd queue inbound traffic. Note that you cant really queue traffic that is being sent *to you* directly since by the time the packet get to your machine it's already gone over the wire. All queueing that applies to inbound traffic is indirect. --- Lars Hansson
Re: altq on what interface on a bridged setup
At 11.55 08/11/2004, you wrote: > [router]-->[ext_if]-->[inf_if]-->[LAN] > bridge > > Should I only apply queueing on the ext_if? The problem is when datas are knocking at the door of a NIC, they're already here, and it's too late to preserve bandwidth. So, it's better to use queueing on internal interface of your bridge for ingoing datas (which are going to the LAN), even if your lan is certainly faster than a Web connection. Hi all, if I have to shape ingoing AND outgoing datas on a trasparent bridge, is it ok to apply queueing to both interfaces, ignoring the FAQ raccomandation? Regards Fabrizio -- Alexandre Anriot [EMAIL PROTECTED]
Re: altq on what interface on a bridged setup
> [router]-->[ext_if]-->[inf_if]-->[LAN] > bridge > > Should I only apply queueing on the ext_if? The problem is when datas are knocking at the door of a NIC, they're already here, and it's too late to preserve bandwidth. So, it's better to use queueing on internal interface of your bridge for ingoing datas (which are going to the LAN), even if your lan is certainly faster than a Web connection. -- Alexandre Anriot [EMAIL PROTECTED]
altq on what interface on a bridged setup
Hi List, I read that you should only queue on your outgoing interface. Does this rule also apply on a bridged setup? So in my setup: [router]-->[ext_if]-->[inf_if]-->[LAN] bridge Should I only apply queueing on the ext_if? Thanks and best regards, Kenneth
