From owner-freebsd-net@FreeBSD.ORG Thu Feb 16 23:47:37 2012 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B169E106564A for ; Thu, 16 Feb 2012 23:47:37 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 3C8748FC08 for ; Thu, 16 Feb 2012 23:47:36 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.4/8.14.4) with ESMTP id q1GNbSJY031571 for ; Fri, 17 Feb 2012 03:37:28 +0400 (MSK) (envelope-from marck@rinet.ru) Date: Fri, 17 Feb 2012 03:37:28 +0400 (MSK) From: Dmitry Morozovsky To: freebsd-net@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (woozle.rinet.ru [0.0.0.0]); Fri, 17 Feb 2012 03:37:28 +0400 (MSK) Cc: Subject: rsh -n to cisco router: incomplete output X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2012 23:47:37 -0000 Dear colleagues, some time ago users of our looking glass start to complain about non-working ping and traceroute commands; looking at the source, I've found that rsh -n router command partially stops working: it returns some of contents (results up to first ping or up to first answer from the first hop in the case of traceroute) I even looked into tcpdumps and consulted with colleagues, but found only TCP RESET semmingly from FreeBSD side which prevents all data to be read. I also tried to look at rsh.c, which was not changed since 2005, just to realize I can't find relevant parts. This is very stable effect, from 4 to 8 branches. I'm not sure where it starts to be broken, alas. Maybe it's something related to IOS versions; however, I doubt it, as all 3 our borders, including rather old one 7206, produce the same output. Any hints? Thank you in advance; please keep me in CC list as I'm not subscribed to -net. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------