I'm playing with UDP multicast and I've come across a strange situation where I can't understand what's happening.
Here is the scenario:
The machines are on a network made up of 3 TP-Link Deco XE75 (forming a mesh) and several switches.
Deco #1 is the main element and it is wired to the WAN.
It is also wired to a switch that, in turn, is wired to Deco #2, Deco #3 and 192.168.68.200.
192.168.68.61 is connected via WiFi to Deco #2.
Physical machine 192.168.68.61
- bind: 0.0.0.0:1234
- join: 224.0.1.187 (IGMP confirmed by netsh and wireshark)
- join: 239.0.0.1 (IGMP confirmed by netsh and wireshark)
Physical machine 192.168.68.200
- bind: 0.0.0.0:12345
- join: 224.0.1.187 (IGMP confirmed by netsh and wireshark)
- join: 239.0.0.1 (IGMP confirmed by netsh and wireshark)
This is what happens:
- message A (source: 192.168.68.61:1234 - target: 224.0.1.187:12345)
NOT RECEIVED by 192.168.68.200 (not present even on Wireshark) - message B (source: 192.168.68.61:1234 - target: 239.0.0.1:12345)
RECEIVED by 192.168.68.200 - message C (source: 192.168.68.200:12345 - target: 224.0.1.187:1234)
RECEIVED by 192.168.68.61 - message D (source: 192.168.68.200:12345 - target: 239.0.0.1:1234)
RECEIVED by 192.168.68.61
The only message that is not received is the message A
Here are some screens (messages A and B):
Maybe is the Deco mesh blocking multicast one way only and for a specific group only?