Re: Dual-Homed/Triple-Subnet Bridge Challenge

Okay Grant,

I've finally got back on site to test your configuration settings.
I'm not quite there yet, so maybe you can get me over the last hurdle.

Here's what I did thus far...

For anyone else reading this, my system is:
Ubuntu 6.06 LTS Server Edition (Dapper)

First, I needed to install the Bridge Utilies:

# apt-get install bridge-utils
# mandb

This completed OK (package is available in main repository)

Next, I needed to install EBtables:

EBtables is not in the *main* Dapper package repository.
It is however available in the *universe* repository.
So I first needed to modify my /etc/apt/sources.list file to include
universe packages.

# apt-get install ebtables
# mandb

After rebooting my system, I issued the following commands
to set up a raw bridge with no other funny stuff

# ifconfig eth0 0.0.0.0
# ifconfig eth1 0.0.0.0
# brctl addbr bri0
# brctl addif bri0 eth0
# brctl addif bri0 eth1
# ifconfig bri0 up

After issuing these commands, I waited about a minute
to allow the server to settle into it's new role in life.
 
At this point, two Zeroconf clients connected on each interface
were able to ping each other. So far so good...

Next I bound the bridge interface to it's own Zeroconf address

# ifconfig bri0 169.254.0.13 netmask 255.255.0.0

The two Zeroconf clients were still able to ping each other
and also ping the server. The server was also able to ping each
Zeroconf client. So far so good...

Next I set up slightly modified versions of your ebtables rules
specifying the ip4v protocol and ip-specific source/destination
addresses.
I assume you left these out for clarity.

# ebtables -t filter -A FORWARD -p IPv4 --ip-src 169.254.0.0/16 -j
ACCEPT
# ebtables -t filter -A FORWARD -p IPv4 --ip-dst 169.254.0.0/16 -j
ACCEPT
# ebtables -t filter -A FORWARD -j DROP

At this point, the two Zeroconf clients were still able to ping each
other
and also ping the server. The server was still able to ping each client.
So far so good...

Next I attempted to bind eth0 and eth1 to their home networks

# ifconfig eth0 192.168.3.13 netmask 255.255.255.0
# ifconfig eth1 192.168.4.13 netmask 255.255.255.0

And this is where the "happy ever after" ending did not happen!
I was unable to ping any hosts on 192.168.3.* or 192.168.4.*
or ping the Image Server from these hosts.

Any suggestions would be welcome?

BTW, I have had good reason in the past not to trust software from the
Dapper *universe* repository, particularly low level stuff like
EBtables.
The Dapper Universe version of EBtables I'm using is 2.0.6 (2003) which
is quite old. Perhaps I will need to build from latest source but I am
a bit reluctant to do this in case it upsets anything else in the stack.


Rgds,

Vincent


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/