Off site node with meraki vpn
-
Just making sure there isn’t any extra steps I’m missing with 1.4.4. The master node/server is setup at the main location where we are on a x.x.248.0 subnet. The second location where the slave node will be is x.x.255.0 subnet. I can ping the other locations work stations IPs and access every station via WIMS addresses. Is there anything outside of standard node install that needs done? Haven’t had the pleasure of setting one up offsite yet so wanted to make sure I’m ready when I go to configure everything.
Would like to take the time to thank the developers and the FOG community for all the hard work and documentation that’s out there. Once we go over our budget at then end of the year, we plan on making a donation to the FOG Project for your efforts.
Thanks in advance
-
@jphipps said in Off site node with meraki vpn:
The master node/server is setup at the main location where we are on a x.x.248.0 subnet. The second location where the slave node will be is x.x.255.0 subnet.
While this is very little information I am still trying to give an answer. You may need to add some more so we can get the bigger picture. From what I understand you have two separated networks. Both on a different subnet mask. If pinging works (both directions?) I suspect routing between those two subnets being setup correctly. That’s a first important step.
Then other questions arise:
- What do you mean by “slave” node? Storage node?
- What is providing DHCP information to those clients in the other location? Possibly ip address helpers are needed to make the DHCP broadcasts reach the DHCP server in case you only have one in your master location.
I think it’s best to install the second node and see how things go.
-
Each site has its own DHCP server handing out different IP ranges. And yes by slave I mean regular storage node. I’m going to assume that the node will need to look back at the DHCP server for the site it will be at since it is in a different subnet.
-
@jphipps As long as routing is working then FOG should be happy. Each local dhcp will point to the local fog server. If you are using the fog client then your fog clients will need to “check in” to the FOG Master node for instructions. Depending on the size of your organization that may add load to your site to site link. The FOG servers use FTP to replicate from the master node to the storage nodes.
While its possible to run in a network where there is a firewall between the sites, its easer to setup if you don’t have any network restrictions between your sites. -
Do to HIPPA regulations a firewall is required at each site.
-
@jphipps Does this firewall filter internal traffic or only external traffic (not generated by your site)? I probably worded that poorly. What I’m trying to identify if there is any restrictions to internal routing between the sites.
-
@george1421 Sorry for the delayed reply, been SWAMPED. Anyway, so far it’s working with no issues, basically plug and play since I configured it here and had it delivered. Setup a bash to send me an email when it came online. As soon as it came up, I added it the console and replication took off… by the way, forgetting to limit bandwidth before replication start upsets a lot of users LOL. Now if I can figure out why these new Dell Latitude 3570’s will let me register them but not load the menu after I will be all set.
Note: No the firewall only filters external traffic, sorry I meant to start off with that.
