🚀 go-pugleaf

In <tafznegebnqpbznh.g8t5vk0.pminews@news.senet.com.au>, "Graham" <fairyqueen@senet.com.au> writes:
>Injoy Connect
>
>I would appreciate help and advice with respect to Injoy Connect
>
>I have managed to successfully install and set up Injoy Connect (IC)  so that
>I can dial in remotely via Injoy Professional to the IC computer.. and I can
>ping that "box" and can "ping" my own machine back!  What I am unable to do
>is to understand the routing concepts to allow me to then 'jump' or 'hop'
>(call it what you will)  to the LAN.
>
>Details....
>
>1	LAN at office using Warp Server for e business  Fixpack 2 and TCPIP
>4.3
>	IP network using the 192.168.1.xxx system where 192.168.1.100 is the 
>file server
>	Protocols are 		Netbios
>				TCPIP
>				Netbios over TCPIP
>
>(I am still running netbios as  well as Netbios over TCPIP)

[remainder cut - see original posting]

Graham,
  Note the following reply when I had to deal with a similar situation 
a fews years ago:

=== forwarded posting ===
From: rde@tavi.co.uk (Bob Eager)
Newsgroups: comp.os.os2.networking.tcp-ip
Subject: Re: Help: PPP Connection to Warp
Date: 28 Sep 1998 23:27:54 GMT
Message-ID: <176uZD2KcidF-pn2-0fVB5Gvb1c3P@rikki>
References: <01bdea9e$285f2ba0$f0f04018@CS787735-A.cgmo1.ab.w

On Mon, 28 Sep 1998 05:00:10, "dchare" <dchare@home.com> wrote:

(posted and emailed)

> I'm looking for a bit of help with this problem. I have an OS/2 Warp system
> on a TCP/IP LAN, and have set it up to receive dialup PPP connections via
> the modem. What I want to be able to do is connect to the system from Win95
> via the modem, and have access to other computers on the LAN.

The problem is that the other machines on the same network as the Warp
machine don't know how to get to your Win95 system. So they can't 
reply to the ping.

Essentially, if a machine on the network wants to send to a particular
IP address, it broadcasts an address resolution request using ARP 
(Address Resolution Protocol).  This is picked up by the machine at 
the wanted IP address, which returns a packet with the PHYSICAL 
address of that machine on the network (the ethernet address, the 12 
digit hex number). This is then used to talk to the target system 
without broadcasting. Without that address, the low level ethernet 
driver can't communicate with a target system except via broadcasts.

OK. That's fine EXCEPT for your Win95 machine. It is never going to 
get that broadcast because it isn't on the Ethernet. Ethernet 
broadcasts won't get propagated down the PPP link. So ARP requests 
from other systems don't ever get replies so those other systems don't
know where to send things.

Solution. Make your Warp system respond not only to its OWN IP 
address, but to the IP address of the Win95 system. In both cases it 
sends back its OWN hardware ethernet address. Its own packets are of 
course processed normally. If it receives a packet for the Win95 
machine, and IP forwarding is on (default anyway even without IPGATE 
if there is more than one interface [ppp0 and lan0 in this case]) then
it will route it to the PPP link and all will work.

How to do that? Simple. This is known as proxy ARP, by the way. The 
Warp system needs to be told to respond as above. However, this means 
that the Win95 machine's IP address is visible on the Warp network. So
use an address acceptable on that network, for the Win95 machine (on 
the same subnet). You may have to get that allocated for you by 
whoever runs the LAN. And a nameserver entry would be nice too. This 
address can be used at both ends of the PPP link, I think. Then, on 
the Warp machine, publish the mapping between the IP address for the 
Win95 machine and the ethernet address of the Warp machine (to which 
all packets for the Win95 machine must be sent). Do this with:

   arp -s ipaddress aa:bb:cc:dd:ee:ff pub

where ipaddress is the address of the Win95 machine, and aa:... is the
12 digit hardware address of the ethernet interface on the Warp 
machine. 

If Tony Rall is reading this, he may well cringe and correct me. He 
isn't responsible for my mistakes, but he is responsible for any good 
stuff!!!

Thanks, Tony. Again.

-- 
Bob Eager
rde at tavi.co.uk
=== end of forwarded posting ===

  If this works you may like to put this command into tcpexit.cmd.

  I have not yet fully understood whether the above is enough or 
whether the ppp tcpip has to be bound with the LAN tcpip ...  If
necessary add the Null Mac adapter in the MPTS configuration program.
Assuming your setup has Netbeui, Tcpip and TCPBeui bound to adapters 0
& 1 set Null Mac to adapter 2. You don't have to make any change to
IBMLan.ini.

Let me know how you get on!

Victor Bien
VCB Computing Alternatives (R)
http://sydney.dialix.com.au/~vcbien/