Multicast

Just don't get why some of my posts have to wait to be approved and some don't.

The post with the output of iptables -S is still waiting to be approved (Cleared my ssh session)

With the input table flushed I am still not seeing multicast traffic.

root@proxmox2:~# asmping 224.0.2.1 10.211.47.1
asmping joined (S,G) = (*,224.0.2.234)
pinging 10.211.47.1 from 10.211.47.2
unicast from 10.211.47.1, seq=1 dist=0 time=0.274 ms
unicast from 10.211.47.1, seq=2 dist=0 time=0.228 ms
unicast from 10.211.47.1, seq=3 dist=0 time=0.201 ms
unicast from 10.211.47.1, seq=4 dist=0 time=0.221 ms
unicast from 10.211.47.1, seq=5 dist=0 time=0.211 ms

- - - Updated - - -

Just don't get why some of my posts have to wait to be approved and some don't.

The post with the output of iptables -S is still waiting to be approved (Cleared my ssh session)

With the input table flushed I am still not seeing multicast traffic.

Really appreciate the help mir!
 
Last edited:
I was getting this message also and the main point I was missing is the fact that you must run omping on each node individually. I missed that part of the picture. Basically you run the command with the IP address of each node. So you run the identical command from separate SSH sessions on each server. The first sessions starts listening for the each node to join. Then when all nodes are accounted for the multicast begins.

EXAMPLE: (run the same exact command on each node at the same time)
root@pve1:~# omping -c 10000 -i 0.001 -F -q 10.17.17.31 10.17.17.32 10.17.17.33
10.17.17.32 : waiting for response msg
10.17.17.33 : waiting for response msg
10.17.17.32 : waiting for response msg
10.17.17.33 : waiting for response msg
10.17.17.32 : waiting for response msg
10.17.17.33 : waiting for response msg
10.17.17.32 : waiting for response msg
10.17.17.33 : waiting for response msg
10.17.17.32 : waiting for response msg
10.17.17.33 : waiting for response msg
10.17.17.32 : joined (S,G) = (*, 232.43.211.234), pinging
10.17.17.33 : waiting for response msg
10.17.17.33 : waiting for response msg
10.17.17.33 : joined (S,G) = (*, 232.43.211.234), pinging
10.17.17.32 : given amount of query messages was sent
10.17.17.33 : given amount of query messages was sent

10.17.17.32 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.048/0.102/0.258/0.029
10.17.17.32 : multicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.050/0.110/0.284/0.031
10.17.17.33 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.048/0.119/0.261/0.035
10.17.17.33 : multicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.052/0.130/0.268/0.037
 
Appreciate the input. Results don't look much better. Still looks like multicast is broke, but it obviously is working.

Maybe try the command using just IP addresses but make sure you run the same command on each node at the same time so they see each other. Looks like one node used hostnames and the other used IP addresses. Maybe hosts file or DNS not working.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!