Which version of FreeNAS are you guys running btw?
This is how the iocage plugin sets it up on a FreeNAS-11.2-RELEASE-U1 test box I have.
I found the VNET issue is a known issue and has been reported as a bug with plans to fix but there is a work around that you can add to your tunable.
See this thread…
1 Like
I also found VNET doesn’t work with a static currently. I had to reserve the IP in my DHCP server and set the jail to DHCP to get network traffic with the work around listed above.
Ok so here’s where we stand. I enabled vnet and dhcp last night and was able to refresh metadata and play files. So I went ahead and added my remaining files, refreshed all the metadata, and tried to run it on the devices that it wouldn’t work, and low and behold it all works! My warden jail is still experiencing the issues from before but I don’t care as long as it works on the new jail. It’s a little crappy I had to do a new database but it’s fine. If I stop the warden plugin and jail my new server seems to want to not run properly so I’m not even gonna mess with it, as long as it’s working. I had enabled static ip at the router level to get around the dhcp issue and it wasn’t working last night but this morning I woke up and the ip I wanted had taken effect so that’s good, now I can port forward properly.
Thank you for the help!
Nice! Glad you got it working. This thread helped me get mine working too for the most part. I’m still having some issues but I believe it to be related to the iocage so it is a FreeNAS issue.
Knowing that VNET is required was also EXTREMELY helpful. If not for that I’d still be fighting with trying to get the Metadata to refresh!
I’m glad I could be of help and I am thankful for the other help on this forum!
So, I guess great team work! LOL
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
