On 1 December 2015 at 06:48, Nathan Aherne <nat...@vuid.com> wrote > Thank you for helping me to understand vimage better Julian! I have read > all three links you posted a number of times. > > I use iocage for jail management and it uses epair. From your comments it > seems you recommend netgraph? > > This is the link to the iocage image instructions - > https://iocage.readthedocs.org/en/latest/networking.html#configuring-a-vnet-jail > < > https://iocage.readthedocs.org/en/latest/networking.html#configuring-a-vnet-jail>. > It seems that iocage does a number of things automatically or at least I am > still confused on how to use iocage and vimage to have multiple jails share > a single public (external) IP. I will continue to read the links you sent > me in the hopes that the ahah moment comes to me. > > Regards, > > Nathan >
The public IP will be configured on whichever device you have connected to the internet. Normally that is a physically separate edge firewall/router. It has the public IP and performs NAT for any devices on the LAN that talk to the internet. This configuration has nothing to do with your jails - it is required for any computers on your LAN which talk to the internet. The jails are then each configured with a LAN address (10.0.0.0/8 range if you like). When they need to talk to the internet, they will go via their default route, which is normally your edge firewall/router, and is often given a 10.0.0.1 address (but could be anything you like). The router will perform the NAT, and if you want the jails to host service listening for internet traffic, you will also need to configure port forwarding on the router to send traffic on the relevant ports to your jails on their LAN IP address. Note that if your router happens to be the host running the jails, this doesn't change any of the above. Regards, Ben _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
