Access to JAIL plugin services in a Virtual Box environment

[guntman]

I started two days ago setting up freenas 8.3 in a Virtual Box environment (Version 4.2.6) and everything went smooth so far. Set up some services like CIFS.
As soon as I started to install the plugins like Transmission or DLNA I ran into an issue with accessing the jail instance GUIs and services from my network.
My host runs with 192.168.1.29 and I have configured a bridged network connection where freenas got 192.168.1.50 assigned and the jail 192.168.1.51.
I am no expert on the network side of things and probably I would have to set up new interfaces and static routing. Any hints, tips, experiences with virtualization of freenas
are welcome!

 

[guntman]

In the meantime I have setup a bridge interface (192.168.2.1) from within freeNAS and configured the epair0a by adding it to the bridge and epair0b (192.168.2.2) on the jail side. With epair0b I also added the default route back to 192.168.2.1. As a result the communication works between the freenas bsd and the jail bsd but still I cannot reach the hosts in my 192.168.1 network. As em0 and bridge0 are both on the freenas system I am wondering why the packets do not get forwarded to the 192.168.1 network. (for 192.168.2 I also added a static route for this network on my router (192.168.1.1) by the way).

 

[tidus532]

I had the same issue, the fix is to set the promiscuous mode to "allow all" in the network adapter settings. It seems that virtualbox only passes the packets that have the bridge between virtualbox and freenas as destination.
As the bridge between the plugin jail and freenas has a different IP, virtualbox will not pass them to your VM. Promiscuous mode overrides this behaviour and delivers all packets to the freenas VM.