Multicasting Stuck on Partclone Screen

[christop]

Hello everyone,

I’m back with more multicasting issues. When I attempt to multicast the task starts, but on the client end, they are left sitting at the first partclone screen after listing the image.

On the networking side, we intend on using 3 VLANS but I have kept it all on the same VLAN to get the initial test working before complicating things.

I am on Ubuntu 24.04 and FOG v 1.5.10.1719

We have the following setup in regards to networking:

1. Option 66 + 67 (Unicast is confirmed working, and it boots successfully
2. IGMP snooping enabled
3. PIM (SM)
4. RP

I have also followed the steps to test multicast manually with the udp-sender and udp-receiver commands and that is working within the same VLAN and outside.

If anyone has any suggestions I would really appreciate it. I understand this is a common issue judging by similar forum posts but I was unable to find a resolution from past posts.

When I start the task the log has the following:```
[09-24-25 5:53:03 am] * No new tasks found
[09-24-25 5:53:13 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup is new
[09-24-25 5:53:13 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup image file found, file: /images/Win11
[09-24-25 5:53:13 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup 1 client found
[09-24-25 5:53:13 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup sending on base port 64622
[09-24-25 5:53:13 am] | Command: /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 240 --mcast-rdv-address 192.168.77.254 --portbase 64622 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/Win11/d1p1.img;/usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 24 --mcast-rdv-address 192.168.77.254 --portbase 64622 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/Win11/d1p2.img;/usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 24 --mcast-rdv-address 192.168.77.254 --portbase 64622 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/Win11/d1p3.img;/usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 24 --mcast-rdv-address 192.168.77.254 --portbase 64622 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/Win11/d1p4.img;
[09-24-25 5:53:13 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup has started
[09-24-25 5:53:23 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup is already running with pid: 3753
[09-24-25 5:53:33 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup is already running with pid: 3753
[09-24-25 5:53:43 am] | Task ID: 16 Name: Multicast Quick Deploy - testGroup is already running with pid: 3753

I've attached an image of my multicast settings within FOG.
![multicastFogSettings.jpeg](/assets/uploads/files/1758694967352-multicastfogsettings.jpeg)
(/assets/uploads/files/1758695329020-f2dd9e34-65e5-4700-a710-70a0a7ae7b5d-multicastfogsettings.jpeg)

[christop]

My RP address was not pointing to my FOG server

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

[christop]

I see that the images did not load so I uploaded my multicast settings to imgur.
https://imgur.com/EU7FOkm

Also wanted to note no ports are being blocked within the VLAN.

I’ll continue troubleshooting but appreciate anyone’s 2 cents on this.

[christop]

I was able to create a multicast task from the FOG server, and while the main client was stuck in the partclone screen, I was able to launch another client on the same VLAN in debug mode and run “udp-receiver --portbase <PORT FROM LOGS>” and it was receiving the stream of traffic and showed up in the ‘multicast.log.udpcast’ logs.

This makes me curious as to what udp-receiver command the client is running when booting into partclone as it never joins the session and just sits at that screen indefinitely.

[christop]

My RP address was not pointing to my FOG server

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