🚀 go-pugleaf

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