All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Eastep <teastep@shorewall.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org, bridge@osdl.org
Subject: [Bridge] Re: Policy match with a bridge
Date: Sun, 15 Aug 2004 18:43:43 -0700	[thread overview]
Message-ID: <4120114F.60906@shorewall.net> (raw)
In-Reply-To: <41200E80.2000005@trash.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Patrick McHardy wrote:
| Tom Eastep wrote:
|
|> | Have you applied the ipsec+netfilter patches ? Without them, packets
|> are
|> | only seen encrypted in the OUTPUT chain.
|> |
|> Yes -- the ipsec+netfilter patches are applied. Here is the same test
|> with the bridge removed and the local ip address transfered to one of
|> the network cards:
|
|
| The problem is ipv4_sabotage_out in the briding code. It prevents the
| packet from hitting the LOCAL_OUT hook while it is still unencrypted.
| When it hits the bridging code and its LOCAL_OUT hook it's too late.
| Not sure how to handle it yet.
|

Thanks for the update.

- -Tom
- --
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBIBFOO/MAbZfjDLIRAvS4AJ9eGQhcxVi09h8gmLZ/CpauSYlw1wCePgBQ
trHWmX/wZV/DyIjSz05IGyQ=
=mL/B
-----END PGP SIGNATURE-----

WARNING: multiple messages have this Message-ID (diff)
From: Tom Eastep <teastep@shorewall.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org, bridge@osdl.org
Subject: Re: Policy match with a bridge
Date: Sun, 15 Aug 2004 18:43:43 -0700	[thread overview]
Message-ID: <4120114F.60906@shorewall.net> (raw)
In-Reply-To: <41200E80.2000005@trash.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Patrick McHardy wrote:
| Tom Eastep wrote:
|
|> | Have you applied the ipsec+netfilter patches ? Without them, packets
|> are
|> | only seen encrypted in the OUTPUT chain.
|> |
|> Yes -- the ipsec+netfilter patches are applied. Here is the same test
|> with the bridge removed and the local ip address transfered to one of
|> the network cards:
|
|
| The problem is ipv4_sabotage_out in the briding code. It prevents the
| packet from hitting the LOCAL_OUT hook while it is still unencrypted.
| When it hits the bridging code and its LOCAL_OUT hook it's too late.
| Not sure how to handle it yet.
|

Thanks for the update.

- -Tom
- --
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBIBFOO/MAbZfjDLIRAvS4AJ9eGQhcxVi09h8gmLZ/CpauSYlw1wCePgBQ
trHWmX/wZV/DyIjSz05IGyQ=
=mL/B
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-08-16  1:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-15  0:32 Policy match with a bridge Tom Eastep
2004-08-15 12:55 ` Patrick McHardy
2004-08-15 15:04   ` Tom Eastep
2004-08-16  1:31     ` [Bridge] " Patrick McHardy
2004-08-16  1:31       ` Patrick McHardy
2004-08-16  1:43       ` Tom Eastep [this message]
2004-08-16  1:43         ` Tom Eastep
2004-08-19 18:10       ` [Bridge] " Bart De Schuymer
2004-08-19 18:10         ` Bart De Schuymer
2004-10-14  0:23         ` Tom Eastep
2004-10-14  0:23           ` [Bridge] " Tom Eastep
2004-10-14  6:24           ` Bart De Schuymer
2004-10-14  6:24             ` Bart De Schuymer
2004-10-16 13:30           ` [Bridge] " Bart De Schuymer
2004-10-16 13:30             ` Bart De Schuymer

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=4120114F.60906@shorewall.net \
    --to=teastep@shorewall.net \
    --cc=bridge@osdl.org \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@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.