You might loko into bridging... but the simplest (ok, the one I have
experience with) is to put the jen-pete-alice-riscpc-matt network in a
different network than stoneboat. Maybe make stoneboat 192.168.1.0/24?
Then just add routes to go back and fourth.
On Mon, 27 Aug 2001, Matthew Bloch wrote:
> Hello all;
> I've successfully set up a connection between my `gateway' machine on my
> home ethernet, and my server in London, so hurrah for CIPE being easy :)
> Feel free to tell me to piss off at this point, because my problem isn't
> with CIPE, but a (presumably) common question about how to set it up
> I have a home network with a few computers that connect through my main
> Linux box (matt) doing masquerading, and a single server out in a co-lo
> facility in Fulham (stoneboat):
> jen ------ pete <
> | | ADSL >
> | Ethernet +---- matt ------> internet < stoneboat
> | | . > .
> alice ---- riscpc . < .
> . . . . . . . . . . . . . . . . .
> CIPE tunnel
> My home ethernet uses the addresses 192.168.0.1 - 192.168.0.255, and I'd
> like stoneboat to appear virtually at 192.168.0.50. My options files are
> set up like so:
> ptpaddr 192.168.0.50
> ipaddr 192.168.0.51
> #me home.soup-kitchen.net:2711
> peer stoneboat.bytemark.co.uk:2711
> ptpaddr 192.168.0.51
> ipaddr 192.168.0.50
> me stoneboat.bytemark.co.uk:2711
> peer home.soup-kitchen.net:2711
> Now the CIPE link shows from matt, but the other machines at home can't
> see stoneboat. I presume this is because 192.168.0.50 isn't an address
> that eth0 will answer for. But I'm unsure how to proceed from here; is
> there any way of `glueing' eth0 to cibcp0 so that the other machines can
> see stoneboat?