All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Hardware reqs for 10Mbps forwarding and shaping.
Date: Tue, 15 Apr 2003 16:52:23 +0000	[thread overview]
Message-ID: <marc-lartc-105042577703576@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105040881412423@msgid-missing>

On Tuesday 15 April 2003 15:55, Jay Wineinger wrote:
> > > Ideally I'd like to use a bridged solution, so if it screws up, the
> > > user can simply unplug the cables, and join then with a cable joiner.
> > > Is this just asking for trouble? I know I would have to use 2.5.47???,
> > > which I'm not really familiar with, how stable is 2.5 ATM?
> >
> > You can use kernel 2.4.20 and configure it as bridge.  If you want to
>
> control
>
> > the traffic, you also need ebtables (this is iptables for a brdige).
>
> I was under the impression that you didnt NEED ebtables for qos as you can
> just shape on both interfaces involved in the bridge and use tc filters for
> matching packets. Please correct me if Im wrong.
Indeed.  You don't need it.  But it can be handy if you want to mark the 
packets and use the fw filter.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

      parent reply	other threads:[~2003-04-15 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 12:12 [LARTC] Hardware reqs for 10Mbps forwarding and shaping Cameron Kerr
2003-04-15 13:28 ` Stef Coene
2003-04-15 13:55 ` Jay Wineinger
2003-04-15 13:55 ` Jay Wineinger
2003-04-15 16:52 ` Stef Coene [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-105042577703576@msgid-missing \
    --to=stef.coene@docum.org \
    --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.