*BSD News Article 22109


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!doc.ic.ac.uk!uknet!cf-cm!paul
From: paul@myrddin.isl.cf.ac.uk (Paul)
Subject: Re: SLIP network problem
Message-ID: <1993Oct9.051546.6674@cm.cf.ac.uk>
Keywords: SLIP, routing
Sender: news@cm.cf.ac.uk (Network News System)
Organization: Intelligent Systems Lab, ELSYM, University of Wales, Cardiff
References: <293qla$ect@dlsn31> <kd.750099708@laotzu> <1993Oct8.192453.19322@emba.uvm.edu>
Date: Sat, 9 Oct 1993 05:15:45 +0000
Lines: 40

In article <1993Oct8.192453.19322@emba.uvm.edu> wollman@aix5.emba.uvm.edu (Garrett Wollman) writes:
>In article <kd.750099708@laotzu>, Kostis Dryllerakis <kd@doc.ic.ac.uk> wrote:
>>	The problem can be more generally put as: what do you need
>>	to do when you connect to a machine on a subnetwork A.B.C as
>>	part of the same subnet (e.g. get assigned A.B.C.yoU) in order
>>	to see the rest of the subnetwork (from the side of the machine
>>	you connect to maybe?)
>
>You can't.  Some other systems support a hack which allows you to make
>this ``work'', but doing so definitely voids your warranty as far as
>correct network operation goes.
>
>Now that that's out of the way, here's what you can do (given the
>caveat that I STRONGLY recommend against doing this, and instead do it
>properly as IP was designed to operate):
>
>- Make sure that your kernel is compiled with the GATEWAY option.  You
>should probably also compile with SENDREDIRECTS set to zero, since
>Net/2 doesn't even come close to meeting the Router Requirements.
>
>- When the point-to-point link is up, you can do
>	arp -s remote.ip.add.ress yo:ur:et:he:rn:et pub
>
>on the well-connected host, and this will cause that host to proxy ARP
>for the other.
>

Hmm, I'm not 100% clear what you're suggesting but in general proxy ARP
won't work on gateways with *BSD.

If you add an arp entry for the well connected side it will catch
packets for the proxy address but it won't send them out the other side
because the arp table says to catch them! What's needed (and exists in
those OS's that can do this) is a private arp table for each interface.

-- 
  Paul Richards, University of Wales, College Cardiff

  Internet: paul@isl.cf.ac.uk
  JANET: RICHARDSDP@CARDIFF.AC.UK