Planning out a FOG install.

[Wayne Workman]

@george1421 In trunk, the interface stuff is corrected now, just fyi. The installer intelligently detects the correct interface and IP to use.

[chimchild]

This is a very informative thread

I fully understand that the configuration and steps you lined out are from you and not FOG.

I apologize if I didn’t articulate all thoughts in my head (finals this months so there’s more hamsters than normal running the wheels)

I was looking at possibly NAT-ing at the FOG box. Have the lab on a private IP range (i.e. 192.168.x.x/24) and have the Fog box NAT/Route those IP to a single weber.edu address. Over the next month or so (after finals) I plan to have a sit down with out network group too. Hopefully they will be fine with a NET situation or assign the room a specific ip-range/vlan. I expect that they definitely want to keep the clustering traffic off the school’s network.

Its great having multiple config options available.

[chimchild]

@Wayne-Workman

@Wayne-Workman said in Planning out a FOG install.:

@chimchild Man, honestly, tell your uni to go to wal-mart and get a 30 dollar router. (or something better).

I don’t really have a budget; I’m sure if I have sufficient justification I can get reasonable purchases authorized. Personally I enjoy the challenges of re-purposing & “recyleware”. So far all hardware (except the new boxes for the lab computers) is stuff I’ve pulled from our storage closets, or the campus warehouse store.

And this has been a nice refresher & educational Linux project for me, that I believe will translate well into real-world post-graduation interviews in the next couple years.

[chimchild]

@george1421

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.

[chimchild]

@Wayne-Workman Thanks for sharing that. I think that will be very helpful to me on my project

[Wayne Workman]

@chimchild Just remember, my project is GPLv3, so to use any of it, your project must be GPLv3 as well.

[chimchild]

@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?

[Wayne Workman]

@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.

[chimchild]

@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.

[chimchild]

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.

[Wayne Workman]

@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.