@sega said in FOG Multicast on different VLANs:

So some people already tried it?

Yes and so have I. You would need some way to dynamically change the network adapter defined in the global FOG settings to change the network adapter. You might also need to change a file called /tftpboot/default.ipxe to point to different interfaces. You might be able to get around this by setting up multiple tftp servers on the fog server, where each tftp server bound to a different interface and had a different home directory, that would be more of a long term change. And then you need to work out a way to update the imaging network interface in the fog settings depending on what interface you wanted to image using. There may be more crafty ways about doing this, but this is just off the top of my head.

@ecoele I can say this option will not probably be added by the developers since its such a niche or one off requirement. But I’m not speaking on behalf of the developers, I’m just stating my opinion. Its up to them to decide if a feature request has merit.

But fog being opensource its free for you to modify to your needs.

What I can tell you that there are several user defined fields you are free to add whatever data you want. On the database side I think the fields are called user1 and user2.

The second part is that FOG’s database runs on mysql (mariadb). This is much like any other sql server. If you have a windows computer and the mysql odbc driver installed you can query the fog database from a reporting writing tool running on windows. From there you can print labels, etc. You could do something as an excel macro to query mysql on the fog server.

Again on the mysql server, you could program something on the fog server in either python or php to extract the data from mysql.

@ecoele The fact that dev-branch is in 1700’s this informatino seems to indicate your’e still running the latest stable.

Once you switch to dev-branch you need to pull in the changes:

cd /your/path/to/fogproject git checkout dev-branch git pull cd bin sudo ./installfog.sh -y

Should get you installed.

You may also need to (from the browser) do a “CTRL + SHIFT + R” to do whats called a hard refresh in the browser to get all the latest/new javascript information.

@Floppyrub The code exists in the FOS system (when you boot a machine for a task, not on your server)

Sorry
with ipxe 1.21.1+ (gc30b7) it works but not with the latest version

@Lorenzo said in Fog iPXE Menu no input:

@Tom-Elliott
Hi
using the new version of ipxe build I can confirm that the ipxe menu works with the keyboard.
The problem is that chainloading grub, the keyboard doesn’t work.
With ipxe 1.0.0 it works. So by now we keep using the old version.

Lorenzo

@rogalskij Yes, I had read it and tried, but FQDN did not solve it for me…

@ rodluz

Okay - So I got FOG working on my rocky 9.6 set up with a few caveats.

I had to do some work to get tftp and pxe to work correctly.

created a symlink from /var/lib/tftpboot > /tftpboot

enabled and started the tftp service manually - systemctl enable tftp & systemctl start tftp

then created a file in /etc/systemd/system/tftp.socket.d/override.conf (after making a director /tftp.socket.d and giving that file permissions) with the following code:

[Socket]
ListenDatagram=69

[Service]
ExecStart=
ExecStart=/usr/sbn/in.tftpf --foreground --secure /tftpboot

reloading the systemd service daemon - “systemctl daemon-reload” & “systemctl restart tftp.socket”

The server would then pxeboot at least BIOS at this point.

The Web UI currently seems to have php conflicts. I installed php-8.0.30-3 and the modules connected to this when installing the server. The web UI has a quirk on the FOG configuration page when you have a button for DefaultMember FOG Version: () it is not printing the version of FOG or the versions of bzimage or init.xz files and in checking using curl http://ip-address-of-server/fog/service/getversion.php - i ony see - 1.5.10.1698

here is a picture of the error

error.png

Yes, was able to confirm it is working. Thank you for your help!

@boombasstic This is known and will be fixed automatically on the 15th, but please if you need to switch to the dev-branch and install it. Then you should be able to export reports.

@Tom-Elliott I figured it out.

I was getting confused by the similar language between the installation process and storage group setup.

A normal installation is just a fog storage node that has a web server and UI on it. A FOG network requires atleast one to work. However a Storage node can be set as the master of a storage group no matter the installation type.

My problem was that because the storage node in the “Bris” storage group did not have a master node setup, the default group could not replicate any images or snapins over. All storage groups must have a master for it to work effectively.

@Tom-Elliott feel free to clarify any of the above rant.

Thank you for the information. I used a bare metal machine. I started with a VM but then just used a old pc. I tried it with Fedora then Ubuntu but did not have any luck. I did not get any errors when installing with the install script.

I will take a look at the information you gave me and see if I can get anything working.

@collegestjoseph Can you try out this testing kernel and let us know if it works? https://github.com/rluzuriaga/fos/releases/tag/EXP_20250927

@Fog_Newb Yep, it’s as I suspected:

The Line:

Subsystem sftp /usr/lib/openssh/sftp-server

should be changed to:

Subsystem sftp internal-sftp

Then restart ssh services: systemctl restart sshd

Then your Storage Node testing should succeed!

My RP address was not pointing to my FOG server 🤦

Once this was adjusted, multicast is functional. Definitely a good reminder to start small.

I found the issue!

The udpsender path on my system was “/usr/sbin/udp-sender”

The path that is set within config.class.php is:

define('UDPSENDERPATH', '/usr/local/sbin/udp-sender');

I ran the following and restarted the FOGMulticastManager to resolve:

sudo ln -s /usr/sbin/udp-sender /usr/local/sbin/udp-sender

And we have logs now! Time to begin multicast testing 🥳

@rhysb92 We need more information.

i ask because I have just built a new VM, and installed dev-branch/stable and it completed and I was indeed able to login with the fog/password combination where i then changed the PW.

So I feel like we’re missing some key information.

All issues have been resolved by the latest kernel . Best regards, this thread can now be closed. Solved. 😉