thanks Chad, didn’t realise you could auto-register with the client, tbh I’ve never used the client in a domain environment. But am planning to use this for our student images (workgroup) for remote sites.

Slightly off topic but the client needs to be configured with fogs IP address (or host) according to the screenshot on the wiki.
I want to use a universal image and not have to hard code specific IP addresses, so I guess I should use a name. But then the next challenge is to get these student machines to resolve that name without a dns server, reason being they will use their own ISP, I guess a workaround would be to make fog a dns server also, just to resolve the fog server itself and then pass everything else to the ISP.

I’m all ears if there’s a more elegant solution.

Hi Raff,

There is routing between the subnets, clients on either can talk to each other.

It’s just that I can’t image from the subnet that is different from Fog’s main subnet, even though it has two nics and is on both subnets.

Clients can get to the menu on either subnet, but can only be imaged on one, this is the confusing part.

Raff, could you possibly describe your network layout and how the single fog server is able to service 40 subnets?

I’ve been doing some research into virtual IPs / interfaces, static routes etc and I think I may of found using iptables maybe the best way of getting this to work and was just wondering if a networking guru can confirm I’m going about this the right way.

So I build a fog server with two nics, 1 nic on each subnet (student / staff).
When initially installing fog I set it’s default IP to one on the student network.
Student pc’s image as normal.

Staff pc’s on the other hand see the fog menu but no commands work.
(respective dhcp servers on each subnet have the boot options pointing to the relevant nics on the fog server)

[B]A Possible solution:[/B]

#Enable IP Forwarding

[COLOR=#333333][SIZE=4][FONT=Tahoma][COLOR=#000000][SIZE=13px]echo 1 > /proc/sys/net/ipv4/ip_forward[/SIZE][/COLOR][/FONT][/SIZE][/COLOR]

[FONT=Helvetica Neue][COLOR=#333333][SIZE=4][FONT=Tahoma][COLOR=#000000]Then configure iptables to forward the packets from staff subnet on /dev/eth1, to student network on /dev/eth0. with the following commands:[/COLOR][/FONT][/SIZE][/COLOR][/FONT]

[FONT=Helvetica Neue][COLOR=#333333][FONT=Tahoma][COLOR=#000000] /sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE [/COLOR][/FONT][/COLOR][/FONT]
[FONT=Helvetica Neue][COLOR=#333333][FONT=Tahoma][COLOR=#000000] /sbin/iptables -A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT [/COLOR][/FONT][/COLOR][/FONT]
[FONT=Helvetica Neue][COLOR=#333333][FONT=Tahoma][COLOR=#000000] /sbin/iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT[/COLOR][/FONT][/COLOR][/FONT]

The “bypass host registration” entry I had with hard coded IPs didn’t work when I copied and changed for the other subnet.

Menu entries appear, but doing any action just causes it to hang, e.g. doing a full host registration, it correctly see’s the hard disk, then says “Starting host registration…” and just stays like that for a long while, then it comes back with the specs, and attempts to send and hangs for longer.

On the default subnet this works as expected and no hangs.

Fog’s default IP is on subnet one, the test machine is on subnet two.

Falko, can you tell me how you initially setup fog, specifically the IP / networking portion when going through the script.

Great info, we’re using simple netgear switches, I think the problem is I’ve overthought this, I’ve an automated image pulled via a menu selection and have just realised that this has the IP address of fog hard coded, this must be why imaging fails on other subnets.

Thanks for your help, I will do some more testing

Hi Falko,

To confirmed you have [B]One[/B] fog server serving both subnets or [B]Two[/B] servers?

If One, could you describe the the setup?

If say the fog IP is set to 192.168.1.0/24 and student machines are on 192.168.2.0/24, how are you able to image the student machines? Doesn’t it fail once you get past the menu’s and you select an action? e.g quick reg / imaging etc.

A way to setup fog with the IP addresses of all the nics.

Maybe add an extra layer / check to see which subnet the client is from and amend fog’s IP to the correct subnet accordingly. This would make this immensely more efficient.

As it stands a fog server has to be built for each and every subnet.

If there’s a way to hack around this I’m all ears

This is a tool I use often - [url]http://www.softperfect.com/products/networkscanner/[/url]
You can use it as ssx4life mention, to scan the network and export the computer names and macs.

If you want a slightly more automatish way of extracting macs from your domain you can actually query the dhcp server with netsh.

We have a lease time of 3 days so I have a script (mixed with grep and sed from unix tools - [url]http://unxutils.sourceforge.net/[/url] ) to query the dhcp server and extract the macs to a file, then filter and export to a bigger / master file that I use for wake on lan scripts (nightly virus scans).

Here’s a script I use (you can amend to include the computer name)

[CODE]:: Script to extract mac addresses from DHCP for both subnets.

:: Delete macsDB.txt if exists
if exist “C:\scripts\WOL\newMACs.txt” del “c:\scripts\WOL\newMACs.txt”

:: Query for MACs on 2 subnets
for %%a in (22,23) do netsh -c dhcp server 10.10.%%a.25 scope 10.10.%%a.0 show clients | grep 255.255.255.0 | sed s/-" "//g | sed s/."255.255.255.0 “//g | cut -d” " -f 2 | grep -Fvf macsDB.txt >> newMACs.txt

type newMACs.txt >> macsDB.txt

:: WOL - SUBNET 1
for /f “tokens=* delims=” %%a in (macsDB.txt) do wolcmd %%a 10.10.22.0 255.255.255.0 7[/CODE]

I have a scheduled task that runs the above script, but the essential part is the “netsh -c dhcp server <ip of dhcp server> <subnet> show clients”

That should show you the current clients based on your lease time, run repeatedly (according to your lease time) to build up a list of valid macs.

No option to delete unfortunately, can only delete comments from #2 onwards.

[IMG]http://i.imgur.com/nIsX6.png[/IMG]

Regarding the DHCP, I can take care of that on each subnet, the problem comes with how fog is normally setup (on one IP address).
I can make clients on each subnet boot to fog, but when it comes to imaging it fails as alot of the commands have the original setup IP address (and therefore subnet) coded into the commands, so actions always fail.

I just want to know more of these so called advanced networking options that can be applied but are not mentioned anywhere on the wiki.

I’m happy to hack some scripts if need be, any advice / direction would be welcome.

Moderators, apologies for the multiple posts, was having a real hard time submitting a post as it kept erroring out, had no idea post was actually submitted.

Please delete the other posts I’ve made prior to this.