Article View: comp.sys.amiga.networking
Article #6430Re: Envoy + AmiTCP?
From: Reto Burkhalter
Date: Thu, 11 Apr 1996 08:41
Date: Thu, 11 Apr 1996 08:41
16 lines
1083 bytes
1083 bytes
>> Robert Hardy >> 09.04.1996 RH> Basically you have two choices to make it work, both documented in the RH> AmiTCP manual (P 40-41 section 6.3). One is to set the `FILTER' option for RH> each device in the AmiTCP:db/interfaces file. The other method is to set RH> Envoy's IP Type and ARP Type to something different for what AmiTCP uses. RH> I used 17999 & 18000. The former method is a little faster. Oops, I just use different IP adresses, all the rest is default. And it works. Reto
Technical Details
Message-ID:
<xbP3qMD4F99aLz3@borki.zug.use.ch>Path:
arc1-ca.pugleaf.net!turicum.use.ch!zug.use.chReferences:
<19960409.4B0C08.14C7A@dork.tvinet.com>Show Full Headers
Complete Article Headers
From: BORKI@zug.use.ch (Reto Burkhalter) Subject: Re: Envoy + AmiTCP? Message-ID: <xbP3qMD4F99aLz3@borki.zug.use.ch> Date: Thu, 11 Apr 96 8:41:14 GMT Path: arc1-ca.pugleaf.net!turicum.use.ch!zug.use.ch Organization: Turicum Communications References: <19960409.4B0C08.14C7A@dork.tvinet.com> X-Gateway: ZCONNECT UE turicum.use.ch [PolyNet Amiga RFC/ZC V4.23 no. 599198gr45qW-017] X-Mailer: MicroDot 1.10 [REGISTERED 004f99] Newsgroups: comp.sys.amiga.networking MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit