Ethernet Bridge development
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: bridge@lists.linux-foundation.org,
	Joakim Tjernlund <joakim.tjernlund@transmode.se>
Subject: Re: [Bridge] IP address on physcial interface instead of bridge interface?
Date: Sun, 28 Mar 2010 14:48:52 +0200	[thread overview]
Message-ID: <4BAF5034.5060100@pandora.be> (raw)
In-Reply-To: <20100327201752.51b6f7ad@nehalam>

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


  parent reply	other threads:[~2010-03-28 12:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 16:42 [Bridge] IP address on physcial interface instead of bridge interface? Joakim Tjernlund
2010-03-25 17:03 ` richardvoigt
2010-03-25 20:24   ` Joakim Tjernlund
2010-03-25 21:03     ` Nicolas de Pesloüan
2010-03-26  7:44       ` Joakim Tjernlund
2010-03-26  8:55         ` Bart De Schuymer
2010-03-26  7:55       ` Joakim Tjernlund
2010-03-26 20:39         ` Nicolas de Pesloüan
2010-03-26 20:48           ` Joakim Tjernlund
2010-03-26 21:35             ` Nicolas de Pesloüan
2010-03-27 10:42               ` Joakim Tjernlund
2010-03-28 15:19               ` Joakim Tjernlund
2010-03-28 16:03                 ` Stephen Hemminger
2010-03-28 16:19                   ` Joakim Tjernlund
2010-03-26 21:42             ` richardvoigt
2010-03-27 10:50               ` Joakim Tjernlund
2010-03-28  3:17                 ` Stephen Hemminger
2010-03-28  9:53                   ` Joakim Tjernlund
2010-03-28 12:48                   ` Bart De Schuymer [this message]
2010-03-28 18:27                     ` Joakim Tjernlund
     [not found]                     ` <OFDC6DBFAF.3C46B16B-ONC12576F4.00654457-C12576F4.00655D53@LocalDomain>
2010-03-28 19:04                       ` Joakim Tjernlund
     [not found]                       ` <OF59D1A758.6E7DFF8C-ONC12576F4.0068613D-C12576F4.0068C11D@LocalDomain>
     [not found]                         ` <OF66063C34.9F68251B-ONC12576F5.0025FFA1-C12576F <4BB05AE7.10905@pandora.be>
     [not found]                           ` <OF35408968.E095E27C-ONC12576F5. <4BB06A0E.9000705@pandora.be>
2010-03-29  6:57                         ` Joakim Tjernlund
2010-03-29  7:46                           ` Bart De Schuymer
2010-03-29  8:34                             ` Joakim Tjernlund
2010-03-29  8:51                               ` Bart De Schuymer
2010-03-29  8:59                                 ` Joakim Tjernlund
2010-03-29  9:31                                   ` Bart De Schuymer
2010-03-29  9:48                                     ` Joakim Tjernlund

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=4BAF5034.5060100@pandora.be \
    --to=bdschuym@pandora.be \
    --cc=bridge@lists.linux-foundation.org \
    --cc=joakim.tjernlund@transmode.se \
    --cc=shemminger@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox