From owner-freebsd-net@FreeBSD.ORG Tue Jan 29 23:17:24 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6AC5BC05 for ; Tue, 29 Jan 2013 23:17:24 +0000 (UTC) (envelope-from markd-freebsd-net@bushwire.net) Received: from smtp1.bushwire.net (f5.bushwire.net [199.48.133.46]) by mx1.freebsd.org (Postfix) with SMTP id 204FDE96 for ; Tue, 29 Jan 2013 23:17:23 +0000 (UTC) Received: (qmail 52630 invoked by uid 1001); 29 Jan 2013 23:10:42 -0000 Delivered-To: qmda-intercept-freebsd-net@freebsd.org DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=2004; d=bushwire.net; b=Q5CaabxSi4mu60j3JxQJk6ptknc35QmrJxEMqRjxpI18gKOGF8MR7FyB2F4IJGRx; Comments: DomainKeys? See http://en.wikipedia.org/wiki/DomainKeys DomainKey-Trace-MD: h=12; b=14; l=C18R71D32M65F52T27S62R48M17C39C27I49; Comments: QMDA 0.3 Received: (qmail 52623 invoked by uid 1001); 29 Jan 2013 23:10:42 -0000 Date: 29 Jan 2013 23:10:42 +0000 Message-ID: <20130129231042.52622.qmail@f5-external.bushwire.net> From: "Mark Delany" To: freebsd-net@freebsd.org Subject: Re: [PATCH] Allow tcpdrop to use non-space separators References: <201301291205.41301.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <201301291205.41301.jhb@freebsd.org> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 29 Jan 2013 23:17:24 -0000 On 29Jan13, John Baldwin allegedly wrote: > A common use case I have at work is to find a busted connection using netstat > -n or sockstat and then want to tcpdrop it. However, tcpdrop requires spaces > between the address and port so I can't simply cut and paste from one terminal > window into another to generate the tcpdrop command. This patch adds support > for having a decimal (netstat output) or colon (sockstat output) Any thoughts on including '#' as a valid port delimiter? this is mentioned in http://tools.ietf.org/html/rfc5952 Section 6 as an (albeit lowly) option and it does have the benefit of avoiding both of the ip4v/v6 delimiters. Mark.