All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Christiansen <axel@zedx.org>
To: hare ram <hareram@sol.net.in>
Cc: netfilter@lists.samba.org
Subject: Re: Problem with bridge+iptables+ulog
Date: Thu, 13 Mar 2003 22:51:28 +0100	[thread overview]
Message-ID: <3E70FD60.2070009@zedx.org> (raw)
In-Reply-To: 078601c2e886$039a49e0$13fcc5cb@Housecall

Hello,
hare ram wrote:
> Hi all
> 
> some one can help i have the following setup
> 
> x.x.x.1/24            x.x.x.2/24
>    +------+                               +------+
>   | Router A |------+ +---------| PC B |
>    +------+              | |              +------+
>                               | |
>                         eth0| | eth1
>                           +-----+
>                             | qos | (br0 =3D x.x.x.3/24)
>                           +-----+
> 
> 
> how can i get the logs from eth0 and eth1
> 


As fare as i know you have to use the FORWARD chain and
will only get passing packet on the bridge interface. The
real interfaces (eth0 ...) only gets hit wehn it has an
ip-address asigned and the packets destination is the
bridge.

You allso need 2 more patche from the bridge project at
sourceforge.

For me the ulog works fine on the bridge. What i never
cared about was in with direction the packets walk through.

Axel

-- 
public key: http://knex.ath.cx:8013/keys/pup_key.txt



  parent reply	other threads:[~2003-03-13 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 10:25 Problem with bridge+iptables+ulog hare ram
2003-03-12 12:50 ` Arnt Karlsen
2003-03-12 15:46   ` hare ram
2003-03-13  0:01     ` Arnt Karlsen
2003-03-13 21:51 ` Axel Christiansen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12  7:20 problem " B H R Balaji

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=3E70FD60.2070009@zedx.org \
    --to=axel@zedx.org \
    --cc=hareram@sol.net.in \
    --cc=netfilter@lists.samba.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.