🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.sys.amiga.networking
5 messages
5 total messages Started by Thomas Krantz Tue, 09 Apr 1996 23:32
Envoy + AmiTCP?
#6348
Author: Thomas Krantz
Date: Tue, 09 Apr 1996 23:32
3 lines
512 bytes
Is it possible to use AmiTCP and Envoy at the same time?
I've tried before but I didn't get it to work properly. 
I have one Adriane, one A2060 and the rest Hydranet cards.
Re: Envoy + AmiTCP?
#6350
Author: Scott J Cape
Date: Wed, 10 Apr 1996 02:01
20 lines
1551 bytes
Excerpts from netnews.comp.sys.amiga.networking: 9-Apr-96 Envoy +
AmiTCP? Thomas Krantz@sabik.tdb. (174)

> Is it possible to use AmiTCP and Envoy at the same time?
> I've tried before but I didn't get it to work properly. 
> I have one Adriane, one A2060 and the rest Hydranet cards.

Yes, it's posible.  I'm doing it right now (with Ariadne)  The only
thing is that you need the latest drivers.  The ones that were shipped
with most cards did not support multicast which is required for multiple
protocal stacks.  I've got version 1.39 of Ariadne device.

Scott Cape                                    cape@andrew.cmu.edu
=================================================================
Amiga 4000/040 25 MHz           |                Ariadne Ethernet
18 Megs RAM                     |                  CyberVision 64
120 Meg HD                      |    AmigaDOS/MacOS/MS-DOS/NetBSD
105 Meg SyQuest Removable       |                     
Emplant MacPRO (w/e586dx)       |                     SPAM RULES!
=================================================================
Re: Envoy + AmiTCP?
#6370
Author: Stefan Becker
Date: Wed, 10 Apr 1996 12:03
13 lines
993 bytes
In article <0lOlNv200YUg0HxUY0@andrew.cmu.edu> Scott J Cape <cape+@andrew.cmu.edu> writes:

> thing is that you need the latest drivers.  The ones that were shipped
> with most cards did not support multicast which is required for multiple
> protocal stacks.  I've got version 1.39 of Ariadne device.

You are confusing multicasting with SANA2 packet filters. The driver
has to support these packet filters in order to be able to separate IP
packages for different protocol stacks.

Regards,

	Stefan
Re: Envoy + AmiTCP?
#6434
Author: Th.Huber
Date: Fri, 12 Apr 1996 14:43
15 lines
1174 bytes
In article <STEFAN.BECKER.96Apr10150311@sasw41.nmp.nokia.com> Stefan.Becker@nmp.nokia.com (Stefan Becker) writes:
>In article <0lOlNv200YUg0HxUY0@andrew.cmu.edu> Scott J Cape <cape+@andrew.cmu.edu> writes:
>
>> thing is that you need the latest drivers.  The ones that were shipped
>> with most cards did not support multicast which is required for multiple
>> protocal stacks.  I've got version 1.39 of Ariadne device.
>
>You are confusing multicasting with SANA2 packet filters. The driver
>has to support these packet filters in order to be able to separate IP
>packages for different protocol stacks.


I don`t know about the adriane.device, but with the a2060.device, Envoy
and AmiTCP works great. Even copying from a remote-envoy-drive to my
PC (TCP with Linux) worked great.
Re: Envoy + AmiTCP?
#6593
Author: Heinz Wrobel
Date: Wed, 17 Apr 1996 20:24
44 lines
2339 bytes
Stefan Becker (Stefan.Becker@nmp.nokia.com) wrote:
>You are confusing multicasting with SANA2 packet filters. The driver
>has to support these packet filters in order to be able to separate IP
>packages for different protocol stacks.

And you are confusing S2R2 packet filtering with S2R2 multiple
protocol stack support. :-) The former is an optional optimization for
packet handling to reduce CPU load by the stack and the latter is a
required feature if multiple protocol stacks unaware of each other
need to be able to handle the same packet types coming from a
single driver.

packet filtering:

    Give the stack a chance to reject a packet before it is entered
    into the actual read processing of the stack.

multiple protocol stack support:

    each stack/opener receives a copy of any incoming packet
    matching a respectively pending request.

Drivers without multiple protocol stack support will return an
incoming packet only to one opener having a matching request,
usually the first one. These drviers have been obsolete now for a
long time. Complain to the manufacturer if you have problems
with one of those.

The easiest way to get a TCP/IP stack and Envoy to coexist is
simply to use an S2R2 multiple protocol stack supporting driver.
Correct functionality of the driver might be hard to verify though
and old Envoy versions unfortunately did not generate or handle IP
according to RFC. Even Envoy 2.0b is not absolutely perfect here.
So the second easiest way may be the better one for many. The
second easiest way is to change the packet numbers used for IP and
ARP in Network Configuration of the involved Envoy nodes to
something different than the TCP/IP stack defaults.

Hopefully all these problems will disappear before the end of this
year.

-- 
Heinz Wrobel        Private Mail:   heinz@hwg.muc.de
My private FAX: +49 89 850 51 25, I prefer email
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads