[Spread-users] Configuration Matters - Network Topology

[David Lloyd]

Let's say that I have two networks:

  192.168.0.0/24
   10.  0.0.0/24

(and I have 1 or more machines in each network running Spread, and 
there's at least one machine in this configuration that has two network 
cards and consequently bridges the 192 and 10 network - let's call this 
machine the BRIDGE).

Now, let's say I have:

  192.168.1.1 (part of a 192.168.1.0/24 network)

...which also runs Spread and can route packets through to the 
10.0.0.0/24 network [but has no direct access to the 192.168.0.0/24 
network].

What I want to do is have a Spread daemon running locally on 
192.168.1.1, which will then talk to the machines on the 10.0.0.0/24 
network which then talks to the machines on 192.168.0.0/24 network.

To put this another way, how do I setup a segment so that the Spread 
Daemon on 192.168.1.1 *knows* about the BRIDGE and/or any of the other 
machines it has a route to but is not part of their network?

Currently I've tried:

# This is equiv. to 192.168.1.1
Spread_Segment 219.90.130.255 {
         localhost 219.90.130.138
}

# This is the 10.0.0.0 network
Spread_Segment  203.2.124.63 {
         nf3 203.2.124.30
}

Here's what Spread logs:

[Thu 03 May 2007 04:27:54] --------------------
[Thu 03 May 2007 04:27:54] Configuration at localhost is:
[Thu 03 May 2007 04:27:54] Num Segments 2
[Thu 03 May 2007 04:27:54]      1       219.90.130.255    4803
[Thu 03 May 2007 04:27:54]              localhost 
219.90.130.138
[Thu 03 May 2007 04:27:54]      0       203.2.124.63      4803
[Thu 03 May 2007 04:27:54] ====================

There is a Spread daemon on nf3 configured with the same configuration 
except I start taht daemone with a -n nf3.

Both these Spread daemons were built from the Spread-4.0 source tar 
balls but one is on an Ubuntu GNU/Linux (the first one called localhost) 
and the other one is a FreeBSD 6.2 (called NF3).

Needless to say, "localhost" messages/joins etc don't get sent to the 
Spread daemon on "NF3" (as I can't see them with spuser).

As is probably noticable, I'm a little fuzzy as to how to describe the 
problem I'm having...

DSL