Why pim_mroute_msg_nocache fuc dont receive incoming packet that doesn't originate on our seg ?

[witt84]

2023/02/21 16:34:42 PIM: [ZAER8-BYQAT] pim_mroute_msg: pim kernel upcall NOCACHE type=1 ip_p=0 from fd=9 for (S,G)=(192.168.110.2,225.0.0.10) on br-wan vifi=2 size=28
2023/02/21 16:34:42 PIM: [MCW79-K545J] Lookedup: 0x7f917c6340 for rp_info: 0x7f9181fa60(224.0.0.0/4) Lock: 3
2023/02/21 16:34:42 PIM: [H8G8R-SHK6F] pim_rp_g: NHT Register RP addr 192.168.11.3/32 grp 224.0.0.0/4 with Zebra
2023/02/21 16:34:42 PIM: [HWBEV-9D9K2] pim_rpf_set_refresh_time: vrf(default) New last route change time: 1676968482919318
2023/02/21 16:34:42 PIM: [QCZ5P-RQFQQ] pim_ecmp_nexthop_lookup: Looking up: 192.168.11.3(default), last lookup time: 1676967600313297
2023/02/21 16:34:42 PIM: [VKDZ4-H8FEM] pim_ecmp_nexthop_search: (192.168.11.3,224.0.0.0)(default) current nexthop br-wan is valid, skipping new path selection
2023/02/21 16:34:42 PIM: [QVA6D-BZ075] pim_mroute_msg_nocache: Received incoming packet that doesn't originate on our seg

[donaldsharp]

Pim received a S,G message from the kernel that it does not believe originated on the segment that the interface is attached to. Accordingly PIM drops it as specified by the rfc