From: "Chris K Ellsworth" <cke@highlandshighspeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Shape and Bridge which Interface to use?
Date: Tue, 11 Jun 2002 18:41:44 +0000 [thread overview]
Message-ID: <marc-lartc-102382095913469@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102378492009591@msgid-missing>
Have you patched your kernel to allow access the bridge packets?
http://bridge.sourceforge.net
and also note that from what i have learned you had to use iptables,
prerouting mangle table, to mark the packets then use tc filiters to put the
packets into a qdics for shapping. and you could only shap out going traffic
you can also check out the bridges list serve @ bridge@math.leidenuniv.nl
they are a good source for bridging problems
Chris
----- Original Message -----
From: "ALBRECHT, BENJAMIN" <BENJAMIN.ALBRECHT@de.thalesgroup.com>
To: <lartc@mailman.ds9a.nl>
Sent: Tuesday, June 11, 2002 1:35 AM
Subject: [LARTC] Shape and Bridge which Interface to use?
hi list,
if tested linux bridging with the tc commands. but the kernel did not
recognized my commands. the commands are from some howto´s. the should be
correct. must i use the "bridge-interface"?
not eth0 and eth1? anyone some progress report to this situation?
thank you
greetings benny
--
Mit freundlichen Grüßen / Best regards
THALES COMMUNICATIONS GmbH
Benjamin Albrecht
Dept.: DP/CIT
Tel.: +49-7231-15-3962
Fax.: +49-7231-15-3813
eMail: Benjamin.Albrecht@de.thalesgroup.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-06-11 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 8:35 [LARTC] Shape and Bridge which Interface to use? ALBRECHT, BENJAMIN
2002-06-11 18:41 ` Chris K Ellsworth [this message]
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=marc-lartc-102382095913469@msgid-missing \
--to=cke@highlandshighspeed.net \
--cc=lartc@vger.kernel.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.