From: Simone <mimmo@ats.it>
To: netfilter@lists.netfilter.org
Subject: Iptables - Bridge - QOS - MPLS
Date: Fri, 17 Mar 2006 10:52:51 +0100 [thread overview]
Message-ID: <441A86F3.8030704@ats.it> (raw)
Hi all..
I'm working on a very interesting project about Iptables .. bridging
server.. qos.. well managing traffic you can see.
The situation is easy.
lnx server --- router A --- router B --- lnx bridge box --- router C
--- client
What i need to do is shape the traffic from/to "client" to "lnx server".
On a normal IP situation this is not hard to configure and all is
working good.
I'm able to shape any kind of traffic, working at layer7 with special rules.
The problem is over the second step.
I had the MPLS protocol over the 3 routers.
The traffic from/to server still work naturally but iptables over the
lnx bridge box isen't able anymore to TAG the traffic and shape it.
So what i ask..
Where i can found the right patches and the support for MPLS for linux ?
iptables need to be patched too ?
I'm sure . searching over various newsletter that there are some
experiments out.. anyone could help me to resolve this situation ?
Thanks in advice for any good reply.
Simon
reply other threads:[~2006-03-17 9:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=441A86F3.8030704@ats.it \
--to=mimmo@ats.it \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.