LARTC - Dec 2004 - How can I discern egress traffic than ingress traffic?

I have two interfaces, eth0 and eth1 but i can''t
discern the egress traffic than ingress traffic. I
need to apply htb qdisc in both directions, and I read
that I need the IMQ patch to do this, because in
ingress qdisc i can''t apply htb qdisc...but where is
the ingress qdisc? affect the traffic that goes from
eth0 to eth1 or is for the traffic that goes from eth1
to eth0? 


	
	
		
______________________________________________ 
Renovamos el Correo Yahoo!: ¡250 MB GRATIS! 
Nuevos servicios, más seguridad 
http://correo.yahoo.es
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Santi Anton wrote:
> 
> I have two interfaces, eth0 and eth1 but i can''t
> discern the egress traffic than ingress traffic. I
> need to apply htb qdisc in both directions, and I read
> that I need the IMQ patch to do this, because in
> ingress qdisc i can''t apply htb qdisc...but where is
> the ingress qdisc? affect the traffic that goes from
> eth0 to eth1 or is for the traffic that goes from eth1
> to eth0?
NOTE: It would have helped a lot if you had told us which interface
connects to the internet.

The interface that faces the internet is specified in the "tc qdisc
add"
command line and the data going out on that interface is egress.  What
comes in on that interface is ingress and uses a policer because
incoming packets cannot be shaped.  Look at the WonderShaper for an
example:  http://lartc.org/howto/lartc.cookbook.ultimate-tc.html

There is no "ingress qdisc".  Well, maybe IMQ makes one possible; I
don''t know.

You cannot affect the rate from one interface to another except using
iptables rate limiting for the FORWARD chain.  

In the following, eth1 is the external interface and eth0 is internal:
You can add a computer to your network that does nothing but shaping. 
It connects to the internet via eth1 and then transparently passes all
packets on to your internal network via eth0.  Google proxyARP and read
this part of the howto:  http://lartc.org/howto/lartc.bridging.html 
WARNING: I don''t think you really want a proxyARP setup, but it can
shape on both interfaces, which means you shape on eth0 to accomplish
something similar to an ingress qdisc and you shape egress on eth1.

gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

Santi Anton wrote:
> I have two interfaces, eth0 and eth1 but i can''t
> discern the egress traffic than ingress traffic. I
> need to apply htb qdisc in both directions, and I read
> that I need the IMQ patch to do this, because in
> ingress qdisc i can''t apply htb qdisc...but where is
> the ingress qdisc? affect the traffic that goes from
> eth0 to eth1 or is for the traffic that goes from eth1
> to eth0? 
You only need IMQ if you need to shape incoming traffic that is headed 
for the box that you are shaping with.

If you just need to shape LAN to internet both ways then you use say htb 
egress queues on eth0 and eth1 as the traffic coming in from the 
internet is being sent out to your LAN as egress on you LAN interface.

Andy.




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/