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

@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 Thanks for sharing that. I think that will be very helpful to me on my project

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

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

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.

I would like to do do it all in one box.

Right now the box will just be handling one Lab/Room, and will largely be an experiment. If it goes well we would like to to set up a more central Fog server (either a VM or physical box) and start migrating our Macs and then out Windows deployments onto it.

I’ll definitely take a look at pfSense, I’m sot sure a whole distribution solution like zeroshell would be the way to go, since I would have FOG on the same box.

Right now I’m working with a i3 quadcore 64bit (Sandybridge), with 4GB of ram. Its a micro form factor so I’ll take a look at to see if I can’t bump up the ram to 8 GB.

@Wayne-Workman
Kewl, both are great posts, thank you guys.

I would personally would like to avoid having dual NICs in the lab boxes. Since I would be well behind the schools security walls and on the internal network I don’t necessarily need to turn the box into a full fledged router with all the security bells and whistles. I think it would just need the NAT software and basic routing of all but the DHCP & PXE traffic between NIC A & B. Or if I could get a lower end router to do that too would be nice. Some cursory googling makes it look like software wise it wouldn’t be too difficult to set up the NAT program on Linux. Time to rummage in the storage closet to see what we have that might work.