*BSD News Article 91863


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!rill.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.utell.co.uk!usenet
From: brian@shift.lan.awfulhak.org (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 2.2-RELEASE + PLIP = problem
Date: 24 Mar 1997 13:29:30 GMT
Organization: Awfulhak Ltd.
Lines: 35
Message-ID: <5h5vjq$fpf@ui-gate.utell.co.uk>
References: <5gm6f1$ukc@hecate.umd.edu> <5gmguh$icd@ui-gate.utell.co.uk>
    <5gu6k6$bm9@ui-gate.utell.co.uk> <5gvfb7$pen@hecate.umd.edu>
Reply-To: brian@awfulhak.demon.co.uk, brian@utell.co.uk
NNTP-Posting-Host: shift.utell.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37680

In article <5gvfb7$pen@hecate.umd.edu>,
	marat@Glue.umd.edu (Marat Fayzullin) writes:
>: Can you "draw" what's going on (in ascii) ?  ie. what are the IP
>: numbers and netmasks of each machine.  It may be that the laptop
>: has an IP number that's part of the network that the other machines
>: share - this should not work.....
> Mhm...That is true: both sides of PLIP link (gateway and laptop) have IP
> numbers from the same domain as all the ethernetted machines (including
> the router). I did try it with numbers from a different domain, but it
> didn't work either (although the circumstances were different from
> described in the last post).
> 
> I'm going to experiment with this stuff on Monday though, and try to
> figure out what exactly is wrong.

It should really look something like this:

-----------          -------------------------
| 1.2.3.2 |---PLIP---| 1.2.3.1       1.2.4.1 |---Ethernet (netmask ffffff00)
-----------          -------------------------

If the machines on the ethernet think that the laptop is sharing the
ethernet, they'll try to ARP the laptop (to determine its MAC address).
This won't work.  If they know it's on a different network, they'll use
whatever router they can (hopefully 1.2.4.1), ARPing for it's MAC address
instead.

In the current environment, hey must be ARPing and failing, all the way up
until the laptop sends something.  Then they see that the MAC address to
use is the routers.

-- 
Brian <brian@awfulhak.demon.co.uk> <brian@freebsd.org>
      <http://www.awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour !