Date: Fri, 8 Nov 2019 17:01:28 +0300 From: Victor Gamov <vit@otcnet.ru> To: Eugene Grosbein <eugen@grosbein.net>, mike@karels.net Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD as multicast router Message-ID: <e4821ad3-bf74-bca7-eaa2-72a979820237@otcnet.ru> In-Reply-To: <b7044779-24d9-a417-b846-571361778565@grosbein.net> References: <201911060241.xA62fd40065707@mail.karels.net> <3334fa50-8a88-17b6-7e91-c09d22e11f7e@otcnet.ru> <53d53fa7-5bd3-e710-facf-66b03b01b014@grosbein.net> <b812fa55-e4ea-6006-af8f-b61199c2a8bd@otcnet.ru> <b7044779-24d9-a417-b846-571361778565@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/11/2019 16:47, Eugene Grosbein wrote: > 08.11.2019 19:10, Victor Gamov wrote: > >>> I'm not familiar with multicast routing in FreeBSD. >>> Multicast routing has its rules in general, though. >>> >>> For example, Cisco routers never process incoming multicast UDP flows if unicast route >>> to source IP address of UDP packets points to interface that differs from real incoming interface. >>> This is "reverse path filtering" embedded in multicast routing unconditionally. >> >> Yes, but FreeBSD can ping source and client in my tests (see my new later at this thread with network scheme) > > It does not matter if source is reachable with unicasts (ping). "Reverse" unicast routes should match incoming interface for multicast UDP. My network scheme is simplest: ---------- -------------------- ----------- | source |-vlan750-| FreeBSD PIM router |-vlan299-| client | |200.5/29| |200.6/29 199.102/30| |199.101/30| ---------- -------------------- ----------- All multicasts comes from 200.5 with 200.5 as source IP. So I hope RPF check passes for FreeBSD. -- CU, Victor Gamov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e4821ad3-bf74-bca7-eaa2-72a979820237>