Date: Mon, 20 May 2013 19:28:26 -0400 From: Joe <fbsd8@a1poweruser.com> To: Devin Teske <dteske@freebsd.org> Cc: freebsd-questions@Freebsd.org Subject: Re: ngctl list ? Message-ID: <519AB19A.50100@a1poweruser.com> In-Reply-To: <13CA24D6AB415D428143D44749F57D7201F51DFF@ltcfiswmsgmb26> References: <51993A7A.8070302@a1poweruser.com> <13CA24D6AB415D428143D44749F57D7201F51DFF@ltcfiswmsgmb26>
next in thread | previous in thread | raw e-mail | index | archive | help
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" command now
shows the real NIC interface device names.
Thanks for you insight.
I have another problem.
To standardize my bridge and eiface names I want to use the JID number
as a suffix.
jid=`jls -j ${jailname} jid`
bridge_name="bridge${jid}
When creating the bridge it gets assigned bridge_name just like I want.
I want to assign the ${jid} to the ieface peer name and can not figure
out the syntax. This is the command I am using now
ngctl mkpeer eiface ether ether
This creates a default name of ngeth0
I would be ok with ngeth${jid}
But would really like to assign my own peer name vetjail${jid}
Does the mkpeer syntax allow doing this?
Thanks
Joe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?519AB19A.50100>