From owner-freebsd-net@freebsd.org Fri Feb 22 04:31:50 2019 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23B4314FF1A3 for ; Fri, 22 Feb 2019 04:31:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AC02680C79 for ; Fri, 22 Feb 2019 04:31:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7019B14FF1A2; Fri, 22 Feb 2019 04:31:49 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B33B14FF1A1 for ; Fri, 22 Feb 2019 04:31:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7AEA80C74 for ; Fri, 22 Feb 2019 04:31:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 081C439E8 for ; Fri, 22 Feb 2019 04:31:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x1M4VlJQ024497 for ; Fri, 22 Feb 2019 04:31:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x1M4VlnZ024488 for net@FreeBSD.org; Fri, 22 Feb 2019 04:31:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 235927] FreeBSD does not reply to ICMP requests when assigned an ip in 240.0.0.0/8 Date: Fri, 22 Feb 2019 04:31:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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, 22 Feb 2019 04:31:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235927 --- Comment #7 from Rodney W. Grimes --- (In reply to Loganaden Velvindron from comment #6) >Linux has already accepted a patch to allow assignment of 240.0.0.0/4: >https://www.spinics.net/lists/netdev/msg540240.html This patch appears to fix very ancient code that still treated this as part of the multicast space. The patches also add use of language (ClassE) that was obsoleted 16 years ago.=20=20 https://www.spinics.net/lists/netdev/msg539064.html is the correct reference to the message with the patch in it. >OpenWRT (major third party firmware) has accepted a similar patch: This is inline with what your asking for here. >A new ID will be submitted to the IETF soon. A new ID for what? Do you mean removing this from IANA reserved? >Please note that there were some attempts in the past in the IETF already: >https://tools.ietf.org/html/draft-fuller-240space-02 A 2007 attempt by Cisco, have you considered contact them about moving forw= ard with that draft? As it stands today the RFC say this is an invalid source address, so we sho= uld continue to respect those standards in a standard released product, however= I would not have a problem with #ifdef FOO_EXPERMINTAL disabling these restrictions, or a sysctl that did it. There are some much larger obsticles to getting this working on the interne= t at a larger scale, in that there are far too many firewalls that filter this range, and getting it out of them is going to take a long time. That time = wont even start until they are reclassed by IANA with an update to RFC6890 and y= ou would probably best get that done as it is the long lead show stopper to th= is idea. Getting FreeBSD, Linux and such fixed is pointless if people are goi= ng to continue to firewall this range. --=20 You are receiving this mail because: You are the assignee for the bug.=