From owner-freebsd-net@freebsd.org Fri Nov 8 14:01:31 2019 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5BFCB1B34ED for ; Fri, 8 Nov 2019 14:01:31 +0000 (UTC) (envelope-from vit@otcnet.ru) Received: from mail.otcnet.ru (mail.otcnet.ru [194.190.78.3]) by mx1.freebsd.org (Postfix) with ESMTP id 478hlG4BW7z4P2X for ; Fri, 8 Nov 2019 14:01:30 +0000 (UTC) (envelope-from vit@otcnet.ru) Received: from MacBook-Gamov.local (unknown [194.190.78.9]) by mail.otcnet.ru (Postfix) with ESMTPSA id B5A5473A0A; Fri, 8 Nov 2019 17:01:28 +0300 (MSK) Subject: Re: FreeBSD as multicast router To: Eugene Grosbein , mike@karels.net Cc: freebsd-net@freebsd.org References: <201911060241.xA62fd40065707@mail.karels.net> <3334fa50-8a88-17b6-7e91-c09d22e11f7e@otcnet.ru> <53d53fa7-5bd3-e710-facf-66b03b01b014@grosbein.net> From: Victor Gamov Organization: OstankinoTelecom Message-ID: Date: Fri, 8 Nov 2019 17:01:28 +0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 478hlG4BW7z4P2X X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of vit@otcnet.ru designates 194.190.78.3 as permitted sender) smtp.mailfrom=vit@otcnet.ru X-Spamd-Result: default: False [-5.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.otcnet.ru:c]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[otcnet.ru]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; HAS_ORG_HEADER(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(-3.28)[ip: (-8.63), ipnet: 194.190.78.0/24(-4.31), asn: 50822(-3.45), country: RU(0.01)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:50822, ipnet:194.190.78.0/24, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Nov 2019 14:01:31 -0000 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