Re: [mpls-linux-general] iptables traffic eng.
Status: Beta
Brought to you by:
jleu
|
From: James R. L. <jl...@mi...> - 2004-03-29 14:03:51
|
Why do you want to use FORWARD entries? I've only tried using MPLS + iptables in OUTPUT entries. FORWARD entries haven't gone through IPv4 output processing and are not ready to be hadned off to another layer (ie MPLS). Do things work as expected if you remove the FORWARD entries? On Mon, Mar 29, 2004 at 03:27:03PM +0200, Zordan Arres wrote: > Hi, > > i've set up a little MPLS network under rh9. > I use 4 pcs in the Core network and 2 Edge Routers to > bind 2 different networks together: one with 192.168.0.0/24 > and the other 192.168.1.0/24. > now i wan't to divide different classes of traffic. e.g. > route ssh over one edge of the core net and everything else over another. > > i tried to use iptables with the following commands: > iptables -t mangle -A FORWARD -p tcp --dport 22 -j MPLS --set-key 0x2 > iptables -t mangle -A OUTPUT -p tcp --dport 22 -j MPLS --set-key 0x2 > > and > iptables -t mangle -A FORWARD -d 192.168.1.0/24 -j MPLS --set-key 0x3 > iptables -t mangle -A OUTPUT -d 192.168.1.0/24 -j MPLS --set-key 0x3 > > but every time i changed the FORWARD-Entries the LER alway ignored my > changes. > The only thing that worked is to reboot them ... is this a bug or did i > forget something ?? > > regards > > Zordan Arres > > -- > +++ NEU bei GMX und erstmalig in Deutschland: T?V-gepr?fter Virenschutz +++ > 100% Virenerkennung nach Wildlist. Infos: http://www.gmx.net/virenschutz > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > mpls-linux-general mailing list > mpl...@li... > https://lists.sourceforge.net/lists/listinfo/mpls-linux-general -- James R. Leu jl...@mi... |