Planning out a FOG install.
-
OK. Overall I plan to stay within “stable” releases. One of my goals once its set up, to be able to remotely manage it so it will be headless, and leave behind sufficient documentation for future administration after I’ve graduated next year.
-
@Wayne-Workman Thanks for sharing that. I think that will be very helpful to me on my project
-
@chimchild Just remember, my project is GPLv3, so to use any of it, your project must be GPLv3 as well.
-
@Wayne-Workman been looking over your script/code. To disable the VPN portion would I just need to comment out or remove lines 43-100? of the functions.sh file?
-
@chimchild A lot more than that, look at the make_setiptables() function. Also, all the components are called from the install.sh file. lines 51 - 53.
Not even going to pretend that adapting my project will be easy or optimal, but do-able yes. The whole project was made from the perspective of forcing a network through a VPN transparently and reliably.
-
@Wayne-Workman
Will keep that in mind. This is still in the planing and tryng different setup & configuration stages. I don’t think the Lab itself won’t be set up until the end of summer. -
I’ve also been looking at something like this https://www.howtoforge.com/nat_iptables as possible solution or part solution, especially if Fog itself can handle the DHCP requests.
-
@chimchild That would do it. I favor iptables for major network appliances. It’s commands and config make more sense to me than firewalld does.