Setting up FOG 1.2.0 in Multiple VLANs
-
I’m going to take a step back and make sure I have my router configured properly.
[QUOTE][I]Tom Wrote[/I]: We have 12 separate VLANs in our organization. All have their own Gateway’s that lead back to our routing switch. Our routing switch has an ip-helper setting back to our central DHCP server for their related Gateway. This way there’s still a gate to communicate across, and the routing switch has all the routes configured to allow pass of traffic from one subnet to another.[/QUOTE]
I’m researching how to configure our FortiGate router to make FOG’s IP visible across all VLANs. If anyone knows how I should setup the FortiGate so the VLANs can communicate with the FOG Server’s IP I’d appreciate it. My network engineering experience is limited.
-
does this help any? [url]http://fogproject.org/forum/threads/multicasting-over-vlans-get-stuck-at-please-wait.5436/#post-14158[/url]
Sorry I don’t know anything about fortigate
-
Reading the wiki on setting up DNSMasq to try. Will report back.
Still would like to know how to setup an ip-helper setting on a FortiGate router if anyone knows.
-
[quote=“Jaymes Driver, post: 37013, member: 3582”]does this help any? [url]http://fogproject.org/forum/threads/multicasting-over-vlans-get-stuck-at-please-wait.5436/#post-14158[/url]
Sorry I don’t know anything about fortigate :([/quote]
I’ll check it out and try that; however, multicasting isn’t the main problem right now. It’s just being able to use FOG across all VLANs. I can’t even PXE boot from another VLAN - only the VLAN that the FOG server is located.
-
I mistyped on previous post.
It will boot to the fogserver’s PXE (not the FOG menu) - it will timeout when default.ipxe is trying to load.
Chainloading solved the issue but only for the VLAN FOG is on.
-
here’s something for you to try
[CODE]chain http://10.52.4.23/fog/service/ipxe/boot.php?mac=${net0/mac} || chain http://10.52.8.23/fog/service/ipxe/boot.php?mac=${net0/mac} || chain http://10.52.1.23/fog/service/ipxe/boot.php?mac=${net0/mac} || etc[/CODE]
on each failure, it will try the next chain command -
Nice hack! It almost worked.
While I was testing it on another VLAN from the FOG server it did as you said and went down the list trying the different IP’s; however, when it finally got to the right VLAN IP and wanted to download bg.png it failed because it was trying to download it from FOG’s native IP (10.52.4.23). I say “native” because that’s the IP that’s setup in FOG’s settings because I had no choice as I couldn’t add FOG’s hostname instead.
I was in the Elementary 10.52.[B]16[/B] vlan
[QUOTE][url]http://10.52[/url].[B]4[/B].23/fog/service/ipxe/bg.png… Connection timeout[/QUOTE] -
[quote=“Jaymes Driver, post: 37013, member: 3582”]does this help any? [url]http://fogproject.org/forum/threads/multicasting-over-vlans-get-stuck-at-please-wait.5436/#post-14158[/url]
Sorry I don’t know anything about fortigate :([/quote]
I read on another thread that you use the DNSMASQ technique for FOG - I followed the wiki guide and set it up here as well. I’ve set the ip-helper/dhcp relay up to point back to the FOG server; however, it still cannot boot to the FOG menu because everytime iPXE loads it tries to pull the boot.php file from the wrong IP (much like the above result).
Should the dhcp-relay/ip-helper be different on each VLAN (I’m using FOG’s respective VLAN IP)
Any ideas?
-
[quote=“Christian Nichols, post: 37570, member: 2195”]I read on another thread that you use the DNSMASQ technique for FOG - I followed the wiki guide and set it up here as well. I’ve set the ip-helper/dhcp relay up to point back to the FOG server; however, it still cannot boot to the FOG menu because everytime iPXE loads it tries to pull the boot.php file from the wrong IP (much like the above result).
Should the dhcp-relay/ip-helper be different on each VLAN (I’m using FOG’s respective VLAN IP)
Any ideas?[/quote]
I’ve never had success (in my messed up network) booting to my fog server from another VLAN. I know that with dnsmasq it is technically possible but I don’t have any experience in doing so.
My network stems from one building and is dished out to each of the other buildings. Each building is a VLAN itself.
I would assume (and you know what happens when you assume) that the ip address would be the same across all VLANs, the ip helper is just to help point that VLAN back to your fog server ip.
-
[quote=“Jaymes Driver, post: 37572, member: 3582”]I’ve never had success (in my messed up network) booting to my fog server from another VLAN. I know that with dnsmasq it is technically possible but I don’t have any experience in doing so.
My network stems from one building and is dished out to each of the other buildings. Each building is a VLAN itself.
I would assume (and you know what happens when you assume) that the ip address would be the same across all VLANs, the ip helper is just to help point that VLAN back to your fog server ip.[/quote]
I just tried a couple of different things. Changing the dhcp-relay/ip-helper IP, removing the Scope Options from the DHCP server, re-enabling Scope Options with FOG’s hostname instead of VLAN IP.
Meh… I’m giving up. I’ll just make the proper changes to get them to work on one of the VLANs everytime we need to re-image a computer.
Thanks to all of you that tried to help
-
Sorry I can’t be of more help, I set up a server at each of my locations, but that works out to my benefit because each building uses the same base, but this lets me tweak the settings to better fit that novell context.
