Lesson Contents
Cisco IOS devices support a number of banners that are presented to users when they use the console line or when they connect remotely using telnet or SSH. They are often used to inform users about their legal rights. It might be a good idea to present a banner to users who are trying to connect to your device, here are some items you might want to think about:
- To show that only authorized users are allowed to connect.
- That all traffic will be monitored.
- That there is no expectation of privacy.
- Don’t use anything that says “welcome”.
- Don’t add any contact information or information about the router in the banner.
Here’s a good example on the website of the California Technology Agency that gives you more information about what a good banner should contain and some sample texts. Before you implement any banners, make sure to check your legal council first. Having said that, let’s look at the different banners…
Different Banners
Cisco IOS routers support several banners, here they are:
- MOTD banner: the “message of the day” banner is presented to everyone that connects to the router.
- Login banner: this one is displayed just before the authentication prompt.
- Exec banner: displayed before the user sees the exec prompt.
- Incoming banner: used for users that connect through reverse telnet.
We’ll take a look at how to configure these different banners now.
MOTD Banner
We’ll start with the message of the day banner that will be presented to anyone accessing the router:
R1(config)#banner motd #
Enter TEXT message. End with the character '#'.
Authorized users only, violaters will be shot on sight! #The # symbol is a start and stop character. You can use any other character if you want. This is what the MOTD banner looks like:
R1#exit
R1 con0 is now available
Press RETURN to get started.
Authorized users only, violaters will be shot on sight!A nice and welcoming banner that everyone will see…let’s move on to the login banner now.
Login banner
The login banner is presented to users that access the router remotely using telnet or SSH:
R1(config)#banner login $ Authenticate yourself! $Let’s try it out:
R1#telnet 1.1.1.1
Trying 1.1.1.1 ... Open
Authorized users only, violaters will be shot on sight! Authenticate yourself!Above, you see that the login banner is displayed after the MOTD banner. It would have been better if I added some empty lines so that the login banner would show up below the MOTD banner.
Exec banner
The exec banner is shown just before the exec prompt:
R1(config)#banner exec #
Enter TEXT message. End with the character '#'.
You are connected to line $(line) at router $(hostname)
#This time I added an extra line in the banner, and I also used some operators like $(line) and $(hostname). Let’s see what that looks like:
Hello Rene
I’m using DIGI PortServer II 16 with SecureCRT, but when I click on connect to open my rack session, there is a black screen with nothing I have to press enter to start the session, is this normal ?
Thanks a lot
Soufiane
Hello Rene !
I didn´t understood the command “telnet 1.1.1.1 6097” -> why 6097 ? what this means ?
Thanks !
Hi Rodrigo,
This is the destination port. Telnet uses TCP port 23 so if you don’t specify a port number, it will use TCP 23.
You can connect to different port numbers to see if a service is responding or not. I like using it to connect to HTTP (80), HTTPS (443) or in this case, 6097.
Rene
Hi Rene,
I cant understand the Reverse Telnet that you have describe in last section. Why we need it/what is the uses of it and how its works. From where we get the IP(1.1.1.1) and port(6097) . Thx
br//
zaman
Hello Mohammad
In order to save space Rene didn’t explain extensively how to configure reverse telnet, but just showed how to configure a banner for it. A nice piece of information about reverse telnet can be found at this Cisco support forum article, but I can tell you a little about it here.
It basically gives you the ability to telnet into a network connected device (say a router) and then connect to a neighbouring device via its console connection. In essence, this gives you the opportunity to remotely connect to the console connection of a device. This
... Continue reading in our forum