From: Bart De Schuymer <bdschuym@pandora.be>
To: Jean-Michel Hautbois <jhautbois@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] [ebtables]Explanation of the packet flow...
Date: Sat, 16 Jan 2010 19:10:39 +0100 [thread overview]
Message-ID: <4B52011F.9020805@pandora.be> (raw)
In-Reply-To: <8cad0aa1001160948r37f19d43v3ab090110574e3d3@mail.gmail.com>
Jean-Michel Hautbois schreef:
> 2010/1/16 Bart De Schuymer <bdschuym@pandora.be>:
>
>> Jean-Michel Hautbois schreef:
>>
>>> Hi everybody !
>>>
>>> I am trying to understand the "PacketFlow.png" image from the website.
>>> I have several misunderstanding, especially on the "Bridging Decision" circles.
>>>
>>> I would like to understand which way a packet takes when the rule on
>>> -A INPUT -j ACCEPT is on, for example. When looking at the packet
>>> flow, I would say it is going to the "routing decision" circle, but, I
>>> am not sure...
>>>
>>>
>>>
>> It is handed to the IP layer, which includes a routing decision.
>>
>
> But this is only true for L3 layer ?
> Or routing decision is at a L2 level, in order to decide whether to
> bridge should route a packet up to the IP layer or not. That's it ?
>
>
The packet flow picture describes the detailed IP packet flow. This is
clearly mentioned in the accompanying document. If you don't know on
what layer routing is done, please try looking it up.
>>> I would also like to understand what is necessary in order to have a
>>> packet transparently directed from one interface to the other. I would
>>> say that only the "-A FORWARD -j ACCEPT" rule is necessary, but
>>> Wireshark doesn't agree with me...
>>>
>>>
>>>
>> Ebtables is used to filter bridged traffic. You can't use ebtables to
>> direct a packet to another interface.
>>
>
> Well, when a bridge is between two interfaces, this is quite the same
> than saying it is forwarded from one to the other, in my point of
> view. No ?
>
>
The bridge indeed forwards the packets, not ebtables. You don't need
ebtables for that unless you want to filter the traffic.
Bart
--
Bart De Schuymer
www.artinalgorithms.be
next prev parent reply other threads:[~2010-01-16 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 8:16 [Bridge] [ebtables]Explanation of the packet flow Jean-Michel Hautbois
2010-01-16 11:53 ` Bart De Schuymer
2010-01-16 17:48 ` Jean-Michel Hautbois
2010-01-16 18:10 ` Bart De Schuymer [this message]
2010-01-17 17:26 ` Jean-Michel Hautbois
2010-01-17 17:47 ` Bart De Schuymer
2010-01-17 18:14 ` Jean-Michel Hautbois
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=4B52011F.9020805@pandora.be \
--to=bdschuym@pandora.be \
--cc=bridge@lists.linux-foundation.org \
--cc=jhautbois@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 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.