Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have observed a different behaviour between netcat and telnet when connecting to the public route server bgp-view.tvnetwork.hu and issuing the command show ip bgp.

Using Telnet the output (which is normally some tens of thousands lines long) is truncated and in order to view it all you have to press space or enter to continue (like the man pages). When I connect with netcat it just starts dumping all the output and after the first few hundred lines it hangs. Even if I state explicitly that I want to pause after the first 100 lines using the command terminal length 100 netcat doesn't change behaviour.

Do you have any idea why this happens and how it can be resolved? My OS is ubuntu 10.4 and the route server runs Quagga (version 0.99.5). Same kind of behaviour is also observed with another quagga route server (). With other type of routers (cisco or juniper) that problem doesn't appear.

Thank you.

ps. I also posted this question to stackoverflow but server fault seems more relative.

EDIT:

Wireshark helped me find that the problem is that netcat refuses to negotiate the Window Size option although the server requests "Do Negotiate About Window Size". Netcat has a -t parameter to negotiate telnet options but its behavior is not to accept any options (uses DON'T or WON'T as a default). So the question now is how to make netcat to negotiate window size and send width 80 and height 25 which are the values that telnet sends.

share|improve this question
    
Does using the -i flag with netcat make a difference in the behavior? –  chuckx Aug 16 '10 at 21:13
    
No, it hangs at the same point –  Vasilis Aug 17 '10 at 2:15

1 Answer 1

If you connect with telnet and start by giving the command term len 0, it seems to not use pagination.

At a guess, the reason it doesn't do any pagination when using netcat is that it's probably not doing the expected TELNET protocol negotiations for basic terminal characteristics.

Edit: Seems the main problem is that it just plain takes too long to display the full routing table. After leaving a telnet session, with term len 0 and sh ip bgp running, I ended up with:

Vty connection is timed out.
Connection closed by foreign host.

It MAY be that having periodic data sent to the route server (maybe a space character every 45 seconds) may be enough to not trigger the VTY time-out, but I'd need to check the source code to be sure.

share|improve this answer
    
Thank you for the reply (unfortunately I don't have enough reputation to vote up). Sending a space every few seconds using the java apache commons net library doesn't work either because - similarly to netcat - it doesn't do the pagination (although the library is supposed to emulate telnet). I will probably try some other libraries although again this behavior happens only with quagga routes. –  Vasilis Aug 17 '10 at 14:18
    
@vasilis, the sending of space is primarily there to fool Quagga into believing there's something of interest happening. Not tried it, so I can't say it would work, but certainly worth a try. –  Vatine Aug 18 '10 at 12:30
    
I used wireshark to find out that you are right about not negotiating the telnet options. See my EDIT. –  Vasilis Aug 21 '10 at 18:44

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.