I expect you are right and I didn’t get the right set of tunables.
I could never get the iocage to start-up with a working network until I removed the vnet and went straight with the em0 interface.
Charley
I expect you are right and I didn’t get the right set of tunables.
I could never get the iocage to start-up with a working network until I removed the vnet and went straight with the em0 interface.
Charley
The tunables may require a restart after you enter them and the “addm ‹gb0› up” tunable for your bridge should correspond to your network interface.
It’s possible I neglected to restart after setting those up, but I am pretty sure I rebooted after making those changes and I do remember making the change to include the em0 interface in the tunables.
Hmm, not sure what was going on then. With my setup I have a single interface , the server itself is configured with an IP of 192.168.2.11/24 and gateway of 192.168.2.1. Each iocage jail has a separate VNET IP, for channels it is 192.168.2.88/24. With the tunables I mentioned I have no issue creating the jail or using Channels.
The only thing that I can think of is that either there is a difference due to VMWare running FreeNAS or something about the version of FreeNAS that I am running being very new and not having been upgraded. It’s probably uncommon to spin up a FreeNAS just for supporting the Channels DVR. I probably did 6 fresh installs to make sure I had it right and documented and tested.
In any case this forum and your instructions were extremely helpful and I now have successfully transferred all of my recordings from the Windows based DVR to the FreeNAS DVR. This reminds me of nearly 20 years ago when I was upgrading, expanding, and enhancing my DIrecTiVo with strong community support.
It’s really great to have this type of support.
Charley