Hide Forgot
Description of Problem: I have a Cisco 677i ADSL-router, and I have to use telnet to configure NAT. With telnet from fairfax/roswell, I get no echo when I have telnetted to the router and write commands - so I can't see what I'm writing. (Telnet to localhost is OK). This was not a problem in Seawolf, so now I have downgraded my Roswell RC1-telnet to the telnet-0.17-10 -package from Seawolf, and it works again. Of course, you can do a lot of configuration even if you can't see what you are writing, but sometimes the result is unexpected. As the "old" telnet-package still works, I think "something" has happened to the new telnet? Version-Release number of selected component (if applicable): telnet-0.17-16
Does 677i have a normal Cisco CLI or some fancy menu-driven interface? telnet-0.17-18 on roswell2 works just fine for me (plain oldschool CLI interface). Could you try rebuilding telnet-0.17-10 and install it on your system (i.e., if curses libs have changed..). Similarly, if you still have a Seawolf box around, does rebuilding -18 there work? If feeling adventurous, you could also try commenting out the "telnet-client-cvs" patch in the spec file.
The telnet interface is not much fancy - just plain telnet. Since last time I tested telnet on Seawolf, I had used up2date - and got the same problem with the new telnet (0.17-18) as I have in the betas. 0.17-10 is the only one of these that works for me. Rebuilding the rpms on Seawolf and Roswell is not making any difference. 0.17-10 works on both systems, 0.17-16 and 0.17-18 does not work. Commenting out "telnet-client-cvs" patch however gives me a "working" rpm!
Hmmm, will review the cvs patch
*** This bug has been marked as a duplicate of 52224 ***
Patch posted to the other report. IMO, this is a MUST-FIX issue. (it won't come up that often as people don't use telnet much anymore, but if you do...)