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: ma...@freebsd.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ------------------------------------------------------------------------ _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
