kern/63317: make ng_ether(4) support "lower" and "orphans"simultaneously

[Gleb Smirnoff]

The following reply was made to PR kern/63317; it has been noted by GNATS.

From: Gleb Smirnoff <glebius at cell.sick.ru>
To: Archie Cobbs <archie at dellroad.org>
Cc: Maxim Konovalov <maxim at macomnet.ru>,
	bzeeb-lists at lists.zabbadoz.net, FreeBSD-gnats-submit at FreeBSD.org
Subject: Re: kern/63317: make ng_ether(4) support "lower" and "orphans"simultaneously
Date: Mon, 26 Apr 2004 11:21:01 +0400

 On Fri, Apr 23, 2004 at 10:22:59AM -0500, Archie Cobbs wrote:
 A> Maxim Konovalov wrote:
 A> > If you manage to get a couple of spared minutes could you please take
 A> > a look at the patch in kern/63317?
 A> 
 A> So just to make sure I understand: the new semantics of having both
 A> hooks connected is that lower gets all packets and orphans would not 
 A> see any packets unless packets are also written into the upper hook
 A> (e.g., if the node connected to lower "passes through" to upper).
 
 No. Lower gets all packets which in normal way would travel into upper
 protocol stack. Orphans gets all packets which in normal way would be
 discarded. Nothing depends on behavior of the node connected to lower.
 
 The functionality of hooks does not change at all. The new behavior is
 the same as in current manpage:
 
      The lower hook is a connection to the raw Ethernet device.  When con-
      nected, all incoming packets are diverted out this hook. 
 
      The orphans hook is equivalent to lower, except that only unrecognized
      packets (that would otherwise be discarded) are written to the hook, and
      normal incoming traffic is unaffected.
 
 The only difference is that the sentence
 
      At most one of orphans and lower may be connected at any time.
 
 is not the truth anymore.
 
 -- 
 Totus tuus, Glebius.
 GLEBIUS-RIPN GLEB-RIPE