As time goes, time to time i turn back to my previous things for refreshing memories, getting new ideas, whatever. So it happened to this topic.

I am again thinking about fully offline cases. We here discussed that zstd compression is not compatible with clonezilla so i have to recapture image to use tools like clonezilla which uses same image taking tool. But… as now i have read, clonezilla now capable using zstd compression (er… whatever it means exactly btw).

Let me ask if it is still true or not to use already taken images (by for) deploy from a live clonezilla-like tool without recapturing? Anyone tested maybe?

@Almeida
@Sebastian-Roth

this is a simply example, security is by your side:

#!/bin/bash SERVER=$1 USERNAME=$2 PASSWORD=$3 FILE=$4 USER_TO_LAST=$5 echo "Result from last $USER_TO_LAST" &> $FILE last $USER_TO_LAST &>> $FILE lftp -u $USERNAME,$PASSWORD $SERVER << EOF put $FILE EOF

Configure as on image:
Snapin template is bash.
example.png

Tested on Linux Mint 19.

@george1421 Thank you for the response. The issue was the switch. I put a “dummy” switch in place of my other one and it worked. I ended up enabling fastport on my other switch and success. Appreciate the help!

@MediumToast i thought this might interest you https://forums.fogproject.org/post/123288

Resolve this please.

@loosus456 What OS is your FOG server running?
You will also need to be able to configure your network switch to support LACP (802.3ad) LAG.

No we do not have any requirement. we just want computers to work as normal with our modified image.

Thank you for quick response. Please mark this as answered.

@virtualdxs You can actually give it a try already! Would be great if you’d join in as tester to help us bring it forward.

git clone https://github.com/FOGProject/fogproject/ cd fogproject git checkout working-1.6 cd bin ./installfog.sh

@Sebastian-Roth Hello, yes I have setup 3 servers with fog running and I was successful in capturing the image and deploying it to 18 computers at the same time. I did look at FOG API, but I had questions about it like does is it run on bash or other script but later figure that it runs on bash.

@Sebastian-Roth Thanks!

@flo FWIW, one of the developers are adding your request to the LDAP plugin. Those should be in the mainstream code on the next release of FOG 1.5.6.

Fog did configure dhcp and it worked. we still modified it according our need. please resolve this.

@george1421

My MySQL knowledge is pretty shallow. For this situation I’ve got enough data, but I’ll read up and maybe change things then.

@mpatel For CentOS use the following:

dodhcp='Y' bldhcp='1' dhcpd='dhcpd' packages='bc curl dhcp ...'

Then re-run the installer and see it do the work.

@jsch Do you use the FOG DHCP server. I suppose you don’t. Please try changing the PXE filename from ipxe.efi to undionly.kpxe and see if that works for you.

@mpatel Disabled SELinux and Firewall???

it did finish. but took long time. Thank you guys. please resolve this.

@FeatherlessBiped This has been an ongoing topic. See my post here: https://forums.fogproject.org/post/117517

FOG was initially build to be bound to one interface and this is still the case in various places in the code and logic (PXE boot, multicast, unicast, capture). So it’s a heavy task to do all the changes and the FOG dev team currently does not seem to have the resources to do so. Don’t get me wrong. This can definitely be done and we will surely encourage and help people who want to implement multi-homing for FOG!

@george1421 No unfortunately I dont have an available to me to test.

@cary1102 For that to work you need to push the router/gateway information to the clients in the 10.10.222.0 subnet. Add the following line so your config looks like this:

subnet 10.10.222.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 10.10.222.XXX; ...

Put in the gateway IP address instead of XXX. I suppose you have a router/gateway that is making communication between the two different subnets possible?!?

You need to know that there might be other obstacles still in front of you. The clients use a couple different protocols like HTTP (easy), FTP and NFS to communicate with your FOG server and so the gateway needs to forward all those for the clients to be able to work properly.