All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: Gareth Williams <gwilliams@ubicom.com>
Cc: agashi shipora <gashipo@gmail.com>, netfilter-devel@vger.kernel.org
Subject: Re: br_netfilter post routing hook question...
Date: Fri, 02 Apr 2010 21:55:03 +0200	[thread overview]
Message-ID: <4BB64B97.9000203@pandora.be> (raw)
In-Reply-To: <CB2DD11991B27C4F99935E6229450D320566ACC5@STORK.scenix.com>

Gareth Williams schreef:
> Ahh but I already tried physdev - and it throws warnings that it will
> not work on forward or post routing paths when it's not on a bridge
> interface.
>
> But I was specifying the rule with "-o br0" which is a bridge so the
> physdev rule should have been sane?
>
> Even though it threw this warning it did add into iptables but still
> didn't work for me.
>
> I might revisit it and see if I can figure out what was wrong.
>
>   
I'd do that if I were you :-)
First figure out what's going on e.g. by adding rules, sending traffic
and looking at the rule counters. The iptables LOG target should produce
a string containing the physindev and physoutdev device name (the bridge
input and output port for the packet).

cheers,
Bart

-- 
Bart De Schuymer
www.artinalgorithms.be


  reply	other threads:[~2010-04-02 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 14:18 br_netfilter post routing hook question Gareth Williams
2010-04-02 17:26 ` agashi shipora
2010-04-02 17:42   ` Gareth Williams
2010-04-02 18:47     ` Bart De Schuymer
2010-04-02 19:15       ` Gareth Williams
2010-04-02 19:55         ` Bart De Schuymer [this message]
2010-04-02 19:56           ` Gareth Williams
2010-04-02 17:50   ` Bart De Schuymer
2010-04-02 17:32 ` Jan Engelhardt

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=4BB64B97.9000203@pandora.be \
    --to=bdschuym@pandora.be \
    --cc=gashipo@gmail.com \
    --cc=gwilliams@ubicom.com \
    --cc=netfilter-devel@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.