Very Computer

I can ping my local linux loopback, I can ping the slip server.  But I can't
access anything else.  I have entries for other machines, nameservers, etc. in
/etc/hosts, but they are unreachable.

Does this behavior have anything to do with /etc/diphosts?  I'm using
dip337b-uri.

Thanks,
Brandon

--
*--------------------------------------------------------*
|  LaUNChpad is a free internet service provided by but  |
|  not limited to UNC and its associates. The opinions of|
|  the users of LaUNChpad do not represent those of UNC, |

        Brandon> NNTP-Posting-Host: lambada.oit.unc.edu

        Brandon> I can ping my local linux loopback, I can ping the slip server.  But I can't
        Brandon> access anything else.  I have entries for other machines, nameservers, etc. in
        Brandon> /etc/hosts, but they are unreachable.

        Brandon> Thanks,
        Brandon> Brandon

Your problem has nothing to do with dip.  The problem is that other
machines don't know to send packets for your slip client through your
slip server.  To inform other machines that they need to do this, you
need to setup an arp proxy with your slip client's IP address and your
slip server's hardware address.  The command to do this is:

arp -s <IP address> <hardware address> pub

where IP address is the IP address of the slip client (the machine
that wants access to the rest of the net) and hardware address is the
ethernet adapter hardware address of the slip server.  The problem is
that I have yet to get proxy arp working on a linux slip server.
However, if you have root access to another machine on the same subnet
you can issue the proxy there.

Hope this helps!
-Harry

: > Your problem has nothing to do with dip.  The problem is that other
: > machines don't know to send packets for your slip client through your
: > slip server.  To inform other machines that they need to do this, you
: > need to setup an arp proxy with your slip client's IP address and your
: > slip server's hardware address.  The command to do this is:

: > arp -s <IP address> <hardware address> pub

Another practical solution is to set up a static route to your SLIP client
via the SLIP host on the default router in your LAN. After that, your default
gateway  knows how to route IP packets to your client. This works fine too.

--


Opinions are mine, not my employer's -- the answer is Forty-two

: I can ping my local linux loopback, I can ping the slip server.  But I can't
: access anything else.  I have entries for other machines, nameservers, etc. in
: /etc/hosts, but they are unreachable.

: Does this behavior have anything to do with /etc/diphosts?  I'm using
: dip337b-uri.

: Thanks,
: Brandon

: --
: *--------------------------------------------------------*
: |  LaUNChpad is a free internet service provided by but  |
: |  not limited to UNC and its associates. The opinions of|
: |  the users of LaUNChpad do not represent those of UNC, |

It sounds like your routing table is not set up to route packets destined
for unknown network numbers through your slip connection.  Check your
routing table by typing route with no parameters.  There should be a line
which shows your slip device (sl*) as a default gateway.  If this line
isn't there, you can add yourself by typing the following:
   route  add default gw 'your_slip_host_name'

You can also check your dip script.  There should be a line with one
command named 'default'.  This command will make the slip connection the
default gateway for your machine.  In my dip script the line comes right
the line which sets $mtu.

Hope this helps.

Danny Arseneau