03-10-2024 09:43 AM
Hi, i hope its right post location for this kind of problem.
I tried to send unicast data with PacketSender to Socat(Debian 12 Server), convert that to Multicast and send that data to Cisco multicast interface/group.
When i try do send Multicast data with MCastTest it will work, MCastTest receiver 1 and 2 will get the data.
When i try do send data with Socat over Cisco router, data don't go to MCastTest 1, it will go to MCastTest 2.
Unicast ping works all-around.
MCastTest - https://www.dqnetworks.ie/toolsinfo/mcasttest/
When i send data with MCastTest, it will go to McastTest receiver 1 and 2.
When i tried to send UDP data with PacketSender to Socat, convert it and send it to MCastTest 1 and 2. Only MCastTest 2 receives data.
I can see that Socat sends multicast out from e0 192.168.10.2 (Interface towards Cisco Router, Cisco R1 f0/0 192.168.10.254).
Test 1:
Multicast to McastTest Receiver 1
socat -d -d UDP4-RECV:8006, bind=192.168.10.2 UDP4-DATAGRAM:229.1.1.1:8002, bind=192.168.10.2,reuseaddr
Test 2:
Multicast to McastTest Receiver 2 works!
socat -d -d UDP4-RECV:8006, bind=192.168.10.2 UDP4-DATAGRAM:229.1.1.1:8002, bind=10.10.20.2,reuseaddr**
----------
R1
ip multicast-routing
interface FastEthernet0/0
ip address 192.168.10.254 255.255.255.0
ip pim sparse-dense-mode
ip igmp join-group 229.1.1.1
duplex half
!
interface FastEthernet1/0
ip address 172.21.0.1 255.255.255.0
ip pim sparse-dense-mode
duplex auto
speed auto
ip mroute 10.10.10.0 255.255.255.0 172.21.0.2
ip route 10.10.10.0 255.255.255.0 172.21.0.2
----------
R2
ip multicast-routing
interface FastEthernet0/0
ip address 10.10.10.254 255.255.255.0
ip pim sparse-dense-mode
ip igmp join-group 229.1.1.1
duplex half
!
interface FastEthernet1/0
ip address 172.21.0.2 255.255.255.0
ip pim sparse-dense-mode
duplex auto
speed auto
ip route 192.168.10.0 255.255.255.0 172.21.0.1
ip mroute 192.168.10.0 255.255.255.0 172.21.0.1
Solved! Go to Solution.
03-10-2024 10:32 AM
Hi @techteching8 ,
It might be due to the TTL value being used by socat by default. Try increasing it using the ip-multicast-ttl parameter.
Regards,
03-10-2024 10:32 AM
Hi @techteching8 ,
It might be due to the TTL value being used by socat by default. Try increasing it using the ip-multicast-ttl parameter.
Regards,
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide