Skip to main content

How to add an IP Route to Windows Routing Table

On some system connected to complex and complicated network, administrator may require to configure a more advanced network topology with additional routing routes requirement. For example, customized route is required when the NIC interface does not know where to route to an IP address on network segment which does not belong to the same subnet, such as router at 192.168.1.1 to access node on 10.1.1.1 and subnet mask of 255.255.255.0. In any cases, administrator or user can add a route into TCP/IP Routing Table using DOS command prompt with route command.
Add IP Route Rules into Windows Routing Table in Command Prompt with Route Command

1. Click Start -> Run (or at Start Search in Windows Vista or Windows 7), and type in Cmd, then press Enter to open a command prompt window.

2. The syntax of route command to add a routing table entry:
route ADD [destination IP address or subnet] MASK [subnet mask] [gateway IP address] [metric] IF [interface]

Not all parts of the syntax is mandatory. Some if optional, such as metric and network interface.
Example command to add a route to 10.1.1.0/24 subnet network through 192.168.1.8 gateway router:

route ADD 10.1.1.0 MASK 255.255.255.0 192.168.1.8

To make the route persistent across boots of the system, use -p flag in addition to route add command. Else, the route is not preserved once system restarts. For example:

route -p ADD 10.1.1.0 MASK 255.255.255.0 192.168.1.8

Note: route help will display different commands and switches supported by route command.

3. Press Enter to execute the route command.

4. View the routing table to verify that the new route rule is added correctly.

Comments

Popular posts from this blog

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.

Connection control operation failed for disk 'ide1:0'

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine.

What worked for me, is
1. Uncheck the "Connected and Connect at power on" from Device Status.
2. Then Change the Device type from "Datastore ISO File to Client Device" Radio Button
3. and press OK to save the changes.

Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui

where it asks

"The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?"

You need to select yes to eject the CD-ROM and then remove the ISO file successfully.

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.