From owner-freebsd-questions@FreeBSD.ORG Mon May 20 02:29:47 2013 Return-Path: Delivered-To: freebsd-questions@Freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 42E733D1 for ; Mon, 20 May 2013 02:29:47 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) by mx1.freebsd.org (Postfix) with ESMTP id 13D4435D for ; Mon, 20 May 2013 02:29:46 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.31]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id r4K2Tbw7020535 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 19 May 2013 21:29:37 -0500 Received: from LTCFISWMSGMB26.FNFIS.com ([10.132.99.18]) by LTCFISWMSGHT03.FNFIS.com ([10.132.206.31]) with mapi id 14.02.0309.002; Sun, 19 May 2013 21:29:37 -0500 From: "Teske, Devin" To: Joe Subject: Re: ngctl list ? Thread-Topic: ngctl list ? Thread-Index: AQHOVNIwXFfQJGFeN0CDQ+tJB0izZpkNreoA Date: Mon, 20 May 2013 02:29:36 +0000 Message-ID: <13CA24D6AB415D428143D44749F57D7201F51DFF@ltcfiswmsgmb26> References: <51993A7A.8070302@a1poweruser.com> In-Reply-To: <51993A7A.8070302@a1poweruser.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.126] MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-05-19_07:2013-05-17,2013-05-19,1970-01-01 signatures=0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 02:29:47 -0000 On May 19, 2013, at 1:47 PM, Joe wrote: When I issue "ngctl list" command on the host it only shows the socket for = ngctl. I thought it would also show the real NIC interface device names. Am I wrong in thinking that? No, you're not wrong, however one wrinkle is that ng_ether(4) has to be com= piled-in to get the netgraph subsystem to attach to your real NIC interface= s. On the system where you're executing "ngctl list" (same thing as "ngctl ls"= ), can you execute: config -x `sysctl -n kern.bootfile` | grep NETGRAPH_ETHER and get back something like the following (which I get back from my system): options NETGRAPH_ETHER # ng_ether(4) (and on that system, I get the following for "ngctl ls") root@folsom.vicor.com ~ # ngctl ls There are 16 total nodes: Name: em0 Type: ether ID: 00000003 Num hooks: 0 Name: em1 Type: ether ID: 00000004 Num hooks: 0 Name: em2 Type: ether ID: 00000005 Num hooks: 0 Name: ng0_beefcake Type: eiface ID: 00000018 Num hooks: 1 Name: ng0_stats Type: eiface ID: 0000000f Num hooks: 1 Name: ngctl21992 Type: socket ID: 0000005f Num hooks: 0 Name: ng0_cfg0_vlbxri Type: eiface ID: 00000024 Num hooks: 1 Name: igb0bridge Type: bridge ID: 00000008 Num hooks: 4 Name: ng0_ipu0a_vlbxr Type: eiface ID: 00000037 Num hooks: 1 Name: ng0_ipm0_vlbxri Type: eiface ID: 0000002d Num hooks: 1 Name: igb1bridge Type: bridge ID: 0000001d Num hooks: 8 Name: ng0_oos0a_vlbxr Type: eiface ID: 00000042 Num hooks: 1 Name: ng0_opm0_vlbxri Type: eiface ID: 0000004e Num hooks: 1 Name: ng0_wss0a_vlbxr Type: eiface ID: 0000005b Num hooks: 1 Name: igb0 Type: ether ID: 00000001 Num hooks: 2 Name: igb1 Type: ether ID: 00000002 Num hooks: 2 NOTE: Alternatively=85 if you don't get a response back from config(8) simi= lar to the above,=85 does "kldstat" show an "ng_ether" entry? I think last = time I tried to load ng_ether(4) as a module (versus compiled-in), it didn'= t list any of my ether devices ("Type: ether" in above "ngctl ls" output). -- Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.