Linux-Hams archive - July 1997: rspfd over ethernet. Was: confusion over routing with rspf

rspfd over ethernet. Was: confusion over routing with rspf


Sat, 5 Jul 1997 15:21:43 +1000 (EST)

Simon J Mudd is rumoured to of said:
>
> Hi Dave, no I'm just running rspfd, though I have been considering running
> routed on this machine and my main machine which are connected by ethernet
> partly to enable the "non-radio" machine to get the list of routing
> tables dynamically. I can't use rspfd over ethernet, and routed seems
> like a viable alternative, and I'm not sure if doing AX25 over ethernet
> is really worth the trouble.
You might do this if you had multiple ethernet segments. Otherwise, why
bother?

There's no real point in doing that as the other (non-radio connected)
machine has two options: direct onto the ethernet or to your radio connected
box via an ethernet. Either way, this is a static arrangement.

Now for the return path, your radio-connected box should be advertising a
node group with advertises the ethenet network or the host on that ethernet.

For example, I have a small ethernet LAN 44.136.13.16/29 so I add this to
my config with a nodegroup line so the other routers know about it.

There is one, and only one, network configuration that I have found you
would need rspf over ethernet. Two radio-connected hosts connected by
ethernet, but then what you're doing here is wierdsville anyway ;)

- Craig

-- 
  / /\  | |  Craig Small VK2XLZ <bzyewhuy@upm.es>
 |==||==|=|  Finger bfyttt.jghkoa@mailit.tunk.net for PGP key. 
  \ \/  | |  fingerprint = AD 8D D8 63 6E BF C3 C7  47 41 B1 A2 1F 46 EC 90