From owner-freebsd-net@freebsd.org  Sat Jan  6 16:31:14 2018
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7317AEC0AE2
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat,  6 Jan 2018 16:31:14 +0000 (UTC) (envelope-from zec@fer.hr)
Received: from mail.fer.hr (mail.fer.hr [161.53.72.233])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
 (Client CN "mail.fer.hr", Issuer "TERENA SSL CA 3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0252D7562D
 for <freebsd-net@freebsd.org>; Sat,  6 Jan 2018 16:31:13 +0000 (UTC)
 (envelope-from zec@fer.hr)
Received: from x23 (31.147.124.149) by MAIL.fer.hr (161.53.72.233) with
 Microsoft SMTP Server (TLS) id 14.3.361.1; Sat, 6 Jan 2018 17:29:59 +0100
Date: Sat, 6 Jan 2018 17:30:49 +0100
From: Marko Zec <zec@fer.hr>
To: John Lyon <johnllyon@gmail.com>
CC: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject: Re: Need Netgraph Help [fixed]
Message-ID: <20180106173049.48e1f044@x23>
In-Reply-To: <47C0E33A-E815-4860-A25C-F29BBB8D6787@gmail.com>
References: <CAKfTJoUMxo7gsio7JJD8Vj_xPgFx5YEBH3_XViFhR0dt59==Dw@mail.gmail.com>
 <5A3225BF.6020205@omnilan.de>
 <CAKfTJoX78JhqsvB669Gxsr5UtZkbwuZrnVhOdU2UMacF7FmP1g@mail.gmail.com>
 <5A32F63E.8010205@grosbein.net> <5A338C5A.20300@omnilan.de>
 <CAKfTJoW5H82VLyBZ_5_sa9HU7Xbot7imeiP-ogVCNkHGe0_30Q@mail.gmail.com>
 <2e0525c8-2251-a5f5-45d1-fe44ebe318f7@freebsd.org>
 <CAKfTJoXe+ZjDEMbF12-JcwBAs0uQoAFYAC3g1A_d0yM8by-z6g@mail.gmail.com>
 <ac0e236e-f27c-d4ed-8527-010dd025efff@freebsd.org>
 <4fee4ea6-9b35-afba-6d5d-24ecca3e28c6@freebsd.org>
 <CAKfTJoUuxKKkZEo5+nv98jqk3T2D77-CS-rdqvVUQE+czHpzrw@mail.gmail.com>
 <3b8d46da-75e3-79f2-379c-b27a88e80733@freebsd.org>
 <CAKfTJoXdqm0Bj+85omHg6oiKhqDNkxfW5rs9nxsqH79qdCd9Gw@mail.gmail.com>
 <47C0E33A-E815-4860-A25C-F29BBB8D6787@gmail.com>
X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd11.0)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [31.147.124.149]
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Jan 2018 16:31:14 -0000

On Sat, 6 Jan 2018 08:22:25 -0500
John Lyon <johnllyon@gmail.com> wrote:

> I just woke up with a follow-up question that may be my aha moment.
> Are Netgraph edges between nodes always bidirectional? I have been
> treating all of the edges as unidirectional, requiring me to create
> two separate Netgraphs.  But if they are bidirectional, that would
> explain some things.

edges -> hooks in netgraph parlance

man 4 netgraph -> /Hooks -> "Data flows bidirectionally between nodes"

A lot of people arrive at BSD / netgraph with previous experiences
with the Click modular router, which might have caused the confusion,
since in Click all datapaths are always unidirectional.  Not
(necessarily) so in netgraph.