Tsaukpaetra
Patron
- Joined
- Jan 7, 2014
- Messages
- 215
(Wasn't sure if this should be in the Development section, I'm on the Nightlies so this option may not apply in the released version)
I've noticed that during plugin creation that the NAT option is selected by default. This is all fine and dandy, as everything *seems* to be working (with respect to the actual jail still having access to the Internet), and it gets an IP address 172.16.0.X.
My problem/question is this: Normally things under NAT (if they're expected to be accessible outside the private LAN) will have port forwards set up so requests directed to the gateway IP (in this case, I assume the FreeNAS's primary IP) will be directed into the network, business as usual.
However, I'm not seeing any such configuration option, and there's precious little information about NAT on the googles with regards to iocage.
I'm really looking forward to this feature, as it would help me cut down on the number of IP addresses used by my FreeNAS boxes.
I've noticed that during plugin creation that the NAT option is selected by default. This is all fine and dandy, as everything *seems* to be working (with respect to the actual jail still having access to the Internet), and it gets an IP address 172.16.0.X.
My problem/question is this: Normally things under NAT (if they're expected to be accessible outside the private LAN) will have port forwards set up so requests directed to the gateway IP (in this case, I assume the FreeNAS's primary IP) will be directed into the network, business as usual.
However, I'm not seeing any such configuration option, and there's precious little information about NAT on the googles with regards to iocage.
I'm really looking forward to this feature, as it would help me cut down on the number of IP addresses used by my FreeNAS boxes.