From: Stephen Hemminger <stephen@networkplumber.org>
To: Balaji J <ping2balaji@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridge interface not forwarding DHCP-Broadcast
Date: Tue, 13 Dec 2016 11:16:49 -0800 [thread overview]
Message-ID: <20161213111649.4d983c5f@xeon-e3> (raw)
In-Reply-To: <CAAtMjxYTtqk3f5ucZuhP=Uv+bJR7NEYPXrB_vUtX+MpzoMt78Q@mail.gmail.com>
On Tue, 13 Dec 2016 23:45:52 +0530
Balaji J <ping2balaji@gmail.com> wrote:
> Thanks Stephen.
> Can i attach an interface with IP assigned to it already/statically to a
> bridge?
> So if i understand correctly from your response, i should run dhcpclient on
> br0 interface to assign IP for the same? and Lets say br0 gets an IP
> assigned by DHCP-Server as "12.0.0.1".
>
> Now my intention is to assign IP address to the Host(say host1) behind
> Router-1 using the DHCP-Server running on/behind Router-2 as shown below:
> Host1 <------> (eth2)[Router-1](eth1:100.1.1.1) <----------EoGRE
> Tunnel----->(eth0:100.1.1.254)[Router-2](DHCP-Server)
>
> So i thought Bridging eth2 to eth1 in Router-1 is the only way to achieve
> the same as i want the dhcp-broadcast packet from Host-1 to get tunneled
> over EogRE till Router-2. Is this assumption correct? or i am missing
> something here?
>
> Or i should not assign any IP to eth2 and instead do it in br0 in Router-1?
>
> Any guidance would be very helpful and greatly appreciated.
>
> Thanks,
> ...Balaji.J
The problem is that the IP address on an enslaved interface is not used
by the IP stack and packets destined for that address tend to be blackholed.
Packets being sent out get put on the enslaved interface and only sent
out that interface not bridged.
next prev parent reply other threads:[~2016-12-13 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 15:43 [Bridge] Bridge interface not forwarding DHCP-Broadcast Balaji J
2016-12-13 17:41 ` Stephen Hemminger
2016-12-13 18:15 ` Balaji J
2016-12-13 19:16 ` Stephen Hemminger [this message]
2016-12-14 2:03 ` Balaji J
2016-12-14 8:01 ` Srinivas M.A.
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=20161213111649.4d983c5f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bridge@lists.linux-foundation.org \
--cc=ping2balaji@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