On May 20, 2013, at 4:28 PM, Joe wrote:
[…]
> Without netgraph compiled into the kernel, issuing "ngctl list" command on
> the host only shows the socket for ngctl.
>
> After I issue the kldload command on the host for netgraph ng_bridge
> ng_eiface ng_ether ng_so
Teske
Here is my results
Without netgraph compiled into the kernel, issuing "ngctl list" command
on the host only shows the socket for ngctl.
After I issue the kldload command on the host for netgraph ng_bridge
ng_eiface ng_ether ng_socket, then issuing "ngctl list" co
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_eth
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?
___
freebsd-questions@freebsd.org mailing list
http://lists.f
On Wed, 23 Dec 2009 13:26:57 +0300
Yuri Pankov wrote:
> On Wed, Dec 23, 2009 at 05:18:28PM +0700, Anh Ky Huynh wrote:
> > Hi all,
> >
> > I have a VirtualBox guest which is running FreeBSD-8.0. I
> > compiled the kernel for this guest with the options NETGRAPH
> > in /usr/src/sys/i386/conf/GENER
On Wed, Dec 23, 2009 at 05:18:28PM +0700, Anh Ky Huynh wrote:
> Hi all,
>
> I have a VirtualBox guest which is running FreeBSD-8.0. I compiled the kernel
> for this guest with the options NETGRAPH in /usr/src/sys/i386/conf/GENERIC. I
> did that because I expected I would see each Ethernet interf
real FreeBSD host
$ ngctl list
There are 5 total nodes:
Name: re0 Type: ether ID: 0001 Num hooks: 2
Name: ngctl15142 Type: socket ID: 0006 Num hooks: 0
Name: vboxnetflt_re0 Type: vboxnetflt ID: 0004 Num hooks: 2
Name: vboxnet0
