[HOWTO] Install TheBrig - one Jail manager for N4F

Parkcomm · Post by **Parkcomm** » 15 Jul 2015 03:48

By the way Alexy - I think I have tested every feature I can now, except updating a new release of FreeBSD, altering the rudimentary config and using a foreign language.

So everything works as expected, and I'm really impressed with this version of thebrig.

There is one other niggle, Jail start and stop buttons are a little flakey, I have not been able to put my finger on the issues, but I use the command line to deleted "/var/run/Jail_" files and "/etc/rc.d/thebrig onestart" quite often. If I work out what causes it to fail I'll let you know.

But otherwise, as I said, top notch.

Post by **alexey123** » 15 Jul 2015 10:50

Sorry, I no have free time for TheBrig development few days..
I'll continue at 19 July

Parkcomm · Post by **Parkcomm** » 16 Jul 2015 04:16

I'll keep an eye out

Post by **MikeMac** » 16 Jul 2015 20:38

alexey123 wrote:TODO:
fstab entries: - With new JQwery I cannot give to work fstab edItor. May be remove it?

I vote for fstab edItor removal

tonyd · Post by **tonyd** » 17 Jul 2015 09:09

Hi. I tried going through the thread but couldn't find anything about this.

I installed the latest release 10.1.0.2.1731 and things went pretty smoothly for everything but TheBrig.

I knew I had an older version, so I upgraded it (coming from last 9.2 build). The install was successful. However, when I refresh and go to TheBrig tab in the GUI I see:

Code: Select all

Warning: require_once(XML/Serializer.php): failed to open stream: No such file or directory in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10 Fatal error: require_once(): Failed opening required 'XML/Serializer.php' (include_path='.:/etc/inc:/usr/local/www') in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10

Did I jump the gun and this is not ready for 10.1 yet?

The funny thing is my two jails are running fine. I just can't control them from the GUI.

Thanks for any help.

Parkcomm · Post by **Parkcomm** » 19 Jul 2015 09:31

Did you make sure you disabled the extended GUI?

HeinzHeinze · Post by **HeinzHeinze** » 19 Jul 2015 18:47

tonyd wrote:The install was successful. However, when I refresh and go to TheBrig tab in the GUI I see:
Code: Select all
Warning: require_once(XML/Serializer.php): failed to open stream: No such file or directory in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10 Fatal error: require_once(): Failed opening required 'XML/Serializer.php' (include_path='.:/etc/inc:/usr/local/www') in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10
Did I jump the gun and this is not ready for 10.1 yet?

Hallo.

I have the very same problem as tonyd.
I am new to nas4free, so i did a totally fresh install of 10.1. The setup went fine. I haven't installed any extended GUI so far. Only nas4free on embedded install and a 3 HDD raidz pool are running yet. When i follow instructions for the installation for thebrig everything runs smooth, no error. I see the new dropdown appearing in the GUI and it contains: TheBrig.
But when I click on it I get the exact text tonyd already posted.

Is there a solutin to this or do we have to wait until thebrig gets adapted to 10.1?

Thanks

Post by **raulfg3** » 19 Jul 2015 20:06

you need to install alcatraz and NO install theBrig in 10.x

HeinzHeinze · Post by **HeinzHeinze** » 19 Jul 2015 21:30

raulfg3 wrote:you need to install alcatraz and NO install theBrig in 10.x

Thank you for the Info. That did the Trick.

For any other newbie having problems, I found this on the forum for installation of thebrig alcatraz branch.

Code: Select all

fetch https://raw.githubusercontent.com/fsbruva/thebrig/alcatraz/thebrig_install.sh
chmod a+x thebrig_install.sh
sh thebrig_install.sh /mnt/yourpool/yourjailfolder 3

Worked fine for me.

Post by **alexey123** » 19 Jul 2015 23:03

Hi all
Message Warning: require_once(XML/Serializer.php): failed to open stream: No such file or directory in says about you try use old version ( for 9,1 or 9,2 based Nas4Free ) of TheBrig
Nas4Free developers remove serializer subrotines from NAS4Free php scripts - we also rewrited our pages . Commit for reference

Also I find next for vnet enabled jails.
I must use only one bridge for correct work and add epair interfaces for it.

Repared https://github.com/fsbruva/thebrig/comm ... 338fdcb98c
please check for multiple vnet enabled jails

tonyd · Post by **tonyd** » 20 Jul 2015 04:07

Thanks for pointing to the 10.1 install. That did it!

Parkcomm · Post by **Parkcomm** » 20 Jul 2015 05:04

VNET still problematic

Side A - 10.1.0.23/24
Side B - 192.168.5.23/24

host ifconfig:

Code: Select all

epair5a: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 02:ff:00:00:06:0a
	inet6 fe80::ff:ff:fe00:60a%epair5a prefixlen 64 scopeid 0x6 
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
	status: active
epair5b: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8<VLAN_MTU>
	ether 02:ff:50:00:09:0b
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
	status: active

start command

Code: Select all

 mightymouse: ~# /etc/rc.d/thebrig onestart Black
Starting jails: security.jail.enforce_statfs: 0 -> 0
Black ifconfig: SIOCIFCREATE2: File exists
ifconfig: interface bridge20 does not exist
jail: Black: /bin/sh /mnt/MightyMouse/DATA/thebrig/conf/jails/prestart.Black: failed

In the host It looks like you added epairb instead of the bridge.

Parkcomm · Post by **Parkcomm** » 20 Jul 2015 06:36

I've also noticed that the fstab is no longer relative to the root of the jail and now requires an absolute path for the mount point

Post by **alexey123** » 20 Jul 2015 16:12

Parkcomm wrote:VNET still problematic

Side A - 10.1.0.23/24
Side B - 192.168.5.23/24

I'll check. But define epair interface from different subnets - is normal? For me work on some subnet only.

Parkcomm wrote:I've also noticed that the fstab is no longer relative to the root of the jail and now requires an absolute path for the mount point

As I remember, all TheBrig version was need full path to fstab.
Dut you give me good idea - I can define mountpoint as relative path
UPD.
I replace default route mechanizm for single briddge - https://github.com/fsbruva/thebrig/comm ... 5dfda9c41e

Now results ifconfig:

Code: Select all

nasbox: ~# ifconfig
msk0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c0018<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWTSO,LINKSTATE>
        ether dc:9c:52:07:a5:51
        inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
        inet6 fe80::de9c:52ff:fe07:a551%msk0 prefixlen 64 scopeid 0x1
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex,flowcontrol,rxpause,txpause>)
        status: active
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 0x2
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
urtwn0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290
        ether 80:1f:02:64:dc:b8
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier
wlan0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 80:1f:02:64:dc:b8
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
        status: no carrier
        ssid "" channel 1 (2412 MHz 11b)
        country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60
        bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1
        bintval 0
bridge20: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 02:fe:4a:c8:9c:14
        inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255
        nd6 options=1<PERFORMNUD>
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: epair4a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 7 priority 128 path cost 2000
        member: epair3a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 6 priority 128 path cost 2000
        member: msk0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 1 priority 128 path cost 20000
epair3a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:ff:00:00:06:0a
        inet6 fe80::ff:ff:fe00:60a%epair3a prefixlen 64 scopeid 0x6
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
epair4a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:ff:00:00:07:0a
        inet6 fe80::ff:ff:fe00:70a%epair4a prefixlen 64 scopeid 0x7
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active

Jails:

For all user: - TheBrig can be updated to fresh version over webgui Updates --> Extensions|TheBrig|Manager over one click

TODO today
fstab part

Parkcomm · Post by **Parkcomm** » 21 Jul 2015 06:52

Alexy

I'll check. But define epair interface from different subnets - is normal? For me work on some subnet only.

the epair is basically a point to point pseudo wire and epaira takes no part in the routing other than connecting to the bridge. So as long epaira has an address what the address is, is largely irrelevant. So in the past I've deliberately chosen addresses outside of my subnet to avoid addressing conflicts.

I don't know if its best practice, whether it would be supported in the future etc., but it definitely works.

I've had a play with the current version of the brig and VNET now works very well

Please have a look a at the following:

Code: Select all

 mightymouse: ~# /etc/rc.d/thebrig onestart Black
Starting jails: security.jail.enforce_statfs: 0 -> 0
Black epair4a
Black: created
route: writing to routing socket: Network is unreachable
add net default: gateway 10.1.0.2 fib 0: Network is unreachable
ps: empty file: Invalid argument
/etc/rc: WARNING: $hostname is not set -- see rc.conf(5).
Starting Network: lo0.
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 0x1 
	inet 127.0.0.1 netmask 0xff000000 
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
ps: /boot/kernel/kernel: No such file or directory
add net fe80::: gateway ::1 fib 0,1,2,3,4,5
add net ff02::: gateway ::1 fib 0,1,2,3,4,5
add net ::ffff:0.0.0.0: gateway ::1 fib 0,1,2,3,4,5
add net ::0.0.0.0: gateway ::1 fib 0,1,2,3,4,5
Generating host.conf.
Creating and/or trimming log files.
Starting syslogd.
ELF ldconfig path: /lib /usr/lib /usr/lib/compat
32-bit compatibility ldconfig path: /usr/lib32
Clearing /tmp (X related).
Updating motd:.
Starting cron.
ps: empty file: Invalid argument

Note that:
- add default gateway uses the host bridge address as the destination. I believe that the actual destination should usually be router, that is the default route associated with the host interface.
- ps: empty file: Invalid argument - I'm not sure what is causing this
- WARNING: $hostname is not set. A good default would be to set the hostname to the name of the jail

I also created a VNET on subnet 5 and on interface bge0 -which bridged to bge0 - as expected.
I then created a VNET on subnet 1 and on interface em0 - this also bridge to bge0 and not to em0.

I think the expected behaviour would be to have a one bridge associated with each physical interface and that these do not bridge together. This is something I will probably not test too much unless you ask me to. My lab is set up with host on em0 and all my jails on bge0, so i would not observe this in normal use.

Post by **alexey123** » 21 Jul 2015 08:32

Parkcomm wrote:
Code: Select all
 mightymouse: ~# /etc/rc.d/thebrig onestart Black
 

If you check Allow start all jails checkbox on Globals section, you can type start instead oneatart

Note that:
- add default gateway uses the host bridge address as the destination. I believe that the actual destination should usually be router, that is the default route associated with the host interface.

I 'm read this article as reference for make jail's scripts
TheBrig create sScripts and fstabs into conf/jails folder, you can inspect its.

- ps: empty file: Invalid argument - I'm not sure what is causing this

Try check Enable mount procfs on TheBrig|Jail|Edit page

- WARNING: $hostname is not set. A good default would be to set the hostname to the name of the jail

You can define hostname over jail's /etc/rc.conf.
Or you want make entry automatically ?

I also created a VNET on subnet 5 and on interface bge0 -which bridged to bge0 - as expected.
I then created a VNET on subnet 1 and on interface em0 - this also bridge to bge0 and not to em0.

I think the expected behaviour would be to have a one bridge associated with each physical interface and that these do not bridge together. This is something I will probably not test too much unless you ask me to. My lab is set up with host on em0 and all my jails on bge0, so i would not observe this in normal use.

I'll check multi-lan config today. I just need built new test machine

Parkcomm · Post by **Parkcomm** » 21 Jul 2015 09:28

If you check Allow start all jails checkbox ...

Thanks, that works

I 'm read this article as reference for make jail's scripts

Cool, that will help with testing.

Both methods will work. I think of it this way: the eparis are physical wires and the bridge is a physical bridge. Would I configure the jail to terminate on the ip.addr of the bridge? The answer is i couldn't do that if i wanted to.

Does it matter? I don't know, perhaps there others on this thread who know better than I do and can jump in.

I can confirm that I have now tested it using ip addresses within the subnet and it does work.

Try check Enable mount procfs ...

That's what I've done with my operating jails. this explains why I only noticed this on the latest test jails.

Or you want make entry automatically ? ...

Personally I am happy to edit rc.conf. It might be handy for newbies but on second thought, jailname and hostname will often be different.

Parkcomm · Post by **Parkcomm** » 21 Jul 2015 11:56

Just rebooted (I never reboot!) and the jails all came up - however the one jail I had configured to use central ports forgot (that it was configured to use central ports)

Also just let theBrig do its thing with routes - everything default routes back to the bridge. Jails configured to boot all came up and worked, but the be bridge address seemed to disappear. I manually configured and started the other jail and they worked too - I'm not sure what happened because I would expect that if the default router is the bridge address and the bridge address disappears, the jails should fail to route.

Maybe I just got confused for a minute, I'm not sure.

Parkcomm · Post by **Parkcomm** » 22 Jul 2015 00:53

Can confirm Update / FreeBSD Update / Jails works as expected for single and multiple jails

I have also noticed that you have the option to use a template as a jail source - do you want me to test this?

erico.bettoni · Post by **erico.bettoni** » 22 Jul 2015 12:22

Is the TheBrig Manager update feature working?
I'm using v0.9 and it says it's the latest version, but I've read in another thread that there is a v0.91.

Post by **alexey123** » 22 Jul 2015 12:48

You can one-click Update it over web page Extensions|TheBrig|Manager

erico.bettoni · Post by **erico.bettoni** » 22 Jul 2015 13:15

alexey123 wrote:You can one-click Update it over web page Extensions|TheBrig|Manager

Yeah, I always do that. I just saw it updated to v0.91 even as it said there was no new version. I was on v0.9.

Parkcomm · Post by **Parkcomm** » 25 Jul 2015 17:33

Hey Alexy -

I think I can explain in a nutshell what the problem is with the example in the link you posted.

I want to send the traffic from the bge0 interface, but my host interface is em0.

If the default route for the route terminates on bridge ip address or the epaira interface,traffic is forwarded using the host routing table and therefore em0 for default route.

However Jail IP <- epair psuedowire - bridge - bge0 -> router works using L1/L2. So using the IP address of the router as default route within the jail works fine. It also means that ip addresses for the bridge and for the epaira interfaces are unnecessary.

btw - I realise not everyone has the same requirements as I do, and I can get this to work relatively easily with a couple of manual tweaks. So if you want to stick with your current approach that's OK with me.

Parkcomm · Post by **Parkcomm** » 27 Jul 2015 22:51

Actually ignore my last sentence - if you want to put jails in your DMZ that can be achieved using the methodology I use - it cannot be done with the method the tutorial suggests because of the problem I describe.

(well it can, but you'd have to fool around with multiple FIBs)

HeinzHeinze · Post by **HeinzHeinze** » 29 Jul 2015 19:13

tonyd wrote:Thanks for pointing to the 10.1 install. That did it!

Hi every one.

Other than my first idea, I decided to install this version instead of the alcatraz branch, as alcatraz is warning on installation to be a developer edition. I'm on NAS4free 10.1. and a newbie so please be forgiving.

I read people can update easily via the GUI. And that it is vital to get the right version of thebrig, if on 10.1, in case of a fresh install, which seem to be no problem for some people.

But I still don't know how to get the right version. Following the instructions of the initial post of this thread and using the install skript I still seem to get the wrong version of thebrig.
I also could not find a link or anything for the newest zip-file on github, which the install skript tries to fetch. From a look at the install skript I got the idea of using different options for the "working", "alexey" and "master" zip. But non worked right and I always got the same error in the NAs4free GUI when klicking on TheBrig.

Code: Select all

Warning: require_once(XML/Serializer.php): failed to open stream: No such file or directory in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10 Fatal error: require_once(): Failed opening required 'XML/Serializer.php' (include_path='.:/etc/inc:/usr/local/www') in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10

If someone could please give new instructions or update the install skript? Would be very kind.

Thanks so far

HeinzHeinze · Post by **HeinzHeinze** » 30 Jul 2015 16:08

Meanwhile I reinstalled the alcatraz branch. The installation worked. But I can't get the jail running (no jail ID and so on...):

Also I got the issue for the start stop button, which alexey123 already gave a solution for in an other thread:

If you cannot press Stop button, so jail was wrote his id file, but not started.
For remove id file manually find it into /var/run folder -----> /var/run/jail_<jailname>.id and delete it

I also added the necessery "in jail allow" he posted there.

This could stop the malfunctioning jail, but the start/stop button keeps stuck. Did this several times now and also reinstalled alcatraz several times.

When I first installed alcatraz 2 weeks ago (before my vacation

) I could solve the issue with the button this way and also the jail was running right.

Did i accidentaly fetch a work in progress version or something? Do I just have to wait?

This is a lot of writing now, sorry.
But help would be very nice, cause would like to have something funktional up and running in a few days.

regards

Post by **MikeMac** » 30 Jul 2015 19:15

HeinzHeinze wrote: issue for the start stop button

I had seen the same problem in a few cases
- jails numbers are not in 1,2,3... order. Ie 2,3,4 or 1, 3, 4 both are problematic in alcatraz (but not in previous version). alexey123 is going to fix. Temporary workaround - use xml editor to edit jails numbers in nas4free config

- something goes wrong with fstab mounts. Previous Brig version starts jail in this situation, new one - not

- also at a few cases there is a need to add hostname into jail's rc.conf

I had described this (and more) in my RUSSIAN blog, see http://2gusia.livejournal.com/302626.html with google translator. Screenshots are from English interface

M*I*B · Post by **M*I*B** » 31 Jul 2015 22:57

... maybe don't work unter 10.1.0.2 ?!?

Just try to install and that works fine. Also the new menuitem "Erweiterungen" (extensions) are up. But if I go there and click "TheBrig" I got...

Code: Select all

Warning: require_once(XML/Serializer.php): failed to open stream: No such file or directory in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10 Fatal error: require_once(): Failed opening required 'XML/Serializer.php' (include_path='.:/etc/inc:/usr/local/www') in /usr/local/www/ext/thebrig/extensions_thebrig.php on line 10

So I have take a look into /usr/local/www/ext/thebrig there is'nt a folder like XML/ or anything like that and I also can't find a file named Serializer.php on the whole system...

Doing any wrong?

thiagomespb · Post by **thiagomespb** » 06 Aug 2015 02:15

Code: Select all

 nas4free: jail# fetch https://raw.githubusercontent.com/fsbruva/thebrig/alcatraz/thebrig_install.sh
thebrig_install.sh                            100% of 7761  B   48 MBps 00m00s
nas4free: jail# chmod a+x thebrig_install.sh
nas4free: jail# bin/sh thebrig_install.sh /volume2/ volume3/
 
nas4free: jail# /bin/sh thebrig_install.sh /volume3/jail 3
Retrieving the unstable branch as a zip file
If you aren't a developer for TheBrig, is a bad idea!
Please re-install according to the documentation...
alcatraz.zip                                  100% of  143 kB  213 kBps 00m00s
Unpacking the tarball...
Done!
Detecting current configuration...

Looks like we're re-installing!
Upgrading/Re-installing...

Warning: preg_grep() expects parameter 2 to be array, null given in /volume3/jail/conf/ext/thebrig/functions.i                                                          nc on line 963

Warning: preg_grep() expects parameter 2 to be array, null given in /volume3/jail/conf/ext/thebrig/functions.i                                                          nc on line 971

Warning: preg_grep() expects parameter 2 to be array, null given in /volume3/jail/conf/ext/thebrig/functions.i                                                          nc on line 994

Warning: Invalid argument supplied for foreach() in /volume3/jail/conf/ext/thebrig/functions.inc on line 995

Warning: preg_grep() expects parameter 2 to be array, null given in /volume3/jail/conf/ext/thebrig/functions.i                                                          nc on line 1000

Warning: Invalid argument supplied for foreach() in /volume3/jail/conf/ext/thebrig/functions.inc on line 1001

Warning: preg_grep() expects parameter 2 to be array, null given in /volume3/jail/conf/ext/thebrig/functions.i                                                          nc on line 1051

Warning: Invalid argument supplied for foreach() in /volume3/jail/conf/ext/thebrig/functions.inc on line 1052
Congratulations! TheBrig was re-installed.

Code: Select all

FreeBSD nas4free.actios.local 10.1-RELEASE-p14 FreeBSD 10.1-RELEASE-p14 #0 r285365M: Sat Jul 11 05:08:33 CEST 2015     root@dev.nas4free.org:/usr/obj/nas4free/usr/src/sys/NAS4FREE-amd64  amd64

10.1.0.2 - Prescience (revision 1731)

M*I*B · Post by **M*I*B** » 06 Aug 2015 10:13

... ty ... I will check that out soon ...
Have I to uninstall / delete the former wrong installation or just leave it while it will be overwritten?

XigmaNAS

[HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F

Re: [HOWTO] Install TheBrig - one Jail manager for N4F