From: Casper Gripenberg <casper.cg@gmail.com>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] Bridge with IP address -> unable to connect to bridge
Date: Mon, 07 Jan 2008 02:30:02 +0200 [thread overview]
Message-ID: <4781728A.8070108@gmail.com> (raw)
Hi,
I tried sending this earlier, but it didn't come through.
Apologies if this appers twice on the list.
I'm running bridging using the brouter setup described on
this page:
http://ebtables.sourceforge.net/examples.html
"Making a brouter".
The setup described there is like this:
ifconfig br0 0.0.0.0
ifconfig eth0 172.16.1.1 netmask 255.255.255.0
ifconfig eth1 172.16.2.1 netmask 255.255.255.0
ebtables -t broute -A BROUTING -p ipv4 -i eth0 --ip-dst 172.16.1.1 -j DROP
ebtables -t broute -A BROUTING -p ipv4 -i eth1 --ip-dst 172.16.2.1 -j DROP
ebtables -t broute -A BROUTING -p arp -i eth0 -d $MAC_OF_ETH0 -j DROP
ebtables -t broute -A BROUTING -p arp -i eth1 -d $MAC_OF_ETH1 -j DROP
My setup is different in that I use a public DHCP IP address
for eth0, and an interal private IP for eth1.
Internet <-> DHCP <-> eth0 br0 eth1 <-> my internal net
The bridge bridges traffic fine, but the problems come when
I try to access eth0 from my internal network.
I can get to eth0 fine if I access it from the internet,
but if I try to access it from my internal network then
it won't work.
The computer on the internal net has a public internet
IP (aquired from the same DHCP box that gave eth0 its
address). So that should not be the problem.
If I look at the arp table on my computer on the
internal net it has the ARP address of eth1 for the
IP of eth0. This seems correct, right?..since we want
to get to eth1 in order to jump to eth0.
Is there some way to get this to work? In the end I want
to be able to filter different ports on eth0 based on if
the traffic comes from the internet or from the internal
net. I think there is just some magic ebtables potion
that will solve it(?)..but I don't know how to make it :-/
Thanks.
Casper
reply other threads:[~2008-01-07 0:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4781728A.8070108@gmail.com \
--to=casper.cg@gmail.com \
--cc=bridge@lists.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