Date: Wed, 30 Jan 2013 11:14:55 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-net@freebsd.org Subject: Re: [PATCH] Allow tcpdrop to use non-space separators Message-ID: <201301301114.55770.jhb@freebsd.org> In-Reply-To: <20130129231042.52622.qmail@f5-external.bushwire.net> References: <201301291205.41301.jhb@freebsd.org> <20130129231042.52622.qmail@f5-external.bushwire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, January 29, 2013 6:10:42 pm Mark Delany wrote: > 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. I'm not aware of any of the tools in the base system at least that use that convention, so in terms of the original goal of making it easier to cut and paste from the output of one program to the parameters to tcpdrop I don't think it fits. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201301301114.55770.jhb>