Community discussions

MikroTik App
 
mahmudFatehi
just joined
Topic Author
Posts: 23
Joined: Mon Jul 01, 2024 6:06 pm

PIM-SM problem

Tue Jul 02, 2024 11:57 am

Hi guys,
I have a network like this.
Image
in R1 default gateway 30.42.0.1 and it has scr nat to 30.42.0.2 it has some dst nat based on my requirement.
in R3 default gateway 40.42.0.1 and it has scr nat to 40.42.0.2 it has some dst nat based on my requirement.
In R2 default gateway 10.42.0.1 it has scr nat to 10.42.0.2.
pc 1 and pc 2 are sender of multicast and pc 3 pc 4 are receiver.
because we have two upstream I think we can't use igmp proxy or mfc. instead i used PIM-SM in all routers. For all routers I created a new PIM-SM instance. and all interfaces were added to the interface template.
pc 3 and pc 4 didn't get traffic. I think it needs RP points. Which router is good in this scenario to be RP? and which interface of that router is good to be RP? Our group Ip is 224.1.1.1 and the address of RP is 30.42.0.1 but It didn't work. even other interfaces and other routers are selected as RP but it doesn't work.
please help me?
Thanks so much.
Last edited by tangent on Tue Jul 02, 2024 2:28 pm, edited 1 time in total.
Reason: Corrected protocol name in title and post (“pmism” → “PIM-SM”)
 
mahmudFatehi
just joined
Topic Author
Posts: 23
Joined: Mon Jul 01, 2024 6:06 pm

Re: PIM-SM problem

Sat Jul 06, 2024 7:49 am

Nobody can help ?
Does NAT make a problem ?
Does Router OS 7.14.2 have a problem?
Does my routing make a problem?
Thanks so much.
 
heberhardt
just joined
Posts: 5
Joined: Fri Oct 18, 2019 10:47 pm

Re: PIM-SM problem

Sat Jul 06, 2024 11:02 am

Hey,

without the configuration of the routers, it is not possible to completely understand where your issues come from.

But for the basics:
PIM does run on top of regular unicast routing, so it is recommended to have a properly configured routing protocol in your network. You can then configure a RP with an address that is redistributed from a loopback interface, for example. NAT is going to make multicast routing way more complicated or maybe even completely unfeasible.
The positioning of the RP in a network is fully dependent on the workload you are going to expect. The shared tree for multicast distribution is built with the RP as root. In a basic configuration every multicast group is initially transported to the RP and then forwarded along the shared-tree.

Moreover the multicast group IP you are using is part of a reserved block. This range should not be used by any application, because this block is reserved for future use. Please consult RFC 5771 and the IANA IPv4 Multicast Address Space Registry tables for valid usable multicast groups.

Until you provide more details and the configuration of the routers, there is nothing I can suggest.
 
mahmudFatehi
just joined
Topic Author
Posts: 23
Joined: Mon Jul 01, 2024 6:06 pm

Re: PIM-SM problem

Sun Jul 07, 2024 1:43 pm

Thanks for your attention
I found the problem.
My original problem is I have 4 pc behind nat(router is Mikrotik ) that are sender of multicast traffic.additionally I have 4 pc behind nat (router is Mikrotik ) that are receiver of multicast. So I need Nat because I don't want to use lots of Ip addresses. Right now 4 pc use one ip as external so i save Ip address. I need multicast because I don't want to send the same data multiple times to senders .Also all 4 PCs that send multicast data are sender so I think igmp proxy and MFC is not a good solution because they have just one upstream. I think Igmp snooping is not a good solution because I have Nat and routing and multi subnet ip addresses. I need PIM-SM. When I use src nat router that pimsm is configured on it does not find each other as neighbors. for example router 1 found that router 2 is its neighbor but router 2 can't find it. if we don't use src nat neighbor problem is solved but client behind nat they cant reach to RP Point. so How can we have sender and receiver multicast (both of them ) behind nat in mikrotik?
Thanks so much.
 
heberhardt
just joined
Posts: 5
Joined: Fri Oct 18, 2019 10:47 pm

Re: PIM-SM problem

Sun Jul 07, 2024 8:53 pm

My statement from yesterday still stands.
Until you share the configuration of the routers and think about a properly routed setup, there is nothing I can help with.
 
User avatar
tangent
Forum Guru
Forum Guru
Posts: 1669
Joined: Thu Jul 01, 2021 3:15 pm
Contact:

Re: PIM-SM problem

Sun Jul 07, 2024 9:29 pm

Why are you trying to save IP addresses? RFC1918 sets aside tens of millions of them for your use in applications like this.

Furthermore, PIM is designed to work in the presence of regular routing, not NAT.

Therefore, make these senders 10.0.0.1 thru 10.0.0.3, and then configure PIM to forward their multicast traffic to the 192 side of the network. Now you aren't burning 192-side IPs, and PIM works as designed.
 
mahmudFatehi
just joined
Topic Author
Posts: 23
Joined: Mon Jul 01, 2024 6:06 pm

Re: PIM-SM problem

Sun Aug 18, 2024 3:44 pm

Hi guys, when i add these config to mikrotik router
ip firewall nat add chain=srcnat action=accept protocol=pim router
that has pim on it can see each other but still can't send and receive multicast traffic all the time. sometimes it works well, sometimes it can't send and receive.
Thanks so much.
 
mahmudFatehi
just joined
Topic Author
Posts: 23
Joined: Mon Jul 01, 2024 6:06 pm

Re: PIM-SM problem

Mon Aug 26, 2024 11:12 am

Hi guys,
This is my R1, R2 and R3 router configuration.
R1 configuration
# 1970-01-02 12:29:02 by RouterOS 7.15.3
# software id = EH73-P2WC
#
# model = RB2011UiAS-2HnD
# serial number = 5E6A048BE09F
/port
set 0 name=serial0
/routing pimsm instance
add disabled=no name=pimsm-instance1 vrf=main
/ip address
add address=10.112.199.197/24 interface=ether7 network=10.112.199.0
add address=192.168.1.1/24 interface=ether1 network=192.168.1.0
add address=192.168.5.1/24 interface=ether5 network=192.168.5.0
add address=192.168.2.1/24 interface=ether2 network=192.168.2.0
add address=192.168.3.1/24 interface=ether3 network=192.168.3.0
add address=192.168.4.1/24 interface=ether4 network=192.168.4.0
add address=192.168.6.1/24 interface=ether6 network=192.168.6.0
/ip firewall nat
add action=accept chain=srcnat protocol=pim
add action=accept chain=srcnat protocol=igmp
add action=src-nat chain=srcnat to-addresses=10.112.199.197
add action=dst-nat chain=dstnat dst-port=32 in-interface=ether7 protocol=tcp \
    to-addresses=192.168.1.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=33 in-interface=ether7 protocol=tcp \
    to-addresses=192.168.2.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=34 in-interface=ether7 protocol=tcp \
    to-addresses=192.168.3.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=35 in-interface=ether7 protocol=tcp \
    to-addresses=192.168.4.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=8554 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.1.2 to-ports=8554
add action=dst-nat chain=dstnat dst-port=8555 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.2.2 to-ports=8554
add action=dst-nat chain=dstnat dst-port=8556 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.3.2 to-ports=8554
add action=dst-nat chain=dstnat dst-port=8557 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.4.2 to-ports=8554
    add action=dst-nat chain=dstnat dst-port=4196 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.2 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4197 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.3 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4198 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.4 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4199 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.5 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4200 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.6 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4201 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.7 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4202 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.8 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4203 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.9 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4204 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.10 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4205 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.11 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4206 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.12 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4207 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.13 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4208 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.14 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4209 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.15 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4210 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.16 to-ports=4196
add action=dst-nat chain=dstnat dst-port=4211 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.17 to-ports=4196
add action=dst-nat chain=dstnat dst-port=7000 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.1.2 to-ports=7000
add action=dst-nat chain=dstnat dst-port=9000 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.2 to-ports=80
add action=dst-nat chain=dstnat dst-port=9001 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.3 to-ports=80
add action=dst-nat chain=dstnat dst-port=9002 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.4 to-ports=80
add action=dst-nat chain=dstnat dst-port=9003 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.5 to-ports=80
add action=dst-nat chain=dstnat dst-port=9004 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.6 to-ports=80
add action=dst-nat chain=dstnat dst-port=9005 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.7 to-ports=80
add action=dst-nat chain=dstnat dst-port=9006 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.8 to-ports=80
add action=dst-nat chain=dstnat dst-port=9007 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.9 to-ports=80
add action=dst-nat chain=dstnat dst-port=9008 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.10 to-ports=80
add action=dst-nat chain=dstnat dst-port=9009 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.11 to-ports=80
add action=dst-nat chain=dstnat dst-port=9010 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.12 to-ports=80
add action=dst-nat chain=dstnat dst-port=9011 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.13 to-ports=80
add action=dst-nat chain=dstnat dst-port=9012 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.14 to-ports=80
add action=dst-nat chain=dstnat dst-port=9013 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.15 to-ports=80
add action=dst-nat chain=dstnat dst-port=9014 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.16 to-ports=80
add action=dst-nat chain=dstnat dst-port=9015 in-interface=ether7 protocol=\
    tcp to-addresses=192.168.5.17 to-ports=80
add action=dst-nat chain=dstnat dst-port=4000 in-interface=ether7 protocol=\
    udp to-addresses=192.168.6.2 to-ports=4000
add action=dst-nat chain=dstnat dst-port=1092 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.2 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1093 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.3 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1094 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.4 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1095 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.5 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1096 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.6 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1097 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.7 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1098 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.8 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1099 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.9 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1100 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.10 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1101 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.11 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1102 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.12 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1103 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.13 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1104 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.14 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1105 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.15 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1106 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.16 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1107 in-interface=ether7 protocol=\
    udp to-addresses=192.168.5.17 to-ports=1092
/ip route
add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=10.112.199.193 \
    pref-src="" routing-table=main suppress-hw-offload=no
/ip upnp
set allow-disable-external-interface=yes enabled=yes
/ip upnp interfaces
add interface=ether7 type=external
add interface=ether1 type=internal
add interface=ether2 type=internal
add interface=ether3 type=internal
add interface=ether4 type=internal
/routing pimsm interface-template
add disabled=no instance=pimsm-instance1 interfaces=\
    ether1,ether2,ether3,ether4,ether7
/routing pimsm static-rp
add address=10.112.136.245 instance=pimsm-instance1
/system note
set show-at-login=no
/tool sniffer
set file-limit=10KiB filter-interface=ether7 memory-limit=10000KiB \
    memory-scroll=no only-headers=yes streaming-server=0.0.0.0:tcpmux
    
    
    
    
    
R2 configuration 
# 1970-01-09 18:35:14 by RouterOS 7.15.3
# software id = 0I9P-TD9N
#
# model = L009UiGS
# serial number = HG509QE7T7E
/port
set 0 name=serial0
/routing pimsm instance
add disabled=no name=pimsm-instance1 vrf=main
/ip firewall connection tracking
set udp-timeout=10s
/ip address
add address=20.42.0.1/16 interface=ether3 network=20.42.0.0
add address=10.112.136.1/24 interface=ether1 network=10.112.136.0
add address=10.112.199.193/24 interface=ether2 network=10.112.199.0
add address=30.42.0.1/16 interface=ether4 network=30.42.0.0
/ip route
add disabled=no dst-address=10.42.0.0/16 gateway=20.42.0.2 routing-table=main suppress-hw-offload=no
/routing pimsm interface-template
add disabled=no instance=pimsm-instance1 interfaces=ether1,ether2,ether3,ether4
/routing pimsm static-rp
add address=10.112.136.245 instance=pimsm-instance1
/system note
set show-at-login=no
/system routerboard settings
set enter-setup-on=delete-key

    
    
    
R3 configuration 
# 1970-01-03 06:39:03 by RouterOS 7.15.3
# software id = 1X4C-P83B
#
# model = RB2011UiAS-2HnD
# serial number = 5E6A043EC5E4
/port
set 0 name=serial0
/routing pimsm instance
add disabled=no name=pimsm-instance1 vrf=main
/interface bridge settings
set use-ip-firewall=yes
/ip address
add address=10.112.136.245/24 interface=ether6 network=10.112.136.0
add address=192.168.2.1/24 interface=ether2 network=192.168.2.0
add address=192.168.3.1/24 interface=ether3 network=192.168.3.0
add address=192.168.4.1/24 interface=ether4 network=192.168.4.0
add address=192.168.5.1/24 interface=ether5 network=192.168.5.0
add address=192.168.1.1/24 interface=ether1 network=192.168.1.0
/ip firewall nat
add action=accept chain=srcnat protocol=pim
add action=accept chain=srcnat protocol=igmp
add action=src-nat chain=srcnat to-addresses=10.112.136.245
add action=dst-nat chain=dstnat dst-port=32 in-interface=ether6 protocol=tcp to-addresses=192.168.1.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=33 in-interface=ether6 protocol=tcp to-addresses=192.168.2.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=34 in-interface=ether6 protocol=tcp to-addresses=192.168.3.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=35 in-interface=ether6 protocol=tcp to-addresses=192.168.4.2 to-ports=22
add action=dst-nat chain=dstnat dst-port=7000 in-interface=ether6 protocol=tcp to-addresses=192.168.1.2 to-ports=7000
add action=dst-nat chain=dstnat dst-port=9000 in-interface=ether6 protocol=tcp to-addresses=192.168.5.2 to-ports=80
add action=dst-nat chain=dstnat dst-port=9001 in-interface=ether6 protocol=tcp to-addresses=192.168.5.3 to-ports=80
add action=dst-nat chain=dstnat dst-port=9002 in-interface=ether6 protocol=tcp to-addresses=192.168.5.4 to-ports=80
add action=dst-nat chain=dstnat dst-port=9003 in-interface=ether6 protocol=tcp to-addresses=192.168.5.5 to-ports=80
add action=dst-nat chain=dstnat dst-port=9004 in-interface=ether6 protocol=tcp to-addresses=192.168.5.6 to-ports=80
add action=dst-nat chain=dstnat dst-port=9005 in-interface=ether6 protocol=tcp to-addresses=192.168.5.7 to-ports=80
add action=dst-nat chain=dstnat dst-port=9006 in-interface=ether6 protocol=tcp to-addresses=192.168.5.8 to-ports=80
add action=dst-nat chain=dstnat dst-port=9007 in-interface=ether6 protocol=tcp to-addresses=192.168.5.9 to-ports=80
add action=dst-nat chain=dstnat dst-port=9008 in-interface=ether6 protocol=tcp to-addresses=192.168.5.10 to-ports=80
add action=dst-nat chain=dstnat dst-port=9009 in-interface=ether6 protocol=tcp to-addresses=192.168.5.11 to-ports=80
add action=dst-nat chain=dstnat dst-port=9010 in-interface=ether6 protocol=tcp to-addresses=192.168.5.12 to-ports=80
add action=dst-nat chain=dstnat dst-port=9011 in-interface=ether6 protocol=tcp to-addresses=192.168.5.13 to-ports=80
add action=dst-nat chain=dstnat dst-port=9012 in-interface=ether6 protocol=tcp to-addresses=192.168.5.14 to-ports=80
add action=dst-nat chain=dstnat dst-port=9013 in-interface=ether6 protocol=tcp to-addresses=192.168.5.15 to-ports=80
add action=dst-nat chain=dstnat dst-port=9014 in-interface=ether6 protocol=tcp to-addresses=192.168.5.16 to-ports=80
add action=dst-nat chain=dstnat dst-port=9015 in-interface=ether6 protocol=tcp to-addresses=192.168.5.17 to-ports=80
add action=dst-nat chain=dstnat dst-port=1092 in-interface=ether6 protocol=udp to-addresses=192.168.5.2 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1093 in-interface=ether6 protocol=udp to-addresses=192.168.5.3 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1094 in-interface=ether6 protocol=udp to-addresses=192.168.5.4 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1095 in-interface=ether6 protocol=udp to-addresses=192.168.5.5 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1096 in-interface=ether6 protocol=udp to-addresses=192.168.5.6 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1097 in-interface=ether6 protocol=udp to-addresses=192.168.5.7 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1098 in-interface=ether6 protocol=udp to-addresses=192.168.5.8 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1099 in-interface=ether6 protocol=udp to-addresses=192.168.5.9 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1100 in-interface=ether6 protocol=udp to-addresses=192.168.5.10 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1101 in-interface=ether6 protocol=udp to-addresses=192.168.5.11 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1102 in-interface=ether6 protocol=udp to-addresses=192.168.5.12 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1103 in-interface=ether6 protocol=udp to-addresses=192.168.5.13 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1104 in-interface=ether6 protocol=udp to-addresses=192.168.5.14 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1105 in-interface=ether6 protocol=udp to-addresses=192.168.5.15 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1106 in-interface=ether6 protocol=udp to-addresses=192.168.5.16 to-ports=1092
add action=dst-nat chain=dstnat dst-port=1107 in-interface=ether6 protocol=udp to-addresses=192.168.5.17 to-ports=1092
/ip route
add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=10.112.136.1 pref-src="" routing-table=main suppress-hw-offload=no
add disabled=yes distance=1 dst-address=0.0.0.0/0 gateway=30.42.0.2 pref-src="" routing-table=main scope=30 suppress-hw-offload=no target-scope=10
/ip upnp
set allow-disable-external-interface=yes enabled=yes
/ip upnp interfaces
add interface=ether6 type=external
add interface=ether1 type=internal
add interface=ether2 type=internal
add interface=ether3 type=internal
add interface=ether4 type=internal
/routing pimsm interface-template
add disabled=no instance=pimsm-instance1 interfaces=ether1,ether2,ether3,ether4,ether6
/routing pimsm static-rp
add address=10.112.136.245 disabled=no instance=pimsm-instance1
/system note
set show-at-login=no
/tool sniffer
set filter-interface=ether6
    
    
    
    
    
    
    
    




My problem is I can't send and receive multicast traffic from R1 to R3 all the time. sometimes it works correctly and sometimes it doesn't work. all R1 R2 R3 can see each other as PIM-SM neighbors but it doesn't work properly.
Thanks so much.
 
mahmudFatehi
just joined
Topic Author
Posts: 23
Joined: Mon Jul 01, 2024 6:06 pm

Re: PIM-SM problem

Sat Sep 07, 2024 8:57 am

I'd appreciate it if anybody could help me ?
If we have a router that has one interface as external and some internal interface that are connected to PC that send multicast data, pc s are behind nat I want use PIM-SM I configure src nat and Pim protocol and if i set
ip firewall nat add action=accept chain=srcnat protocol=pim
routers interface with pim enable can see each other but if I don't set these configuration router interface with pim enable can't see each other properly because of nat. actually I have another router with one interface as external and other as internal with nat and pc behind nat for receive multicast data the same as sender. Sometimes it works properly and can send and receive multicast data but sometimes it doesn't work. I have to use multicast for sender and receiver because multiple receivers receive the same data ? I have to use Nat because multiple PCs ( sender or receiver of multicast data ) with local ip must have one public IP ( I don't mean public internet IP I mean translate IP from private IP to other private IP for example translate from 192.168.0.0 to 10.42.0.0) in my network. The sender and receiver are not in the same subnet so I need to use a router. How ever does PIM work in a scenario? is it complex or infeasible? If it is complex, can you help me ? another solution like IGMP proxy ?
Thanks so much.
 
maimbo
just joined
Posts: 3
Joined: Sat Dec 07, 2024 8:15 am

Re: PIM-SM problem

Sat Jan 11, 2025 1:59 am

The way I see it, this architecture resembles two customers using NAT to connect to an ISP, where R1 and R3 are the CPE routers and R2 is the ISP router? If I've got that right, then IMHO the simplest solution would be to use IGMP Proxy on R1 and R3, and PIM-SM on R2?