Non-Routable (Private) IP

-


RFC 1597 provides for a group of Internet Networks that will never be assigned. Furthermore, these addresses will not route through the Internet.
This makes them the proper choice for use in your home or company Intranet. We recommend non-routable IP for most networks. These IP addresses have specifically been set aside to use when it isn’t necessary (or desirable) for anyone on the Internet to be able to instantly navigate to your computer. It is especially useful to the DSL and Cable Modem users who have multiple computers connected to a single proxy server, firewall or router.
These non-routable IP addresses also provide additional security on the “Internal” side of your network. Typically a firewall, Cable Modem or DSL router will provide Network Address Translation (NAT) to translate the these nonroutable address to a real Internet routable IP address.
Reserved IP addresses for private networks
10.0.0.0 – 10.255.255.255                     /8
172.16.0.0 – 172.31.255.255                 /12
192.168.0.0 – 192.168.255.255             /16
169.254.0.0 – 169.254.255.255    APIPA  – Windows OS systems.
Automatic Private IP addressing
run and ipconfig /all on your windows system and you might see an address such as 169.254.x.y. This happens when you PC cannot find the DHCP server. It will make ups its own ip address. To get rid of this you just run.
ipconfig /release
ipconfig /renew

Comments

Post a Comment

Popular posts from this blog

REVERSE TELNET ON AUX PORT

-
  Requirement :   Need   to   configure   reverse telnet   via   AUX   port. Connect one router's aux port to another device's console port, and telnet to the router.Use reverse telnet to connect to the other device's console via your aux port   Setup   :   Here's how to set it up. 1.       Connect your router's aux port to another device's console port using a Cisco flat crossover cable. 2.       Telnet to your router, enable, and set the aux port up as follows:   R1#conf t R1(config)# line aux 0 R1(config-line)# modem InOut R1(config-line)# transport preferred all R1(config-line)# transport input all R1(config-line)# transport output all R1(config-line)# end 3.       Make sure you have an address on your lo0 interface, and the interface is up. R1#conf t R1(config)#int   lo0 R1(config-if)#ip   add   127.0.0.1 255.255.255.0 Execution : 1)       Come back in enable mode, find out the line number of your AUX port with “show   line”. It will look something l
Read more

Disabling Unneeded Services

-
Step 1: Configure the Physical Interface Because this lab uses only one router, you will simulate an active FastEthernet connection by activating the interface and applying the no keepalive command to initiate an “always up” state, regardless of the existence of a device at the remote end. Normally, you would not use the no keepalive command on a routed interface, except in special circumstances. In this lab, you will use it only for simulation purposes. Configure the R1 physical interface using the IP address shown in the topology diagram. Use the no keepalive command in interface configuration mode, and then use the no shutdown command to activate the interface. Because you have disabled keepalives, the interface status displays as link state (Layer 1) and line protocols state (Layer 2) “up,” even if it is not connected to an external device. R1(config)# interface fastethernet0/0 R1(config-if)# ip address 192.168.10.1 255.255.255.0 R1(config-if)# no keepalive R1(config-if)# no s
Read more