Posts made by igorpa2

@george1421

@george1421 said in FOG With more than 1 subnet:

What host OS is the fog server running?

I’m using debian.

After some searching on internet, i found this steps(https://gist.github.com/troyfontaine/59ace875a951154f881bfe3d297d1a10) to configure PFSense with VLAN and TFTP Server. After configuring the step 3, now i can boot on the other vlan(172) but it’s more slowly than the vlan 200 to receive the boot file. But it works!! I don’t really know yet if this is the problem, but it worked haha. Now i’ll make some tests and see if the imaging it’s working correctly.

Thank you.

@george1421 Ok, i will check de pfsense again. The first thing i really thought of was him. But since I was not successful, I came here to ask for help hehe. I don’t understand why it could be blocking, because, as I said, I released all the ports and protocols of everything that comes from the 172 network and that go to the main FOG address.

@george1421 said in FOG With more than 1 subnet:

@george1421 If its not an mtu issue then lets see if you can connect to the port. Microsoft has a tool call portqry that we can use from 172 to connect to the fog server on 200. All this tool does is try to open a port at the defined IP address. It doesn’t know what the port does it just tries to reach it.

https://learn.microsoft.com/en-US/troubleshoot/windows-server/networking/portqry-command-line-port-scanner-v2

In the case of tftp its udp port 69.

The command might look like this

portqry.exe -n 192.168.200.55  -p udp -e 69

FWI: 192.168.200.55 represents whatever the fog server’s IP address is for the imaging network.

If you can’t connect to the port then we need to look at the fog server to see if some kind of firewall is enabled on the fog server, to-where why it only allows communication on the local subnet.

Here’s the command result:

(I hid the IP because it is a real ip)

@george1421 said in FOG With more than 1 subnet:

@igorpa2 OK then I guess you need to see if its an mtu issue then

Here is a good article on this: https://www.comparitech.com/net-admin/determine-mtu-size-using-ping/ look at the section “Find the path MTU with a Ping command”

I kind of don’t think is this the issue, but the test is pretty easy. From a windows or linux computer on the 172 subnet run the ping command as outlined in that document. I think the magic number is having an MTU larger than 1468, this is the default tftp block size. If your MTU is 1500 more less then this issue isn’t related to MTU. If your mtu is less than 1468 then we can adjust the block size on the fog server to be less than your mtu.

I discoverd the MTU is 1472. Sending a ping above this with the option “do not fragment” it returns the message “ping: local error: Message too long, mtu=1500”

@george1421

1. Yes, i can ping each other on both two subnets.
2. Yes, pfsense itself. I set the rules to pass all ports and all protocols between the FOG IP Server and the 172 network.

The MTU is in blank, what seems to be the default 1500.

@george1421 I have tested to use only one FOG to use on all subnets and I have a problem that I can’t transmit the file via TFTP. My client on network 172 normally receives the IP from DHCP, but does not receive the file to boot.

I also did the following test: I entered my FOG from network 172, and 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 . Do you have any idea what it could be? In clients from network 200, the boot occur normally.

@george1421 said in FOG With more than 1 subnet:

@igorpa2 said in FOG With more than 1 subnet:

Just to know, it’s possible to use only the Master FOG installed on 200 network with one network interface and this work to all others subnets

Yes this is how I have it setup on my campus is that just one fog server and one interface can image all 6 vlans. Understand that imaging across your vlans will put a network load on your vlan router which may impact your overall transfer rates. Imaging a fog server on a 1GbE network on the same vlan as the fog server, you should see transfer rates (according to partclone) in the 5.5 to 6.2GB/min using contemporary target computer as a baseline. Across your subnets I would expect in the lower 5GB/min range. Now my infrastructure used 10GbE in the core with a 10GbE router and I see 13-14GB/min to target computers attached to an access layer switch at 1GbE.

Yes, in our 1GbE network, we see 5 to 7GB/min transfer rate, like your network, but when client connect on node that are on another subnet(client on 172 subnet coneccting on 200 node) the transfer don’t exceed 2GB/min and some cases reaching a whopping 20~50MB/Min. I honestly don’t know why this happens, but I’ll check all the settings again and test using how you use them and see what problems we have. I will update this thread again with any conclusions I reach.

Thank you.

@george1421 said in FOG With more than 1 subnet:

@igorpa2 Ok the last bit of setup for the location plugin is to assign target computers to the location that way they know which storage node is their home server.

Once you do that the pxe booting computer will contact the master node during pxe boot, load ipxe then find out which storage node to use to pull the image from.

Just be aware the way fog works, you can only capture images to the master node. Slave nodes are deploy only nodes.

So the linkage is storage node to a location and target computer to a location so they can both find each other.

Well done, i have configured the hosts. Thank you George for help, tomorrow i will test if will work. Just to know, it’s possible to use only the Master FOG installed on 200 network with one network interface and this work to all others subnets ? I will test this environment again to see if i will have problems and/or to remember what problems i had when on i installed the FOG for first time. Thank you!

@george1421 said in FOG With more than 1 subnet:

@igorpa2 said in FOG With more than 1 subnet:

No, i don’t have installed the location plugin.

Without the location plugin the clients will typically image from the master node until the client count is reached then the next target computer will roll over to the slave node.

So go and install the location plugin. Create your two locations. They can be called anything just they must be named differently. Finally assign a storage node to a location.

Okay done, installed, created and assigned.

@george1421 said in FOG With more than 1 subnet:

So to the imaging point. You have two storage nodes. One is the master node and one is a slave node. In your configuration are they in the same storage group?

Yes

@george1421 said in FOG With more than 1 subnet:

If yes, did you install the the Location plugin into the FOG server and assign each storage node to a location?

No, i don’t have installed the location plugin.

@george1421 said in FOG With more than 1 subnet:

So have you confirmed that pxe booting works correctly for both uefi and bios on each subnet?

With our actual scenario, yes.(One master fog in 200 subnet with one network interface on it and another fog installed as storage node on 172 subnet with one network interface).

@george1421 We have one PfSense as DHCP Server. We have options 66 and 67 configured on dhcp server of each subnet. undionly.kkpxe for bios and snponly.efi for uefi.

@george1421 No no, it’s on same campus. We have one LAN network with more 3 Vlan’s. We have FOG installed on LAN interface(200.x.x.x) and we added another interface(172.x.x.x), because when on clients on subnet 172 network, we have encountered some problems. I don’t remember anymore if are pxe boot or imaging problem we have encountered because we installed in 2018 =P . I can test again and try to use fog only with one interface and see if the boot and imaging works with only the LAN interface on both subnets(200 and 172).

@george1421

1. With the fog with two network adapter, they boot only on legacy clients. On UEFI clients, only on the subnet that have configured on installation process they boot. With the FOG with one network adapter + one FOG Storage Node configured in other subnet, both uefi and legacy pxe boot.

2. With the fog with two network adapters, yes, but when i put the FOG Master installation in one subnet and the FOG Storage Node in another subnet, no. What I wrote in the previous post happens, where for example, a client that is on network 172, tried to use network node 200 and, a client that was on network 200, tried to use network node 172 causing rate problems transmission as mentioned above.

Ok, thank you for response.

I have encountered some problems like, when i boot the client with UEFI bios from the same network where FOG is installed(IPADDR set up on .fogsettings) the boot occur normally, but when i boot from another network, the client does not receive anything from the server. This occur only on UEFI boot, if i boot from legacy device, i can boot normally on two networks. In this scenario, i have one VM with two virtual network cards, one for each network. The first thing i thought, its the TFTP nothing working correctly with this infrastructure, then i disabled the network card that was not booting and created another FOG VM and installed as Storage Node to see if the problem is resolved. Then now, i can boot with UEFI in two networks, but now, when i will deploy an image, the server node used is not always on the same network as the client causing my transfer rate to drop dramatically. It happened that a client was on network X, connected to node Y and, when I deployed to a client Y, it connected to node X. hehehehehe I had to disable the storage node in FOG to “force” the client to access the node on same network to use all my gigabit network bandwidth on the deploy process.

The way I installed and thought about fog, is it wrong? Can I use it with just one interface and it works correctly on all networks? Because I remember when I installed FOG for the first time, some FOG function didn’t work on other networks by installing it this way. I don’t remember if it was the multicast or another problem.

Re: [HELP]Using FOG with diferent VLAN´s

Hello guys, is there any news about how to install and configure FOG, with more than 1 subnet ? (I tested with 2 different ways and have encountered some problems using it.)

Thank you!

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.

Hello guys from FOG community, i want to know if it´s possible to make Hardware-Independent Images on linux systems ? In the tutorial on “Making Images” link, i found only the windows tutorial and don´t saying anything about linux. Can anyone help me if it´s possible ?

Thanks for attention and sorry for not so good English…rs

Regards, Igor.

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

Hello people, i want to update my FOGServer from 1.5.4.8 working bench to new version 1.5.5 and when i tried to download the FOG from GITHub like this tutorial page https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG the GitHUB is soliciting login with user and password, something that had not happened before. Is it still possible to download FOG through this method? Thanks.

Regards, Igor.