From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4BAF5034.5060100@pandora.be> Date: Sun, 28 Mar 2010 14:48:52 +0200 From: Bart De Schuymer MIME-Version: 1.0 References: <2e59e6971003251003g34f45ccsf7feecbcb2d68cbf@mail.gmail.com> <4BABCF8A.3040701@free.fr> <4BAD1B85.6020807@free.fr> <2e59e6971003261442g77365b55sa624fe184e5003ac@mail.gmail.com> <20100327201752.51b6f7ad@nehalam> In-Reply-To: <20100327201752.51b6f7ad@nehalam> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] IP address on physcial interface instead of bridge interface? List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stephen Hemminger Cc: bridge@lists.linux-foundation.org, Joakim Tjernlund Stephen Hemminger schreef: > > If you read the network receive code path in the kernel, you > will see that there is a special hook used. Basically, > > if received_interface_is_part_of_bridge(incoming_interface) > then process_bridged_packet(packet) > > Then bridge looks at packet and decides whether it is local or forwarded. > The problem is with your application if it wants to use eth0 directly. > > The ebtables brouting chain was designed to enable you to do this. -- Bart De Schuymer www.artinalgorithms.be