Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trying to send Multicast data to/from Pod fails #1352

Open
adt47 opened this issue Nov 4, 2024 · 3 comments
Open

Trying to send Multicast data to/from Pod fails #1352

adt47 opened this issue Nov 4, 2024 · 3 comments

Comments

@adt47
Copy link

adt47 commented Nov 4, 2024

I have a deployment setup running across multiple Proxmox VMs each running a K3S cluster. One of the VMs has a Docker container running a simulator for sending data to the clusters. Each Cluster consists of a single node with 6 pods and 6 services as viewed in the attached image. One of the pods (pod 6) needs to communicate with it's counterparts on the other nodes via multicast (represented by the blue line).
image
I am using Flannel and Multus to accomplish this. I created the following Network Attachment Definition
image
and I added this annotation to my pods, with different IPs and MAC addresses on each pod of course.
image
With this setup I can exec into one of the pods and ping the other pods and VMs, but using IPERF to test Multicast fails.
Here is the command and output for starting the Multicast subscriber:
image
and the publisher :
image

It appears that the problem is that the publisher is defaulting to the internal Flannel network (10.42.0.186) instead of the network I attached. I do not know how to fix this.

Note: I did try doing this without Multus and just using "hostNetwork: true" in my pod which did allow me to send multicast data between the pods. But the side effect was that the comms from the Docker container to the attached SVC 6 no longer works. If I could figure out how to get the data directly to the pod without the service, this might also solve my problem, though I would prefer to go the Multus route.

Any assistance would be appreciated.

@gytisgreitai
Copy link

did you ever resolve this?

@adt47
Copy link
Author

adt47 commented Jan 6, 2025

did you ever resolve this?

I have not, either no one has stumbled upon my queries, or no one cares/knows how to fix the problem.

@gytisgreitai
Copy link

Adding explicit multicast routing to ipam routes definition fixed multicast for me: "routes": [ { "dst": "224.0.0.0/4" }]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants