Re: SLIP slidin' away...

[knarf@nasim.nasim.cube.net (Frank Bartels)]

Chris Herborth (cherborth@semprini.waterloo-rdp.on.ca) wrote:

> On the Linux end (aka 'bbs'), I was using 'dip' to set up my
> connection... diphosts is set up correctly there AFAIK, and everything
> on that end appears to work properly.  When I log in as my 'dip'
> account, it tells me the IP address of bbs (100.1.0.1), my IP address
> (100.0.0.1), and my netmask (255.255.0.0).

You have a routing problem. I assume these are phantasy-IP-addresses, so
you should choose a pair of addresses, which are in the same subnet:

# According to RFC 1597, you can use the following IP networks for
# private nets which will never be connected to the Internet:
#
#        10.0.0.0        -   10.255.255.255
#        172.16.0.0      -   172.31.255.255
#        192.168.0.0     -   192.168.255.255
#
# In case you want to be able to connect to the Internet, you need
# real official assigned numbers.  PLEASE PLEASE PLEASE do not try
# to invent your own network numbers but instead get one from your
# network provider (if any) or from the Internet Registry (ftp to
# rs.internic.net, directory `/templates').

So just give `bbs' the 192.168.0.1 and the MiNT-machine the
192.168.0.2 and set the netmask to 0xffffff00 (which should be default
for class-C networks anyway). The just add the route for 192.168.0.0
network on both machines. If you don't have an ethernet-card in your
PC you will run into troubles because of Linux' braindead network
handling.

> Everything looks sorta like it should work (at least the IP addresses
> match, and I don't get any errors), but when I do some tests, they don't
> work.  I've tried:

I assume you have set the defaultroute to the slip-interface on your
MiNT-machine, but there is no routing entry for the MiNT-machine on
`bbs'. So every packet will go through the slip-interface if it's not
the local host, but the remote host (bbs) doesn't know how to send
back the packages. If you try ping MiNT-machine on `bbs', you'll get
either a "network is unreachable" or if you have a defaultroute on the
linux box to another network interface.

> ping says 100% packet loss, telnet and ftp don't appear to time-out but

I think this is a bug anywhere in MiNT-Net. I've seen these "never
time out" problems very often.

> they never connect, and udpprobe immediately fails.  Watching my modem
> lights, I can see the send-data light is flickering (especially during
> ping, naturally), but receive-data never lights.

Sure, the packet's don't know how to come back to your MiNT-machine.

Bye,
Knarf
-- 
    Frank Bartels    |      UUCP/ZModem: + 49 89 5469593       | MiNT is
knarf@nasim.cube.net | Login: nuucp Index: /pub/ls-lR.nasim.gz | Now TOS!