Latest News:
2019-03-31: XigmaNAS 11.2.0.4.6625 - released!

Latest BETA Release:
2019-03-31: XigmaNAS 12.0.0.4.6625 - BETA released!

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS cost money, please consider a donation to our project so we can continue to offer you the best.
We need your support! eg: PAYPAL

Specify a MAC address for the Jail. Is there a way?

Jails with XigmaNAS
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
supercazzola
Starter
Starter
Posts: 27
Joined: 30 Dec 2012 05:54
Status: Offline

Specify a MAC address for the Jail. Is there a way?

#1

Post by supercazzola » 26 Mar 2018 00:30

I saw a post a few years ago where someone asked if it was possible to assign a virtual MAC address to the network interface of the Jail. I am really in a pickle here, and need to do just that.

Is there a way?

The problem is my network is now a Google WiFi mesh network, and they do not allow port forwarding to a machine unless it is on the network, so I can not add an entry for the jail (the Plex port TCP forwarding 32400).

It sees the MAC address of the host NAS4Free, and refuses to acknowledge the presence of the Jail in its tables for detected devices.

I know some folks will tell me to get rid of the router, but I really need to be able to specify a different Mac for this machine. Can anyone recommend a solution?

Thank you

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4797
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#2

Post by raulfg3 » 26 Mar 2018 08:07

12.0.0.4 - BETA (revision 6625)+OBI on SUPERMICRO X8SIL-F 8GB of ECC RAM, 12x3TB disk in 3 vdev in RaidZ1 = 32TB Raw size only 22TB usable

Wiki
Last changes
Old Wiki

supercazzola
Starter
Starter
Posts: 27
Joined: 30 Dec 2012 05:54
Status: Offline

Specify a MAC address for the Jail. Is there a way?

#3

Post by supercazzola » 26 Mar 2018 10:04

The last link is the one I mentioned, when I posted. It didn’t help as they basically asked what router he had and told him to get rid of it.

I’ll gave the others a read, but almost all were for changing the MAC for the main NAS4Free, and that won’t help. I need one for the host and one for the jail, same network card.

Which leads me to ask, could I install a second network card, and have only the jail use that ?


Sent from my iPad using Tapatalk Pro

User avatar
ms49434
Developer
Developer
Posts: 562
Joined: 03 Sep 2015 18:49
Location: Neuenkirchen-Vörden, Germany - GMT+1
Contact:
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#4

Post by ms49434 » 26 Mar 2018 13:13

Did you look into a virtual lan solution like netgraph's ngctl / ng_bridge / ng_eiface?
In the below thread a MAC prefix is defined for virtual lan's:
https://lists.freebsd.org/pipermail/fre ... 51113.html

Code: Select all

Hello list

I cant get to the internet using this netgraph setup script.
I sure would appreciate giving this console log a look over for
errors. My netgraph knowledge level is not sufficient to see what is
wrong. The goal is to run this script to setup and break down a netgraph
network for a single vnet jail at a time. rl0 is the real nic interface
device name of the nic facing the internet. This box is on my lan and
the gateway box does NAT for all lan boxes. The host running this script 
can ping the internet ok.

Thank you very much for your help.





The host's kernel has modules with vimage & ipfw compiled in.

 From the host
# /root >ifconfig
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
	options=2008<VLAN_MTU,WOL_MAGIC>
	ether 00:0c:6e:09:8b:74
	inet 10.0.10.5 netmask 0xfffffff8 broadcast 10.0.10.7
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
ipfw0: flags=8801<UP,SIMPLEX,MULTICAST> metric 0 mtu 65536
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
	inet 127.0.0.1 netmask 0xff000000
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

The jails config file
# /root >cat /usr/local/etc/vnet/vdir4
vdir4 {
host.hostname       =  "vdir4";
path                =  "/usr/jails/vdir4";
mount.fstab         =  "/usr/local/etc/fstab/vdir4";
vnet;
persist;
}

The netgraph script
# /root >cat /usr/local/bin/vnet.ng.test
#!/bin/sh
# snip comments for displaying here
# This script is based on this /usr/share/examples/netgraph/virtual.lan

# Give the name of ethernet interface.
ETHER_INTF="rl0"

# List the names of virtual nodes and their IP addresses. Use ':'
# character to separate node name from node IP address and netmask.

#TARGET_TOPOLOGY="c1|10.0.2.20/24 c2|10.0.2.21/24 c3|10.0.2.22/24"
TARGET_TOPOLOGY="vdir4|10.0.2.20/24"

# MAC manufacturer prefix. This can be modified according to needs.
MAC_PREFIX="00:1d:92"

# Temporary file is important for proper execution of script.
TEMP_FILE="/var/tmp/virtual.lan.tmp"

virtual_lan_start() {

# Load netgraph KLD's as necessary.

for KLD in ng_ether ng_bridge ng_eiface; do
	if ! kldstat -v | grep -qw ${KLD}; then
		echo -n "Loading ${KLD}.ko... "
		kldload ${KLD} || exit 1
		echo "done"
	fi
done

# Reset all interfaces and jails. If temporary file can not be found
# script assumes that there is no previous configuration.

if [ ! -e ${TEMP_FILE} ]; then
   echo "No previous configuration(${TEMP_FILE}) found to clean-up."
else
   echo -n "Cleaning previous configuration..."
   virtual_lan_stop
   echo "done"
fi

# Create temporary file for usage. This file includes generated
# interface names and jail names. All bridges, interfaces and jails
# are written to file while created. In clean-up process written
# objects are cleaned (i.e. removed) from system.

if [ -e ${TEMP_FILE} ]; then
	touch ${TEMP_FILE}
fi

echo -n "Verifying ethernet interface existence..."
# Verify ethernet interface exist.
if ! ngctl info ${ETHER_INTF}: >/dev/null 2>&1; then
	echo "Error: interface ${ETHER_INTF} does not exist"
	exit 1
fi

ifconfig ${ETHER_INTF} up || exit 1
echo "done"

# Get current number of bridge interfaces in the system. This number
# is used to create a name for new bridge.
BRIDGE_COUNT=`ngctl l | grep bridge | wc -l | sed -e "s/ //g"`
BRIDGE_NAME="bridge${BRIDGE_COUNT}"

# Create new ng_bridge(4) node and attach it to the ethernet interface.
# Connect ng_ether:lower hook to bridge:link0 when creating bridge and
# connect ng_ether:upper hook to bridge:link1 after bridge name is set.

echo "Creating bridge interface: ${BRIDGE_NAME}..."
ngctl mkpeer ${ETHER_INTF}: bridge lower link0 || exit 1
ngctl name ${ETHER_INTF}:lower ${BRIDGE_NAME} || exit 1
ngctl connect ${ETHER_INTF}: ${BRIDGE_NAME}: upper link1 || exit 1
echo "Bridge ${BRIDGE_NAME} is created and ${ETHER_INTF} is connected."

# In the above code block two hooks are connected to bridge interface,
# therefore LINKNUM is set to 2 indicating total number of connected
# hooks on the bridge interface.
LINKNUM=2

# Write name of the bridge to temp file. Clean-up procedure will use
# this name to shutdown bridge interface.
echo "bridge ${BRIDGE_NAME}" > ${TEMP_FILE}


# Attach vnet jail.
for NODE in ${TARGET_TOPOLOGY}; do

   # Virtual nodes are defined in TARGET_TOPOLOGY variable. They
   # have the form of 'nodeName|IPaddr'. Below two lines split
   # node definition to get node name and node IP.

   NODE_NAME=`echo ${NODE} | awk -F"|" '{print $1}'`
   NODE_IP=`echo ${NODE} | awk -F"|" '{print $2}'`

   # Create virtual node (jail) with given name
   echo -n "Creating virtual node (jail) ${NODE_NAME}..."

   jail -f "/usr/local/etc/vnet/${NODE_NAME}" -c ${NODE_NAME}
   if [ $? -ne 0 ]; then
     echo "Error: /usr/sbin/jail failed to start jail ${NODE_NAME}."
     virtual_lan_stop
     exit 2
   fi
   echo "done"

   # Write name of the jail to temp file. Clean-up procedure will
   # use this name to remove jail.

   echo "node ${NODE_NAME}" >> ${TEMP_FILE}

   # Create a ng_eiface object for virtual node. ng_eiface
   # object has a hook that can be connected to one of bridge
   # links. After creating interface get its automatically
   # generated name for further usage.

   echo "Creating eiface interface for virtual node ${NODE_NAME}."
   ngctl mkpeer eiface ether ether
   EIFACE=`ngctl l | grep ngeth | tail -n 1| awk '{print $2}'`
   echo "Interface ${EIFACE} is created."

   # Write name of the interface to temp file. Clean-up procedure
   # will use this name to shutdown interface.

   echo "interface ${EIFACE}" >> ${TEMP_FILE}

   # Move virtual interface to virtual node. Note that Interface
   # name will not be changed at the end of this movement. Moved
   # interface can be seen at the output of ifconfig command in
   # jail: 'jexec jailname ifconfig'

   echo "Moving ${EIFACE} to ${NODE_NAME}"
   ifconfig ${EIFACE} vnet ${NODE_NAME}

   # Make lo0 interface localhost.
   jexec ${NODE_NAME} ifconfig lo0 localhost

   # Generate a random mac address for virtual interface. First
   # three octets can be changed by user. Last three octets are
   # generated randomly.
   M4=`od -An -N2 -i /dev/random | sed -e 's/ //g' | \
		awk '{ print $1 % 256 }'`
   M5=`od -An -N2 -i /dev/random | sed -e 's/ //g' | \
		awk '{ print $1 % 256 }'`
   M6=`od -An -N2 -i /dev/random | sed -e 's/ //g' | \
	awk '{ print $1 % 256 }'`

   MAC=`printf ${MAC_PREFIX}:%02x:%02x:%02x ${M4} ${M5} ${M6}`

   # Set the link address (mac address) of virtual interface in
   # virtual node to randomly generated MAC.
   echo "Setting MAC address of ${EIFACE} to '${MAC}'"
   jexec ${NODE_NAME} ifconfig ${EIFACE} link $MAC

   # Either IPv4 or IPv6 can be used in this script. Ifconfig
   # IP setting syntax differs slightly for two IP versions.
   # For version 4 'inet' keyword is used whereas for version 6
   # 'inet6' is used. Below line tries to decide which IP version
   # is given and sets IPVER to 'inet' or 'inet6'.

   IPVER=`echo ${NODE_IP} | awk -F"." '{ split($4,last,"/"); \
	if( NF==4 && $1>0 && $1<256 && $2<256 && $3<256 && \
	last[1]<256) print "inet"; else print "inet6"}'`

   # Set IP address of virtual interface in virtual node.
   echo "Setting IP address of ${EIFACE} to '${NODE_IP}'"
   jexec ${NODE_NAME} ifconfig ${EIFACE} ${IPVER} ${NODE_IP}

   # Connect virtual interface to bridge interface. Syntax is :
   # ngctl connect INTERFACE: BRIDGE: INTERFACE_HOOK EMPTY_LINK.
   # Interface has one hook named 'ether' and below line connects
   # ether hook to bridge's first unconnected link.

   echo -n "Connecting ${EIFACE}:ether to ${BRIDGE_NAME}:link${LINKNUM}..."

   ngctl connect ${EIFACE}: ${BRIDGE_NAME}: ether link${LINKNUM} \
	|| exit 1
   echo "done"

   # Now, bridge has one more connected link thus link count is
   # incremented.
   LINKNUM=`expr ${LINKNUM} + 1`
done
echo "Virtual LAN established successfully!"

}


# Stop routine.
virtual_lan_stop() {

if [ ! -e ${TEMP_FILE} ]; then
   echo "Nothing to stop! ${TEMP_FILE}: temp file not found"
else
   echo -n "Shutdown bridge interface.."
   OBJECTS=`cat ${TEMP_FILE} | grep bridge | awk '{print $2}'`
   for BRIDGE in ${OBJECTS}; do
     ngctl shutdown ${BRIDGE}: >/dev/null 2>&1
   done
   echo "done"

   echo -n "Shutdown all eiface interfaces..."
   OBJECTS=`cat ${TEMP_FILE} | grep interface | awk '{print $2}'`
   for INTERFACE in ${OBJECTS}; do
     ngctl shutdown ${INTERFACE}: >/dev/null 2>&1
   done
   echo "done"

   echo -n "Removing all jails..."
   OBJECTS=`cat ${TEMP_FILE} | grep node | awk '{print $2}'`
   for NODE in ${OBJECTS}; do
      jail -f "/usr/local/etc/vnet/${NODE}" -r ${NODE}
   done
   echo "done"

   echo "Removing tempfile ${TEMP_FILE}"
   rm ${TEMP_FILE}
fi
echo "Virtual LAN objects removed successfully!"

}


# Main entry point.

case $# in
	1)
		case $1 in
                         start)
                                 echo -n "Creating default target topology:"
				echo " ${TARGET_TOPOLOGY}"
                                 virtual_lan_start
                                 ;;
                         stop)

				if [ ! -e ${TEMP_FILE} ]; then
					echo -n "Noting to stop! ${TEMP_FILE}:"
					echo " temp file not found"
				else
					virtual_lan_stop
				fi
                                 ;;
                         help)
                                 virtual_lan_usage
				exit 1
                                 ;;
                         *)
                                 virtual_lan_usage
                                 exit 1

                 esac
		;;
	2)
	        case $1 in
			start)
                         	TARGET_TOPOLOGY=$2
                                 echo -n "Creating target topology:"
				echo "${TARGET_TOPOLOGY}"
                                 virtual_lan_start
                                 ;;
                         *)
                         	virtual_lan_usage
                                 exit 1
                 esac
		;;

	*)
                 virtual_lan_usage
                 exit 1
esac


# /root >vnet.ng.test start
Creating default target topology: vdir4|10.0.2.20/24
Loading ng_ether.ko... done
Loading ng_bridge.ko... done
Loading ng_eiface.ko... done
No previous configuration(/var/tmp/virtual.lan.tmp) found to clean-up.
Verifying ethernet interface existence...done
Creating bridge interface: bridge0...
Bridge bridge0 is created and rl0 is connected.
Creating virtual node (jail) vdir4...vdir4: created
done
Creating eiface interface for virtual node vdir4.
Interface ngeth0 is created.
Moving ngeth0 to vdir4
Setting MAC address of ngeth0 to '00:1d:92:df:92:8e'
Setting IP address of ngeth0 to '10.0.2.20/24'
Connecting ngeth0:ether to bridge0:link2...done
Virtual LAN established successfully!


# /root >ngctl ls -l
There are 5 total nodes:
   Name: rl0             Type: ether           ID: 00000001   Num hooks: 2
   Local hook      Peer name       Peer type    Peer ID         Peer
hook
   ----------      ---------       ---------    -------
---------
   upper           bridge0         bridge       00000006        link1

   lower           bridge0         bridge       00000006        link0

   Name: ipfw0           Type: ether           ID: 00000002   Num hooks: 0
   Name: bridge0         Type: bridge          ID: 00000006   Num hooks: 3
   Local hook      Peer name       Peer type    Peer ID         Peer
hook
   ----------      ---------       ---------    -------
---------
   link2           ngeth0          eiface       0000000a        ether

   link1           rl0             ether        00000001        upper

   link0           rl0             ether        00000001        lower

   Name: ngeth0          Type: eiface          ID: 0000000a   Num hooks: 1
   Local hook      Peer name       Peer type    Peer ID         Peer
hook
   ----------      ---------       ---------    -------
---------
   ether           bridge0         bridge       00000006        link2

   Name: ngctl1513       Type: socket          ID: 0000000d   Num hooks: 0


# /root >jexec vdir4 tcsh
vdir4 / >ping -c 1 8.8.178.135
PING 8.8.178.135 (8.8.178.135): 56 data bytes
ping: sendto: No route to host

--- 8.8.178.135 ping statistics ---
1 packets transmitted, 0 packets received, 100.0% packet loss
vdir4 / >exit
exit


# /root >vnet.ng.test stop
Shutdown bridge interface..done
Shutdown all eiface interfaces...done
Removing all jails...vdir4: removed
done
Removing tempfile /var/tmp/virtual.lan.tmp
Virtual LAN objects removed successfully!

# /root >jls
    JID  IP Address      Hostname                      Path

# /root >ngctl ls -l
There are 3 total nodes:
   Name: ngctl1540       Type: socket          ID: 00000010   Num hooks: 0
   Name: rl0             Type: ether           ID: 00000001   Num hooks: 0
   Name: ipfw0           Type: ether           ID: 00000002   Num hooks: 0
1) XigmaNAS 11.2.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7, 22GB out of 32GB ECC RAM, LSI 9300-8i IT mode in passthrough mode. Pool 1: 2x HGST 10TB, mirrored, SLOG: Samsung 850 Pro, L2ARC: Samsung 850 Pro, Pool 2: 1x Samsung 860 EVO 1TB , services: Samba AD, CIFS/SMB, ftp, ctld, rsync, syncthing, zfs snapshots.
2) XigmaNAS 11.2.0.4 amd64-embedded on a Dell T20 running in a VM on ESXi 6.7, 8GB out of 32GB ECC RAM, IBM M1215 crossflashed, IT mode, passthrough mode, 1x HGST 10TB , services: rsync.

supercazzola
Starter
Starter
Posts: 27
Joined: 30 Dec 2012 05:54
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#5

Post by supercazzola » 26 Mar 2018 13:20

I’ll take a look. But it seems like it is over my head. I was hoping that the Brigg would have a spot where it could specify the MAC address, or that it would be a simple text file to edit. I’ll spend more time on it after work this week. Thank you for your suggestions


Sent from my iPad using Tapatalk Pro

nas4me2
NewUser
NewUser
Posts: 9
Joined: 21 Mar 2017 07:47
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#6

Post by nas4me2 » 25 Jun 2018 18:37

Have done precisely this with thebrig:

Code: Select all

cat poststart.jail1:
...
/usr/sbin/jexec jail1 /sbin/ifconfig epair6b ether xx:xx:xx:xx:xx:xx up
Do this by adding it to the poststart command in the expanded jail config.

supercazzola
Starter
Starter
Posts: 27
Joined: 30 Dec 2012 05:54
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#7

Post by supercazzola » 26 Jun 2018 11:55

nas4me2 wrote:Have done precisely this with thebrig:

Code: Select all

cat poststart.jail1:
...
/usr/sbin/jexec jail1 /sbin/ifconfig epair6b ether xx:xx:xx:xx:xx:xx up
Do this by adding it to the poststart command in the expanded jail config.
I’ll try it this weekend. Thank you


Sent from my iPad using Tapatalk Pro

supercazzola
Starter
Starter
Posts: 27
Joined: 30 Dec 2012 05:54
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#8

Post by supercazzola » 27 Jun 2018 15:14

supercazzola wrote:
nas4me2 wrote:Have done precisely this with thebrig:

Code: Select all

cat poststart.jail1:
...
/usr/sbin/jexec jail1 /sbin/ifconfig epair6b ether xx:xx:xx:xx:xx:xx up
Do this by adding it to the poststart command in the expanded jail config.
I’ll try it this weekend. Thank you


Sent from my iPad using Tapatalk Pro
Image

Sadly, it says the epair6b doesn’t exist



Sent from my iPhone using Tapatalk Pro

nas4me2
NewUser
NewUser
Posts: 9
Joined: 21 Mar 2017 07:47
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#9

Post by nas4me2 » 17 Apr 2019 12:25

Wow - sorry I missed the response email to this.

In case anyone is wondering why it didn't work, I have many jails and the line I quoted is from jail #6, hence the epair6b in the command.

You need to modify that 6 to be whatever jail number is assigned for your system. It will (should?) be epair1b for a single jail system.

[Edited to add]
Also, I'm using full vnets - I'm not if it will work otherwise as I've never tried to do that.

supercazzola
Starter
Starter
Posts: 27
Joined: 30 Dec 2012 05:54
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#10

Post by supercazzola » 17 Apr 2019 13:05

I’ll give it a try again. Thank you

supercazzola
Starter
Starter
Posts: 27
Joined: 30 Dec 2012 05:54
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#11

Post by supercazzola » 21 Apr 2019 13:15

OK, so I tried to run it from a command line to see if it would take. this time I get the following error:

Code: Select all

192.168.1.223->/usr/sbin/jexec DVRjail2 /sbin/ifconfig epair1b ether 11:22:33:44:55:66 up
jexec: jail_attach(1): Operation not permitted
192.168.1.223->
I am assuming that is because the jail is running.
Could you help me understand more about where that command needs to go? I use the Brigg, so perhaps I am not familiar with the location of the file to add the command to.

cookiemonster
experienced User
experienced User
Posts: 106
Joined: 23 Mar 2014 02:58
Location: UK
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#12

Post by cookiemonster » 21 Apr 2019 18:53

I'm not sure this would work. I don't think the brig uses VNET by default although it has the option.

In my opinion this is one the trickiest areas to navigate on xigmanas because networking with jails can be a challenge since one needs to use workarounds, they were intended to have limited connectivity by default for security. Then you have all sorts of networking technologies to get your head around. Then jails in xigmanas IMHO I find don't get a lot of support. Further, thebrig is another potential layer of complexity.
I think that unless you're up for a nice training/learning challenge, then it'll frustrate you. I'll be happy to be proven wrong though.
So you're easiest route is to replace the router.
Xigmanas 11.2.0.4 x64-full-RootOnZFS on Supermicro X8DT3. zroot on mirrorred pair of CRUCIAL_CT64M225. Memory: 24GB ECC; Storage: (HBA) - LSI SAS 9211-4i with 3 SATA x 1 Tb in raidZ1, 1 x 3 Tb SAS drive as single stripe.

User avatar
JoseMR
Hardware & Software Guru
Hardware & Software Guru
Posts: 1003
Joined: 16 Apr 2014 04:15
Location: PR
Contact:
Status: Offline

Re: Specify a MAC address for the Jail. Is there a way?

#13

Post by JoseMR » 21 Apr 2019 23:29

cookiemonster wrote:
21 Apr 2019 18:53
I'm not sure this would work. I don't think the brig uses VNET by default although it has the option.

In my opinion this is one the trickiest areas to navigate on xigmanas because networking with jails can be a challenge since one needs to use workarounds, they were intended to have limited connectivity by default for security. Then you have all sorts of networking technologies to get your head around. Then jails in xigmanas IMHO I find don't get a lot of support. Further, thebrig is another potential layer of complexity.
I think that unless you're up for a nice training/learning challenge, then it'll frustrate you. I'll be happy to be proven wrong though.
So you're easiest route is to replace the router.

+1

I encourage the use of iocage due its active development as well as for its usage simplicity, it is so simple that managing jails with iocage, a management GUI page is almost unnecessary but could be an extra.

However, the iocage notorious requirement is Python3 and ZFS which is indeed a very good thing IMO.

Also note that the system command setfib can be quite handy, and indeed required wen dealing with jails and multiple NIC's/Routing setups for ease.

I'm looking forward to develop an iocage extension based on requests, though RootOnZFS users can directly install py36-iocage into a new Boot Environment and start creating/managing jails after the setfib file copy workaround.

Regards
System: FreeBSD 12, MB: Supermicro X8SI6-F, Xeon X3450, 16GB DDR3 ECC RDIMMs.
Addons at GitHub
JoseMRPubServ

Post Reply

Return to “Jails”