From owner-freebsd-net@freebsd.org Tue Sep 15 13:51:14 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B34E0A04FA8 for ; Tue, 15 Sep 2015 13:51:14 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 733311C68 for ; Tue, 15 Sep 2015 13:51:14 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id t8FDpCZn008637 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 15 Sep 2015 07:51:12 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id t8FDpBbj008634; Tue, 15 Sep 2015 07:51:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 15 Sep 2015 07:51:11 -0600 (MDT) From: Warren Block To: Ian Smith cc: "O. Hartmann" , Kimmo Paasiala , freebsd-net@freebsd.org Subject: Re: HELP! Mysterious socket 843/tcp listening on CURRENT system In-Reply-To: <20150915201451.L90924@sola.nimnet.asn.au> Message-ID: References: <20150915090658.1e0b9074@freyja.zeit4.iv.bundesimmobilien.de> <20150915094757.3daef42c@freyja.zeit4.iv.bundesimmobilien.de> <20150915201451.L90924@sola.nimnet.asn.au> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 15 Sep 2015 07:51:12 -0600 (MDT) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 13:51:14 -0000 On Tue, 15 Sep 2015, Ian Smith wrote: > > But that is an other issue and it is most likely > > due to the outdated documentation (that doc still uses port 37 for NTP > > purposes and referes to the outdated divert mechanism using natd, see the > > recent handbook). The internet is also full of ambigous examples. > > Yes, the handbook IPFW section is still crazy after all these years, > despite ongoing attempts to limit the damage. Best just ignore it. Best overall would be to fix the documentation. Given that there seems to be more interest in IPFW lately, it would be nice if someone well-versed in it would repair or even rewrite the IPFW handbook section. Rewrites are sometimes less work than fixing an old section that no longer fits actual usage. I have not used IPFW in years, but would be willing to help with an edit/rewrite.