Ethernet Bridge development
 help / color / mirror / Atom feed
From: Tom Eastep <teastep@shorewall.net>
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: netfilter-devel@lists.netfilter.org, bridge@osdl.org
Subject: [Bridge] Re: Policy match with a bridge
Date: Thu, 14 Oct 2004 00:23:16 -0000	[thread overview]
Message-ID: <416DC6EF.9050001@shorewall.net> (raw)
In-Reply-To: <200408192010.28417.bdschuym@pandora.be>

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

Bart De Schuymer wrote:
> On Monday 16 August 2004 03:31, Patrick McHardy wrote:
>
>>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.
>
>
> I'll have a look at that after I'm finished with the IPv6 bridge
firewalling
> stuff.
>

Any progress on this?

Thanks,
- -Tom
- --
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBbcbvO/MAbZfjDLIRAmBsAJsFlFdf6+c5tzT8Z5OGG/nnxoL//wCghS8L
hX2rkQdtF2v7YIwRyfRDLIY=
=6sB9
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-10-14  0:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <411EAF08.3000401@shorewall.net>
     [not found] ` <411F5D5E.4000001@trash.net>
     [not found]   ` <411F7B87.7060303@shorewall.net>
2004-08-16  1:31     ` [Bridge] Re: Policy match with a bridge Patrick McHardy
2004-08-16  1:43       ` Tom Eastep
2004-08-19 18:10       ` Bart De Schuymer
2004-10-14  0:23         ` Tom Eastep [this message]
2004-10-14  6:24           ` 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=416DC6EF.9050001@shorewall.net \
    --to=teastep@shorewall.net \
    --cc=bdschuym@pandora.be \
    --cc=bridge@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox