Nateevs's Posts
Nairaland Forum › Nateevs's Profile › Nateevs's Posts
1 2 3 4 5 6 7 8 ... 472 473 474 475 476 477 478 479 480 (of 685 pages)
OMO IBO:I didn't see that. . |
@Ibime Have you got it? |
I have got no clue how we are playing. . We are all over the place. |
Ibime:nsport |
PF is a very poor player. . |
What was PF doing there? |
Nice play Ibime:Channel 89800 |
This pitch is crazy. . . WE have to be on rampage from the first whistle. Ferriera will get 3 crosses right out of 40. . Why can't we play a youngster there. .? |
What's wrong? No Lampard, No Carvalho. -------------------------Cech------------------------ -Ferriera--------Ivanovic-----Terry----------Zhirkov-- ------------Mikel----------- Joe----- Malouda----- Ballack Anelka Drogba |
Now we need to go ahead and do ourselves a favour. We have to win this. |
chamotex:Nothing went wrong dude. Everton are a strong team. Last week when everyone was shouting about our loss I said I never expect to get 3 pts against Everton - Home or away. These guys are strong organized and very hard to beat. Give credit to them. |
Goaaaaaaaaaaaaaaaaalllllllllllllllllllllllllll |
That was scary. . . Thot Rooney put it in. |
Everton . . you guys will be really mad if you let this one go. |
Now that's what I'm talking 'bout. Let's go fellas . . Snatch all 3 points. |
game on. |
Thanks Debo. Though I got banned afterwards but it's all fine now. Thanks. |
PT3. Now clear the config on the router and configure SSH on it this way. Remember to reconfigure the Ethernet Interfaces as well. Router#conf t Router(config)#username admin password cisco Router(config)#ip domain-name nateevs.com Router(config)#crypto key genrate key rsa You should see this output on your router. . . The name for the keys will be: R1.nateevs.com Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys, keys will be non-exportable, [OK] *Mar 18 14:09:19.401: %SSH-5-ENABLED: SSH 1.99 has been enabled It is also good practise to configure ssh authentication retries and time out on the router Router(config)#ip ssh authentication retries 3 Router(config)#ip ssh timeout 60 Next is to configure the vyt lines to accept only SSH this way: Router(config)#line vty 0 15 Router(config-line)#transport input ssh Router(config-line)#login local We are good to go. Now on your pc, try to telnet into the router again. This is what you should see. C:\Documents and Settings\Nateevs>telnet 192.168.1.1 Connecting To 192.168.1.1, Could not open connection to the host, on port 23: Connection failed The router no longer allows communication on TCP port 23 (Telnet). You can only now SSH into the router. To do that, you need to download and install an SSH client software like Putty or Tera term. Enter the IP address of the router. You will be prompted to authenticate. Enter username and password configured. Launch Wireshark. Click on and analyse packet transfer from source to destination on TCP port. See attached doc. You should see that the packet is encrypted. That's SSH in a nut shell. Read up on some more and it's straight forward. If you have any problems executing any of the above tasks just post here. |
I am trying to post Part 3 of the Lab scenario. The spam-bot on the site will not allow me do it. So I attach it as a word doc. So anyone who wants it can download it and use. |
PT3. Now clear the config on the router and configure SSH on it this way. Remember to reconfigure the Ethernet Interfaces as well. Router#conf t Router(config)#username admin password cisco Router(config)#ip domain-name nateevs.com Router(config)#crypto key genrate key rsa You should see this output on your router. . . The name for the keys will be: R1.nateevs.com Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys, keys will be non-exportable, [OK] *Mar 18 14:09:19.401: %SSH-5-ENABLED: SSH 1.99 has been enabled It is also good practise to configure ssh authentication retries and time out on the router Router(config)#ip ssh authentication retries 3 Router(config)#ip ssh timeout 60 Next is to configure the vyt lines to accept only SSH this way: Router(config)#line vty 0 15 Router(config-line)#transport input ssh Router(config-line)#login local We are good to go. Now on your pc, try to telnet into the router again. This is what you should see. C:\Documents and Settings\Nateevs>telnet 192.168.1.1 Connecting To 192.168.1.1, Could not open connection to the host, on port 23: Connection failed The router no longer allows communication on TCP port 23 (Telnet). You can only now SSH into the router. To do that, you need to download and install an SSH client software like Putty or Tera term. Enter the IP address of the router. You will be prompted to authenticate. Enter username and password configured. Launch Wireshark. Click on and analyse packet transfer from source to destination on TCP port. See attached doc. You should see that the packet is encrypted. That's SSH in a nut shell. Read up on some more and it's straight forward. If you have any problems executing any of the above tasks just post here. |
PT3. Now clear the config on the router and configure SSH on it this way. Remember to reconfigure the Ethernet Interfaces as well. Router#conf t Router(config)#username admin password cisco Router(config)#ip domain-name nateevs.com Router(config)#crypto key genrate key rsa You should see this output on your router. . . The name for the keys will be: R1.nateevs.com Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys, keys will be non-exportable, [OK] *Mar 18 14:09:19.401: %SSH-5-ENABLED: SSH 1.99 has been enabled It is also good practise to configure ssh authentication retries and time out on the router Router(config)#ip ssh authentication retries 3 Router(config)#ip ssh timeout 60 Next is to configure the vyt lines to accept only SSH this way: Router(config)#line vty 0 15 Router(config-line)#transport input ssh Router(config-line)#login local We are good to go. Now on your pc, try to telnet into the router again. This is what you should see. C:\Documents and Settings\Nateevs>telnet 192.168.1.1 Connecting To 192.168.1.1, Could not open connection to the host, on port 23: Connection failed The router no longer allows communication on TCP port 23 (Telnet). You can only now SSH into the router. To do that, you need to download and install an SSH client software like Putty or Tera term. Enter the IP address of the router. You will be prompted to authenticate. Enter username and password configured. Launch Wireshark. Click on and analyse packet transfer from source to destination on TCP port. See attached doc. You should see that the packet is encrypted. That's SSH in a nut shell. Read up on some more and it's straight forward. If you have any problems executing any of the above tasks just post here. |
PT3. Now clear the config on the router and configure SSH on it this way. Remember to reconfigure the Ethernet Interfaces as well. Router#conf t Router(config)#username admin password cisco Router(config)#ip domain-name nateevs.com Router(config)#crypto key genrate key rsa You should see this output on your router. . . The name for the keys will be: R1.nateevs.com Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys, keys will be non-exportable, [OK] *Mar 18 14:09:19.401: %SSH-5-ENABLED: SSH 1.99 has been enabled It is also good practise to configure ssh authentication retries and time out on the router Router(config)#ip ssh authentication retries 3 Router(config)#ip ssh timeout 60 Next is to configure the vyt lines to accept only SSH this way: Router(config)#line vty 0 15 Router(config-line)#transport input ssh Router(config-line)#login local We are good to go. Now on your pc, try to telnet into the router again. This is what you should see. C:\Documents and Settings\Nateevs>telnet 192.168.1.1 Connecting To 192.168.1.1, Could not open connection to the host, on port 23: Connection failed The router no longer allows communication on TCP port 23 (Telnet). You can only now SSH into the router. To do that, you need to download and install an SSH client software like Putty or Tera term. Enter the IP address of the router. You will be prompted to authenticate. Enter username and password configured. Launch Wireshark. Click on and analyse packet transfer from source to destination on TCP port. See attached doc. You should see that the packet is encrypted. That's SSH in a nut shell. Read up on some more and it's straight forward. If you have any problems executing any of the above tasks just post here. |
PT3. Now clear the config on the router and configure SSH on it this way. Remember to reconfigure the Ethernet Interfaces as well. Router#conf t Router(config)#username admin password cisco Router(config)#ip domain-name nateevs.com Router(config)#crypto key genrate key rsa You should see this output on your router. . . The name for the keys will be: R1.nateevs.com Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys, keys will be non-exportable, [OK] *Mar 18 14:09:19.401: %SSH-5-ENABLED: SSH 1.99 has been enabled It is also good practise to configure ssh authentication retries and time out on the router Router(config)#ip ssh authentication retries 3 Router(config)#ip ssh timeout 60 Next is to configure the vyt lines to accept only SSH this way: Router(config)#line vty 0 15 Router(config-line)#transport input ssh Router(config-line)#login local We are good to go. Now on your pc, try to telnet into the router again. This is what you should see. C:\Documents and Settings\Nateevs>telnet 192.168.1.1 Connecting To 192.168.1.1, Could not open connection to the host, on port 23: Connection failed The router no longer allows communication on TCP port 23 (Telnet). You can only now SSH into the router. To do that, you need to download and install an SSH client software like Putty or Tera term. Enter the IP address of the router. You will be prompted to authenticate. Enter username and password configured. Launch Wireshark. Click on and analyse packet transfer from source to destination on TCP port. See attached doc. You should see that the packet is encrypted. That's SSH in a nut shell. Read up on some more and it's straight forward. If you have any problems executing any of the above tasks just post here. |
PT3. Now clear the config on the router and configure SSH on it this way. Remember to reconfigure the Ethernet Interfaces as well. Router#conf t Router(config)#username admin password cisco Router(config)#ip domain-name nateevs.com Router(config)#crypto key genrate key rsa You should see this output on your router. . . The name for the keys will be: R1.nateevs.com Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys, keys will be non-exportable, [OK] *Mar 18 14:09:19.401: %SSH-5-ENABLED: SSH 1.99 has been enabled It is also good practise to configure ssh authentication retries and time out on the router Router(config)#ip ssh authentication retries 3 Router(config)#ip ssh timeout 60 Next is to configure the vyt lines to accept only SSH this way: Router(config)#line vty 0 15 Router(config-line)#transport input ssh Router(config-line)#login local We are good to go. Now on your pc, try to telnet into the router again. This is what you should see. C:\Documents and Settings\Nateevs>telnet 192.168.1.1 Connecting To 192.168.1.1, Could not open connection to the host, on port 23: Connection failed The router no longer allows communication on TCP port 23 (Telnet). You can only now SSH into the router. To do that, you need to download and install an SSH client software like Putty or Tera term. Enter the IP address of the router. You will be prompted to authenticate. Enter username and password configured. Launch Wireshark. Click on and analyse packet transfer from source to destination on TCP port. You should see this: |
PT3. Now clear the config on the router and configure SSH on it this way. Remember to reconfigure the Ethernet Interfaces as well. Router#conf t Router(config)#username admin password cisco Router(config)#ip domain-name nateevs.com Router(config)#crypto key genrate key rsa You should see this output on your router. . . The name for the keys will be: R1.nateevs.com Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes. How many bits in the modulus [512]: 512 % Generating 512 bit RSA keys, keys will be non-exportable, [OK] *Mar 18 14:09:19.401: %SSH-5-ENABLED: SSH 1.99 has been enabled It is also good practise to configure ssh authentication retries and time out on the router Router(config)#ip ssh authentication retries 3 Router(config)#ip ssh timeout 60 Next is to configure the vyt lines to accept only SSH this way: Router(config)#line vty 0 15 Router(config-line)#transport input ssh Router(config-line)#login local We are good to go. Now on your pc, try to telnet into the router again. This is what you should see. C:\Documents and Settings\Nateevs>telnet 192.168.1.1 Connecting To 192.168.1.1, Could not open connection to the host, on port 23: Connection failed The router no longer allows communication on TCP port 23 (Telnet). You can only now SSH into the router. To do that, you need to download and install an SSH client software like Putty or Tera term. Enter the IP address of the router. You will be prompted to authenticate. Enter username and password configured. Launch Wireshark. Click on and analyse packet transfer from source to destination on TCP port. You should see this: |
PART 2 If you do not have routers you can download GNS3 from the internet and install on your pc. You are also going to need[b] WIRESHAR[/b]K. Wireshark is a network analyser - it is also a network packet sniffing tool. Download and install it. Now configure both Ethernet interfaces of your Router with IP addresses within the same IP subnet. Your PC connected to this setup must also have an IP address in the same IP subnet. Now configure the vty lines on your router. Router#conf t Router(config)#line vty 0 15 Router(config-line)#password cisco Router(config-line)#login Launch Wireshark. Set the network interface on the pc to "promiscuous mode" within Wireshark. This allows you to monitor packet transfer in the network. From your pc, telnet into one of the routers. The router will prompt fro password. Enter password. Now quickly watch the activity on Wireshark. You should see TCP packets on port 23 from Source address (PC) to destination address (router). Click on it and then analyse the packet. You should see the password you typed into the router in Wireshark. Right there in plain text. This is very bad. Someone with a packet sniffer like Wireshark can see your vty passwords, gain access to your router, modify or steal information your network. We don't want that. |
PT2. If you don't have routers, download a program called GNS3. You will be able to simulate real live Cisco routers on the program. Next step is to download WIRESHARK on your pc. Wireshark is a sniffing tool. Now configure passwords on the vty lines on both routers. Router#conf t Router(config)#line vty 0 4 Router(config-line)#login Router(config-line)#password cisco Configure IP addresses on the Fast ethernet interfaces of both routers. Make sure the IP addresses are in the same IP subnet. You will also need to configure the LAN port of your pc in this same IP Subnet. Launch Wireshark (You will need to set the properties of the network interface of the pc connected to the lab to "Promiscous mode" so you can see packets transfer in real time.). Now from the PC, telnet into any of the routers. The router will prompt for a password. Enter the password you configured. When you are inside the router, qucikly take a look at the Wireshark program you should see telnet communication between your pc and the router you are telnet into. Analyse the packet. You will see that the password you entered on the router is on there in clear text. This is the danger. Every other communication between the pc and the Router on the vty line is also sent in clear text. Anyone with a packet sniffer can sit on the network and see ever thing going on between the router and the pc. Not good! |
PT2. If you don't have routers, download a program called GNS3. You will be able to simulate real live Cisco routers on the program. Next step is to download WIRESHARK on your pc. Wireshark is a sniffing tool. Now configure passwords on the vty lines on both routers. Router#conf t Router(config)#line vty 0 4 Router(config-line)#login Router(config-line)#password cisco Configure IP addresses on the Fast ethernet interfaces of both routers. Make sure the IP addresses are in the same IP subnet. You will also need to configure the LAN port of your pc in this same IP Subnet. Launch Wireshark (You will need to set the properties of the network interface of the pc connected to the lab to "Promiscous mode" so you can see packets transfer in real time.). Now from the PC, telnet into any of the routers. The router will prompt for a password. Enter the password you configured. When you are inside the router, qucikly take a look at the Wireshark program you should see telnet communication between your pc and the router you are telnet into. Analyse the packet. You will see that the password you entered on the router is on there in clear text. This is the danger. Every other communication between the pc and the Router on the vty line is also sent in clear text. Anyone with a packet sniffer can sit on the network and see ever thing going on between the router and the pc. Not good! |
yemi 22:With remote network access and management, the norm was to use telnet as a communication protocol. Telnet is insecure as it sends everything between the communicating devices in clear text. Someone with a packet sniffer in the middle of the communicating devices could sniff and see data being sent in clear text. Things like passwords This is insecure and very bad for data integrity and confidentiality. SSH is the answer to that. It encrypts all data sent between the communicating devices. It provides data integrity and confidentiality. SSH usesTCP port 22 during communication. SIMPLE LAB TEST. Set up two Cisco routers connected via an ethernet switch and a pc on the network. So your setup looks like this:
|
simo2rule:I wish you well in CCNA Exams. . . You should ask when you don't understand some terms we use in here. Those that know will give us some more info on what they are talking about. |
FBS:Honestly out of the about 20 crosses he made it was the only one that reached a Chelsea player. . . How many could DD have scored if Paulo's crosses reached him. . The guy is wack. . always has been. We should sell him off and play a youngie when we need another right back. |
Game Over. . Chelsea 4 - 1 Cardiff Chelsea through to the next round of the FA Cup. |
1 2 3 4 5 6 7 8 ... 472 473 474 475 476 477 478 479 480 (of 685 pages)
That was inch perfect!