🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.os2.networking.misc
Article #28

Re: Routing for OS/2

#28
From: Bruce Clarke
Date: Thu, 08 Sep 1994 07:48
68 lines
3613 bytes
In article <343pu5$g8v@juniper.almaden.ibm.com> trall@trall.almaden.ibm.com (Tony Rall) writes:

> Routing a LAN (office) machine via SLIP to a home machine
> ---------------------------------------------------------
>  
>          SLIP link
>   S1-------------------S2/I1---(the office network)
>   home                 office
>  

I'm planning to make my home machine part of the office network using proxy
arp as explained in the proposed FAQ. However, I would also like to have a
second home machine and cannot get approval for a separate home subnet. I'm
considering the possibility of having a private home network of two machines
when SLIP is not running, and having the home machines function as part of
the office net when SLIP is up. My home machines (without SLIP) would work

    L1 ------------------- L2
    home1		   home2

as a private network if L2 were the default route of L1 and vice versa.

When SLIP is up the result would be

				     SLIP link
    L1 ------------------- L2/S1-------------------S2/I1---(office net)
    home1		   home2		  office

I'm wondering if this can be made to work with proxy arp. The machines with
two interfaces require two IP addresses, so 5 IP addresses on the office net
would be needed.

If SLIP is running, and if home2 is set up as in the FAQ, does home2 need an
additional routing table entry to reach home1? How about configuring home2
with:

	 route -f add default S2 1
	 route add L2 L1 12

Home1 is the tricky part. If home1 uses home2 as the default route, wouldn't
packets originating at home1 that are sent to the office net be forwarded
properly by home2 to the other office machines?

To make home1 visible to the office net, could proxy arp be used?
Suppose the office machine executed

	 arp -s S1 12:34:56:78:90:12 pub

where 12:... is the MAC address of home1. Wouldn't this cause packets on the
office network that are destined to home1 to be sent to the office machine,
then to home2 and ultimately to home1?

I'm a novice so I'd appreciate advice on whether this is likely to work before
I try it.

If it won't work, and if my private home network is running, what commands
should home2 give when a SLIP connection is made so that home2 is on the
office network and the link to home1 is either disabled or does not cause
problems?


--
Bruce Clarke, Dept of Chemistry, University of Alberta,
              Edmonton AB, Canada, T6G 2G2

bclarke@gpu.srv.ualberta.ca
voice (403) 492-5739
fax (403) 492-8231
Technical Details
Message-ID: <940908074839@hydra.chem.ualberta.ca>
Path: arc1-ca.pugleaf.net!nntp.gmd.de!newsserver.jvnc.net!rutgers!sgigate.sgi.com!sgiblab!swrinde!gatech!newsxfer.itd.umich.edu!nntp.cs.ubc.ca!unixg.ubc.ca!quartz.ucs.ualberta.ca!hydra.chem.ualberta.ca!bruce
References: <1994Aug31.051152.25439@lugb.latrobe.edu.au> <343pu5$g8v@juniper.almaden.ibm.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10a752,d1169684aef35f98
X-Google-Attributes: gid10a752,public
X-Google-Thread: 106983,d1169684aef35f98
X-Google-Attributes: gid106983,public
X-Google-Thread: 100b63,d1169684aef35f98
X-Google-Attributes: gid100b63,public
X-Google-ArrivalTime: 1994-09-08 10:39:57 PST
Path: arc1-ca.pugleaf.net!nntp.gmd.de!newsserver.jvnc.net!rutgers!sgigate.sgi.com!sgiblab!swrinde!gatech!newsxfer.itd.umich.edu!nntp.cs.ubc.ca!unixg.ubc.ca!quartz.ucs.ualberta.ca!hydra.chem.ualberta.ca!bruce
From: bruce@news.srv.ualberta.ca  (Bruce Clarke)
Newsgroups: comp.os.os2.networking.misc,comp.os.os2.networking.tcp-ip,aus.computers.os2
Subject: Re: Routing for OS/2
Date: Thu, 08 Sep 1994 07:48:39
Organization: Computer and Network Services, U of Alberta, Edmonton, Canada
Lines: 69
Message-ID: <940908074839@hydra.chem.ualberta.ca>
References: <1994Aug31.051152.25439@lugb.latrobe.edu.au> <343pu5$g8v@juniper.almaden.ibm.com>
Reply-To: bclarke@gpu.srv.ualberta.ca
NNTP-Posting-Host: hydra.chem.ualberta.ca
NNTP-Software: PC/TCP NNTP