Date: Fri, 21 Jul 1995 15:27:27 -0400 (EDT) From: "Michael C. Newell" <mnewell@lupine.nsi.nasa.gov> To: Nik Clayton <Nik.Clayton@brunel.ac.uk> Cc: questions@FreeBSD.org Subject: Re: Routing and/or sendmail problem Message-ID: <Pine.SUN.3.91.950721152157.18317N-100000@lupine.nsi.nasa.gov> In-Reply-To: <17546.9507211634@molnir.brunel.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 Jul 1995, Nik Clayton wrote: > This is a general SOS. > > Situation > ~~~~~~~~~ > I've got one machine with two interfaces: > > tun0, kernel tunnel device used with iijppp. My ISP allocates a > static IP address, so I've put this in /etc/sysconfig. PPP works > fine. > > ep0, 3C509b network card, configured on 0x390, IRQ 11. It's > probed at boot up, gets recognised and configured properly. > > These interfaces are on two completely different networks. The tun0 > interface has the IP address 158.152.128.94 (surfs-up.demon.co.uk). > The ep0 interface has the IP address 194.159.66.50 > (elbereth.blueberry.co.uk). > > My intention is to create a local network consisting of Macs > running MacTCP, and this PC (all on the 194.159.66.0 net) and have > the PC as a gateway so that these machines can connect to the > Internet (using the tun0 interface). > I'm doing more or less the same thing; check out "http://www.newell.arlington.va.us" (one of these days I'm going to put my config in there in detail... :-) > What I've done > ~~~~~~~~~~~~~~ > a) Compiled a kernel with "options GATEWAY" in the config file. > I also include "options IPFORWARDING"; I don't know if you need it. > b) Put the following lines in /etc/sysconfig > > hostname=elbereth.blueberry.co.uk > . > . > . > network_interfaces="lo0 tun0 ep0" > ifconfig_lo0="inet localhost" > ifconfig_tun0="inet surfs-up 158.152.1.222 netmask 0xffffffff" > ifconfig_ep0="inet elbereth.blueberry.co.uk netmask 0xffffff00 link2" > When you start up, does "ifconfig -a" show "ep0" with the correct values? Also you may have to set the routed flags to "-s", the default in sysconfig is "-q". This means routed comes up in listen only mode; it doesn't announce routes. In my case my provider (the org I work for :-) requires that I RIP in my routes to them; thus "routed -q" fails whereas "routed -s" works. In your case there's no route to your internal route from your tunnel server: mnewell@lupine: ping 194.159.66.50 ICMP Host Unreachable from gateway ermin.demon.co.uk (158.152.1.98) for icmp from lupine.nsi.nasa.gov (198.116.2.100) to 194.159.66.50 ICMP Host Unreachable from gateway ermin.demon.co.uk (158.152.1.98) for icmp from lupine.nsi.nasa.gov (198.116.2.100) to 194.159.66.50 ICMP Host Unreachable from gateway ermin.demon.co.uk (158.152.1.98) ^C so either you're going to have to (a) have the owner of 158.152.1.98 install a static route to 194.159.66.0 or you'll have to RIP the route out yourself. Try killing off routed, then from root do "routed -s". Wait 30 seconds or so, then see if it helps... Thanks, Mike +--------------------------------------+------------------------------------+ |Mike Newell | The opinions expressed herein are | |NASA Science Internet Network Systems | my own, and do not necessarily | |Sterling Software, Inc. | reflect those of the NSI program, | |MNewell@nsipo.nasa.gov | Sterling Software, NASA, or anyone | |+1-202-434-8954 | else. | +--------------------------------------+------------------------------------+ | work: http://www.eco.nsi.nasa.gov/~mnewell | | home: http://www.newell.arlington.va.us | +---------------------------------------------------------------------------+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.950721152157.18317N-100000>