All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abraham van der Merwe <abz@frogfoot.net>
To: lartc@vger.kernel.org
Subject: [LARTC] more bridging + qos confusion
Date: Tue, 04 Mar 2003 17:14:33 +0000	[thread overview]
Message-ID: <marc-lartc-104679858822902@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]

Hi!

If I create the following setup:



 66.8.28.52/29            66.8.28.51/29
  +------+                  +------+
  | PC A |------+ +---------| PC B |
  +------+      | |         +------+
                | |
            eth1| | eth0
              +-----+
              | qos | (br0 = 66.8.28.49/29)
              +-----+

PC A is connected to qos via crossover cable and PC B and qos is plugged
into same switch. So even though everything is on the same network, traffic
has to go through qos when PC A talks to PC B.

Now, if PC A ping PC B, then my packet counters on the PREROUTING, INPUT,
FORWARD, OUTPUT, POSTROUTING chains stay the same for both filter and mangle
tables - i.e. netfilter don't see any traffic flowing through the machine.

Why is this? How do I match this traffic using netfilter? I can't use
ebtables because I have to match traffic in the mangle table if I want to
use it in conjunction with tc.

-- 

Regards
 Abraham

By the yard, life is hard.
By the inch, it's a cinch.

___________________________________________________
 Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks
 P.O. Box 3472, Matieland, Stellenbosch, 7602
 Cell: +27 82 565 4451 Http: http://www.frogfoot.net/
 Email: abz@frogfoot.net


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2003-03-04 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04 17:14 Abraham van der Merwe [this message]
2003-03-04 17:23 ` [LARTC] more bridging + qos confusion Martin A. Brown
2003-03-04 17:29 ` Abraham van der Merwe
2003-03-04 17:43 ` Martin A. Brown
2003-03-04 18:01 ` Abraham van der Merwe
2003-03-04 18:22 ` Abraham van der Merwe

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-104679858822902@msgid-missing \
    --to=abz@frogfoot.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.