From owner-freebsd-current@freebsd.org Mon Jul 17 05:50:20 2017 Return-Path: Delivered-To: freebsd-current@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 AA34ACFC819 for ; Mon, 17 Jul 2017 05:50:20 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27B7B7307C; Mon, 17 Jul 2017 05:50:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.117.19]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M0tr1-1dmBvI2U5n-00v8ra; Mon, 17 Jul 2017 07:50:11 +0200 Date: Mon, 17 Jul 2017 07:50:02 +0200 From: "O. Hartmann" To: Ian Lepore Cc: "O. Hartmann" , FreeBSD CURRENT Subject: Re: netgraph: documentation issue? What kernel options? Where to find? Message-ID: <20170717074645.53ac20a7@thor.intern.walstatt.dynvpn.de> In-Reply-To: <1500244180.22314.61.camel@freebsd.org> References: <20170716224834.030e004b@thor.intern.walstatt.dynvpn.de> <1500244180.22314.61.camel@freebsd.org> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/g9wtycGJj/uhL3YM0Lp8p0t"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:j5Icyy0Vfn2KVf8NVCw0rJZ62udsoXRAIHJNfCU4tLHdDsexNoZ spobFkbb3KFBv+ppV7j9QFfR7S6ne1QpTr62zRWEH3hCPvl+K8Cf8Q4zRp+9L/jNMrmyIBO dawBSSg+dihzgsdYnb/x4v/mpDOp3yYmmv/Ittaom8RzZ7SWRhryb54FRqLNOM1Gyq64SsB gR9uVl/d6e2hScMi5V/vA== X-UI-Out-Filterresults: notjunk:1;V01:K0:otYoMy5CRi0=:KaJzpbLtknLKYSFMPQn0TH SxuI405sh17H1nZSCySV4zyAE5AP7YirGRq+uRPBpBuUPFQOsr5ch0SQu75Y3dC264Sf4waGz FzD476IVIiAnLl4vLBclr/3Sx7cZ7LPppgV4WXPW5K52J8n7W8Na09a+kTjgJYMpXqhW7OMMM P39Ud4cqoT4fw7SgcHGigMQNhDFCkGC4SdjYqt+xmsfwewXRqkyM8Oh5S9Mbf7JGLiR5vXACC 2J1ZuPknJehSdbZIpTWXXs/xpWSJ7mOnPi7MYcjGd6UCZrr0cxbd8a39g54hZBD0eLCgM60HU +tqZdLd7RAfwfQ1rf1Sw1lTJy0bGEqvI+ZO51r8XSFHV7GVq2PutDacWjPC/uCXvOnOaUJxD+ L2MLjcx1kmSCKgs3JgTqLl3sQfYn1V2lF4B9NlC1sAA0Ffe+30y2d6UVpn78ObiI+EESFqinM cv1RZEAsBR/sStpHwpqzMKBAl1Fll7oCmov7QDi+4GkvOvjXPoJw1EHOFSswzW9yoS3hCrZCt ibIugcbhV3NaTtuQnar3NFCI0K2ithnGQ/gBx6juqlDhEFsoPOOOnXfKY1+rIl6NXNesAaGH5 /HV+Q0k8c7hd9QC4Mps/2VFJxVrw2cJkslIIBYXRz39mDQZgLv+D59iGDguVnUrWcm1dPTitt mt4qGLuLPNasm0wGoV+7hLnM/PuVp6QMsmfO6MrctBMepnxZ3dv/MskpfcO8MOxDBLMQ7GkCU ZjFOG3JFX6BPieuPo8lgx67VIkfqTxaYuLpn9LPWdVO9lFsshS62EaVqcJzNgNuLpi5PEutYD YnFX25HgwRoiAjN94/FTYmriNyyLg== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2017 05:50:20 -0000 --Sig_/g9wtycGJj/uhL3YM0Lp8p0t Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Am Sun, 16 Jul 2017 16:29:40 -0600 Ian Lepore schrieb: > On Sun, 2017-07-16 at 22:48 +0200, O. Hartmann wrote: > > For a small SoC based system, I use a highly customised static kernel > > and build the > > system via NanoBSD with no kernel modules. > >=20 > > Tyring to track down some network issues with recent CURRENT I > > figured out, that when > > using the ppp client to connect via modem to the ISP and there is no=A0 > >=20 > > options NETGRAPH_ETHER > > options NETGRAPH_PPPOE > >=20 > > in the kernel configuration, the resulting system fails to establish > > a ppp session. The > > man page states, that a netgraph node is established, but as hard as > > I look, I can not > > find any(!) information in the man pages what options are > > necessary/optional to provide > > the correct module statically. > >=20 > > The same is for many other NETGRAPH_XXX features. Starting from man > > page "man 4 > > netgraph", section "SEE ALSO", I started tweaking the kernel with > > NETGRAPH_XXX, i.e. > > ng_vlan -> NETGRAPH_VLAN until the compiler bails out with an error, > > for instance > > ng_car -> NETGRAPH_CAR. > >=20 > > I tried to find out what options cover which netgraph module but > > there is - right, > > nothing I can find on a direct route. > >=20 > > Since netgraph isn't so brand new (I guess ~ 2000 from the PDFs I > > found on the network), > > there must be some documentation other than "reading the source > > code". > >=20 > > Please give me some hints where to find the entry point for the > > appropriate documented > > options for netgraph modules. > >=20 > > Obviously, some ng_xxx modules are prerequisite for some services to > > work properly, as > > ppp - but I can't find any hints for "options NETGRAPH_ETHER" or > > "options NETGRAPH_PPPOE" > > in the manpages (looked at ppp, pppoed).=A0 > >=20 > > Thanks in advance, > > kind regards > >=20 > > Oliver > > =20 >=20 > I can't help with anything specific to netgraph or its [lack of] docs. >=20 > For the general question "How do I know what undocumented device or > option statement to put in my kernel config to get xxxxx" a good place > to start is /usr/src/sys/conf/NOTES. =A0It's supposed to contain all the > options and devices (except some machine/arch-specific stuff). =A0If you > don't find it in NOTES, try "grep -i xxxxx *" in that dir, you may find > the thing you're looking for in 'options' or 'files' and get some clues > that way. Yes, correct and I did this, too, but pulling in all of the options resulte= d in failues, as far as I know NETGRAPH_CAR bailed out (with -DNO_CLEAN, I must confess). >=20 > For the netgraph stuff, I see that in NOTES it tells you how to find > the manpages for netgraph things, so I guess I accidentally did answer > that part too. =A0:) No, not exactly, it doesn't tell me which NETGRAPH_XXX I need for a certain service so I hav= e to do experiments: starting the service with a full install of all modules and se= e what modules gets kloaded and then put the appropriate option into the kernel. In my situation, using ppp/pppoe failed silently when disabling options NET= GRAPH_ETHER, NETGRAPH_PPPOE and the refering kernel modules weren't present. Since I fight a problem with VLANs and routing on CURRENT, I'd appreciate a= more dense documentation - or a hint. >=20 > -- Ian Thank you very much for the patience, kind regards Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =DCbermittlung meiner Daten f=FCr Werbezwecke oder f=FCr die Markt- oder Meinungsforschung (=A7 28 Abs. 4 BDS= G). --Sig_/g9wtycGJj/uhL3YM0Lp8p0t Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWxQCgAKCRDS528fyFhY lIrGAf9uiuC7MoSuTZxE/sUw76Nr0z7ToKcoA6RnTnQPnyM51xoT/OSVeZwMc93n 34ELoPZmxxLBe7eQ3coI9TXBmWOxAgCWJL2YlUB9G/rqsGw92xCsNC+anYe6TTUv VRUimsNGZ3rzDOntqsh7YeMUjubDXtkANHCZdpDZxp2PI+R2Dzc6 =l5cI -----END PGP SIGNATURE----- --Sig_/g9wtycGJj/uhL3YM0Lp8p0t--