Return to BSD News archive
Xref: sserve comp.protocols.tcp-ip:27752 comp.unix.bsd:13505 comp.unix.ultrix:21621
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bruce.cs.monash.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!ucbvax!hplabs!sdd.hp.com!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.protocols.tcp-ip,comp.unix.bsd,comp.unix.ultrix
Subject: Re: How do multi-homed hosts choose the interface?
Message-ID: <2klspcINNgqp@early-bird.think.com>
Date: 25 Feb 94 22:06:36 GMT
References: <2khb6f$9fl@breeze.dra.hmg.gb>
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 23
NNTP-Posting-Host: telecaster.think.com
In article <2khb6f$9fl@breeze.dra.hmg.gb> heading@signal.dra.hmg.gb (Anthony Heading) writes:
> I want the two routing machines to use the FDDI network to
>talk to each other, but they steadfastly refuse to use anything
>but the ethernet.
We solved this problem by putting static routes in /etc/gateways. We're
using SunOS and NIS, so we have to assign distinct names to each interface
address; in the example below, host1 would have names hostN for its
ethernet interface and hostN-fddi for the FDDI interface. /etc/gateways on
a FDDI machine looks like:
host host1 gateway host1-fddi metric 1
host host2 gateway host2-fddi metric 1
I think if we ran gated instead of routed we could configure the FDDI
machines to broadcast similar host-specific routes, so it wouldn't be
necessary to hard-code them into /etc/gateways.
--
Barry Margolin
System Manager, Thinking Machines Corp.
barmar@think.com {uunet,harvard}!think!barmar