netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Haxby <john.haxby@oracle.com>
To: ratheesh k <ratheesh.ksz@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Brouter basic question .
Date: Tue, 30 Mar 2010 16:00:16 +0100	[thread overview]
Message-ID: <4BB21200.1080807@oracle.com> (raw)
In-Reply-To: <cfeab66d1003300601l140102e0nd8111713140044b5@mail.gmail.com>

On 30/03/10 14:01, ratheesh k wrote:
> Hi ,
>
>   i have a rule
>
>             ebtables -t broute -A BROUTING -j ACCEPT .
>
> So packet wont traverse any other chain ?  ( Prerouting , Input ,
> Forward , Postrouting ) ???
>    

I thought this was obvious, but on second thoughts, it's probably not as 
obvious as all that

$ man ebtables
...
                          The targets DROP and ACCEPT have a special 
meaning in
               the broute table (these names are used instead of more  
descrip-
               tive  names  to keep the implementation generic).  DROP 
actually
               means the frame has to be routed, while ACCEPT means  
the  frame
               has  to  be bridged.

and in the diagram that Jan pointed to 
(http://upload.wikimedia.org/wikipedia/commons/3/37/Netfilter-packet-flow.svg) 
it becomes clear: -J ACCEPT means that the frame goes to the ebtables 
nat table; DROP means it goes up into the network layer for iptables to 
play with.

You'll make life easier for yourself as well if you call layer two 
things "frames" and layer three things "packets".

jch



      parent reply	other threads:[~2010-03-30 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 13:01 Brouter basic question ratheesh k
2010-03-30 14:22 ` Michele Petrazzo - Unipex
2010-03-30 14:47   ` Jan Engelhardt
2010-03-30 15:00 ` John Haxby [this message]

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=4BB21200.1080807@oracle.com \
    --to=john.haxby@oracle.com \
    --cc=netfilter@vger.kernel.org \
    --cc=ratheesh.ksz@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).