Date: Fri, 8 Nov 2019 15:22:09 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Victor Gamov <vit@otcnet.ru>, mike@karels.net Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD as multicast router Message-ID: <53d53fa7-5bd3-e710-facf-66b03b01b014@grosbein.net> In-Reply-To: <3334fa50-8a88-17b6-7e91-c09d22e11f7e@otcnet.ru> References: <201911060241.xA62fd40065707@mail.karels.net> <3334fa50-8a88-17b6-7e91-c09d22e11f7e@otcnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
07.11.2019 21:17, Victor Gamov wrote: > I still have misunderstood here. Pimd installs multicast routes and this routes displayed by `netstat -g`. > So, the system knows interface where multicast received. > When Join received via interface 2 (vlan299) who must resend multicast from input interface 3 (vlan750) > to output interface 2 (vlan299)? I guess it kernel-specific task and kernel must resend multicast > without any other helpers. Is it wrong? 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53d53fa7-5bd3-e710-facf-66b03b01b014>