This is really just a routing problem.
You probably have a route on "matt" that is set up like this:
/sbin/route add -net 192.168.0.0 dev eth1
with, perhaps, the keywords "netmask 255.255.255.0" as well if
192.168.0.0 is defined to be a "class-C" or "/24" network.
In your routing table you should see an entry like this:
192.168.0.0 * 255.255.255.0 U 0 0 eth1
This forces any request for a host on the 192.168.0.0/16 net to use the
eth1 (internal) interface. Unfortunately, "stoneboat" doesn't live there.
So you just need to add a route to "stoneboat" on "matt" like this:
/sbin/route add -host 192.168.0.50 dev cipcb0
[on my machine the CIPE interface is cipcb0, not cibcp0; i'm assuming
that's just a typo.] If you list your routing table, you'll see that
routes are sorted by their masks, so a 255.255.255.255 host mask comes
before a network mask like 255.255.255.0. That means the router will
apply the specific rule for 192.168.0.50 before it gets to the rule for
the entire network.
In general, I put my CIPE hosts on a different subnet and just route
accordingly. But if you really want it to appear within your internal
subnet, you'll need to add a host route.
On Monday 27 August 2001 2:33, you 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 seamlessly.
> 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?