From owner-freebsd-ipfw@freebsd.org Sun Mar 18 03:00:51 2018 Return-Path: Delivered-To: freebsd-ipfw@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 CA385F594F0 for ; Sun, 18 Mar 2018 03:00:51 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67DFB7A4F7 for ; Sun, 18 Mar 2018 03:00:51 +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 B3BEF12ECC for ; Sun, 18 Mar 2018 03:00:50 +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 w2I30o7g093875 for ; Sun, 18 Mar 2018 03:00:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2I30ouO093867 for freebsd-ipfw@FreeBSD.org; Sun, 18 Mar 2018 03:00:50 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: freebsd-ipfw@FreeBSD.org Subject: [Bug 226688] [ipfw] rejects adding 255.255.255.255 to a table Date: Sun, 18 Mar 2018 03:00:50 +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: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ipfw@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-ipfw@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2018 03:00:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226688 --- Comment #4 from Rodney W. Grimes --- 255.255.255.255 is a special broadcast IP addresses used to broadcast on "t= his network". That is not applicable in this case though. BUT 255.255.255.255 should be a perfectly valid table entry for the reasons= the submitter stated. If for some odd reason someone got this IP on the wire y= ou would want ipfw to filter it out. As a workaround you could use 255.255.255.254/31, this is pretty safe as: 240.0.0.0/4 is "reserved". Which you could also use to block this, and if your trying to block bad addresses you should block 240/4 anyway. I am not sure how much effort it is worth trying to fix this. And now that I see: ${fwcmd} table ${BAD_ADDR_TBL} add 240.0.0.0/4 is already in /etc/rc.firewall which would include 255.255.255.255 this bug could be closed as "to hard to fix" --=20 You are receiving this mail because: You are the assignee for the bug.=