Return to BSD News archive
Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!dptspd!TAMUTS.TAMU.EDU!news.utdallas.edu!convex!barczak
From: barczak@convex.com (Paul Barczak)
Subject: Re: SLIP
Sender: usenet@news.eng.convex.com (news access account)
Message-ID: <barczak.748207167@convex.convex.com>
Date: Thu, 16 Sep 1993 19:19:27 GMT
References: <1693258.40235.678@status.gen.nz>
Nntp-Posting-Host: dhostwo.convex.com
Organization: Engineering, CONVEX Computer Corp., Richardson, Tx., USA
X-Disclaimer: This message was written by a user at CONVEX Computer
Corp. The opinions expressed are those of the user and
not necessarily those of CONVEX.
Lines: 67
In <1693258.40235.678@status.gen.nz> craigw@status.gen.nz (Craig Whitmore,At Home ,649-292-4859,649-292-4859) writes:
>I am trying to get slip working from my Amiga to a 386BSD machine. I have set it
>it up as the FAQ's instructions on the BSD end and have followed the instructionss
>on the amiga end (Using AmiTCP or AmigaNOS).
>I can connect to the machine OK, and can telnet/ftp/ping etc the actual machine
>I can connected to, my amiga locally but anywhere else I cannot connect to (or them
>connected to me from a distant machine).
>Is there anything I have forgotten, or anything else I have to do for
>other machines to know where I am, and how to get to me?. If anyone wants any more information
>on my setup, let me know , And I can send you more information about
>it.
This sounds to me like a routing problem - the other machines on the network
need to be informed of the SLIP path to your remote machine. This can
be accomplished a variety of ways, the most "accepted" way is running routed
or gated on the machine that is directly connected to the network.
I had various snags myself when trying to run either of these, and I ran
across a proxy arp solution in the PPP faq. On my gateway, I just run:
arp -s (remote-ip-address) (gateway-ether-address) public permanent
Works great for me.
/ptb
--------------------------------------------------------------------------
Paul Barczak (ptb@convex.com) Convex Computer Corporation
(From the PPP FAQ ...)
----
~From: ignatios@theory.cs.uni-bonn.de (Ignatios Souvatzis)
If you have only one single machine on the other side, the easiest way
is to give it a IP address belonging to the local ethernet/IP subnet,
and to tell the ppp gateway machine to advertise (proxy arp) its own
ethernet address as the other machines'. Works like a charm here. Of
course, for a large group or complicated network on the other side,
you would get more management problems.
On the gateway do:
arp -s othermachinesipaddress myownethernetaddress permanent public
ifconfig pppNUMBER myipaddress othermachinesipaddress [other params] up
on remote machine:
ifconfig pppNUMBER gatewaysipaddress [other params] up
route add default gatewaysipaddress 1
pppNUMBER might be spelled as dpNUMBER for dialup IP.
Of course, if you use routeing daemons, you could also propagate the
route via routed / gated etc. to other machines, but it's more painful
because every machine has to do it (and might choose not to do it),
and every machine doing IP on a Ethernet HAS to talk arp.
On intermittently connected demand-dialed links, you may need to edit
/etc/gateways to define the destination of the PPP or SLIP connection
as a "passive" link. Otherwise, routed will remove routes from the
kernel's routing table that use that link, because it won't hear RIPs
coming from hosts or routers across the wire. Since it doesn't hear
anything from hosts or routers on the far side of the wire, routed
assumes that the link is dead forever.