From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonas Berlin Subject: Re: [PATCH] goto port to ipv6 Date: Mon, 18 Apr 2005 06:28:08 +0000 Message-ID: <42635378.6050002@outerspace.dyndns.org> References: <425CD235.7060909@outerspace.dyndns.org> <4262E109.2010804@trash.net> <426310E5.2030207@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org Return-path: To: Patrick McHardy In-Reply-To: <426310E5.2030207@trash.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Quoting Patrick McHardy on 2005-04-18 01:44 UTC: > But it's a useful feature. If this was the only reason, I think we > should submit it for both IPv4 and IPv6. What's your opinion of my fix included in this IPv6 port (which I fixed for IPv4 separately and Harald accepted last friday) to indicate "goto" targets in iptables -L listings with a [goto] in the match extension part? One alternative could be adding some special character(s) around the jump target itself, like *SUBCHAIN or SUBCHAIN* or ->SUBCHAIN or something.. Also I have no idea whether one should consider the output possibly being used by scripts etc, so I'd appreciate if people could give their opinion on this (before it goes upstream :) .. - -- - - xkr47 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCY1N3xyF48ZTvn+4RAugMAJ9MWEACo1ybJIKs4p2Fr7hT/n1EHwCeLc4T wnNUQ7dzH231Extu+SK0YrY= =t9Wg -----END PGP SIGNATURE-----