Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    13k Topics
    115k Posts
    K

    @Tom-Elliott
    Multicast
    cb765515-1c91-406f-bac6-c30fd8dca2e3-grafik.png
    7d927a7b-ff64-4544-bdc1-f166768eeb5c-grafik.png
    deee65ea-e430-40ff-b5e9-732fd60bf0de-grafik.png WhatsApp Image 2026-09-22 at 10.31.53(1).jpeg WhatsApp Image 2026-09-22 at 10.31.53.jpeg

    root@fog:~/FOG_SERVER_Updates_durchführen# tail -n 40 /opt/fog/log/multicast.log [09-08-26 9:49:42 pm] * No new tasks found [09-08-26 9:49:52 pm] * No new tasks found [09-08-26 9:50:02 pm] * No new tasks found [09-08-26 9:50:12 pm] * No new tasks found [09-08-26 9:50:22 pm] * No new tasks found [09-08-26 9:50:32 pm] * No new tasks found [09-08-26 9:50:42 pm] * No new tasks found [09-08-26 9:50:52 pm] * No new tasks found [09-08-26 9:51:02 pm] * No new tasks found [09-08-26 9:51:12 pm] * No new tasks found [09-08-26 9:51:22 pm] * No new tasks found [09-08-26 9:51:32 pm] * No new tasks found [09-08-26 9:51:42 pm] * No new tasks found [09-08-26 9:51:52 pm] * No new tasks found [09-08-26 9:52:02 pm] * No new tasks found [09-08-26 9:52:12 pm] * No new tasks found [09-08-26 9:56:33 pm] ===== FOG 1.5.10.2473 -- MulticastManager starting ===== [09-08-26 9:56:33 pm] Interface Ready with IP Address: 10.10.3.196 [09-08-26 9:56:33 pm] Interface Ready with IP Address: 127.0.0.1 [09-08-26 9:56:33 pm] Interface Ready with IP Address: 127.0.1.1 [09-08-26 9:56:33 pm] Interface Ready with IP Address: 192.168.0.196 [09-08-26 9:56:33 pm] * Starting MulticastManager Service [09-08-26 9:56:33 pm] * Checking for new items every 10 seconds [09-08-26 9:56:33 pm] * Starting service loop [09-08-26 10:00:14 pm] ===== FOG 1.5.10.2473 -- MulticastManager starting ===== [09-08-26 10:00:14 pm] Interface Ready with IP Address: 10.10.3.196 [09-08-26 10:00:14 pm] Interface Ready with IP Address: 127.0.0.1 [09-08-26 10:00:14 pm] Interface Ready with IP Address: 127.0.1.1 [09-08-26 10:00:14 pm] Interface Ready with IP Address: 192.168.0.196 [09-08-26 10:00:14 pm] * Starting MulticastManager Service [09-08-26 10:00:14 pm] * Checking for new items every 10 seconds [09-08-26 10:00:14 pm] * Starting service loop [09-08-26 10:08:36 pm] ===== FOG 1.5.10.2473 -- MulticastManager starting ===== [09-08-26 10:08:36 pm] Interface Ready with IP Address: 10.10.3.196 [09-08-26 10:08:36 pm] Interface Ready with IP Address: 127.0.0.1 [09-08-26 10:08:36 pm] Interface Ready with IP Address: 127.0.1.1 [09-08-26 10:08:36 pm] Interface Ready with IP Address: 192.168.0.196 [09-08-26 10:08:36 pm] * Starting MulticastManager Service [09-08-26 10:08:36 pm] * Checking for new items every 10 seconds [09-08-26 10:08:36 pm] * Starting service loop root@fog:~/FOG_SERVER_Updates_durchführen#

    I use two network cards—the “192” network is the one with the PCs, and the “10” network contains only servers and my backup servers …

  • Get the latest news on what's happening.
    Security Advisories
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    General Tutorials
    2k Topics
    19k Posts
    R

    Now I read the AI summary and got what I need:

    It stores one row for each address in the hostNetwork table. Limits of this method The sleeping host must run fog-agent. The server uses the sleeping host’s own last report to find its subnet. A host with the legacy FOG Client, or with no client, has no rows, so the relay cannot help it. The old path still runs for it.

    So If I populate the hostNetwork table for the hosts that I need manually, It will work. Thank you for the details.

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    Tom ElliottT

    @servicedesk-pianezza Confirmed, and your fix is the right one. Thanks for the clear report.

    The check was using the 24-character Base24 alphabet. That set is what you use to decode an older key into its binary form, and N is not one of its digits. It is not the set of characters a key is printed with. Windows 8 and later put N in the key itself, so any key carrying one was refused at entry.

    There was a second half of the same bug. The browser keeps its own copy of that character list, for the masked display of a saved key. So even where a key with an N got stored, the page showed it as five groups of dots instead of keeping the first and last group. Both copies now say the same thing, and a test compares them character for character so they cannot drift apart again.

    The test also runs Microsoft’s published KMS client keys through the validator, and checks that the characters Windows leaves out (A E I O U L S Z 0 1) are still rejected and the length is still exactly 25.

    It is in PR #1773 against working-1.6: https://github.com/FOGProject/fogproject/pull/1773

    It will be in the next beta build. If you would rather not wait, the one-character edit you already made is exactly what landed.

70

Online

12.8k

Users

17.6k

Topics

157.1k

Posts