From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: Problems with bridge+router setup
Date: Mon, 28 Dec 2015 11:44:31 +0100 [thread overview]
Message-ID: <5681128F.5090203@plouf.fr.eu.org> (raw)
In-Reply-To: <7f5d15a0a7067992b1ae21b149d64266@vpn.quintux.com>
Misterke a écrit :
>
> Client B however is a Digital TV box and my triple-play provider
> unfortunately requires those to be directly connected to the cable
> modem, which will hand them actually a DHCP address in a particular
> range and probably do other special stuff.
Does it use VLAN tagging (IEEE 802.1q) or plain ethernet ?
> So, what I would like the RPi2 to do is:
> - For ethernet frames TO or FROM specific MAC adresses (those of
> clients of type B) on its eth1 side, just pass them on from/to eth0
> - For anything else, behave like a router and have iptables rules
> dictate what is allowed and when outputting to the eth0-side do
> NAT/masquerading
What about broadcast packets such as ARP requests or DHCP replies sent
by the cable modem ? How do you decide if they should be bridged ?
> * -A INPUT -p icmp -m icmp --icmp-type source-quench -j ACCEPT
ICMP source quench is deprecated and considered harmful.
> But I also have additional questions:
> - To act as a router, I need IP addresses at both sides of the
> bridge. At the eth0 side, that should
> be a DHCP address coming from the cable modem, but at the other end
> it should be a static address.
> Now, in the previous simple bridge setup, I already had the bridge
> get a DHCP address and I could
> even add a second static address to br0, but then those addresses
> would exist at both ends of the
> bridge, right? So, should I then create ebtables/iptables rules
> somehow to avoid that someone
> would notice the internal IP address on the internet and vice
> versa?
> - Next to that, when running dnsmasq to hand out DHCP addresses, I of
> course don't want it to start
> offering addresses to the Internet side of the bridge. So, either
> I somehow need to tell dnsmasq
> to only work on the LAN side (eth1) or perhaps I would again have
> to somehow limit this with
> ebtables/iptables.
>
> Any advice from anyone on all this?
My advice is to not use br0 but only eth0 and eth1 for IP setup, DHCP,
routing and so on.
next prev parent reply other threads:[~2015-12-28 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 11:00 Problems with bridge+router setup Kurt Haenen
2015-12-27 19:21 ` Neal P. Murphy
2015-12-28 9:57 ` Misterke
2015-12-28 10:44 ` Pascal Hambourg [this message]
2015-12-28 16:33 ` Misterke
2015-12-28 18:46 ` Pascal Hambourg
2015-12-28 20:59 ` Misterke
2015-12-28 23:28 ` Pascal Hambourg
2015-12-28 22:50 ` Neal P. Murphy
2016-01-02 11:26 ` Misterke
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=5681128F.5090203@plouf.fr.eu.org \
--to=pascal@plouf.fr.eu.org \
--cc=netfilter@vger.kernel.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 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.