Topics created by igorpa2

@banaunnuh said in FOG With more than 1 subnet:

used the TFTP get command for my main FOG server and got the same error when I try to boot with the 172 clients. The file does not come, it gives a timeout error

Can you ping the fog server IP address from the 172 subnet?
Is there some kind of screening/firewall between the 200 and 172 subnets? The tftp protocol uses UDP port 69 NOTE: If you test tftp pull between a windows computer on 172 and the fog server on 200 you need to temporarily disable the windows firewall on the test computer because tftp, is like FTP in that it opens a command channel and a data channel for communications.

No, no, sorry for not clarifying. It’s just an open question, because I’ll do it, but we don’t know if it would work or not. 😄

Thanks for clarifying George. I will do and test and if we encounter any error or problem, i will ask here for support. Thanks again!!! 🙂

Regards.

@george1421 Thanks, with this commands above i was not presented to enter password, thanks.

Hello guys, just to give feedback to you, everything is working now, but only multicast is not working correctly. The multicast starts normally and deploys the image between the 3 VM´s, but the transmission rate got too low, worse than using unicast mode for the 3 VMs, I’m trying to find some solution on the internet now for my problem, it’s probably some configuration for the internal network in VirtualBox. Anyone have any ideia or know about this ?

@cml said in [HELP]Using FOG with diferent VLAN´s:

@igorpa2

Just circling back to the original issue. Can you ping from a device on the 200 network to a device on the 172 network?

If not, what do you have as your layer 3 device?

Yes, i can ping from device in 200 network to and 172 network.
My layer 3 device is a pfSense Server controlling the network.

@igorpa2 Well with Normal FOG servers and Storage Nodes there are some things you need to keep in mind.

Both Normal and Storage nodes and support pxe booting of clients. You would point the dhcp server scope to boot from the fog server that is closest to the client. The pxe booting client computer must be able to contact the full fog server during pxe booting to find out where it’s assigned fog server is located. Storage nodes must be in contact with the main fog server 100% of the time. All of the file transfers will happen between the client and the assigned storage node. You can only capture images to the master fog server. Storage nodes can only send images to target computes. For every computer that the FOG service is installed, it must be able to react the master FOG server to check in for waiting tasks. The Location plugin can be used to assign target computers to specific storage nodes. If the location plugin is not used then a random storage node will be assigned to the target computer.

The idea of a normal or master FOG server and storage nodes are to place storage nodes at remote locations behind sometimes slow WAN links. The remote clients would then load the pxe booting and imaging files from the local FOG server, not needed to pull the imaging across the slow WAN links. You can also use the master node and storage node on the same campus for load sharing if you are sending out a large number of unicast images to many clients. But then if you are imaging many clients at one time, multicasting is a better way to image.

Hello guys, here again returning for feedback.

The multicast worked fine!! very good. Thanks for all devs and people who help us. Thanks!

Now, as said in the first topic, i´m very happy with this and thinking of doing my course completion work(TCC in portuguese) of University graduate about the use of FOGServer in computers lab.