Potential misprint in command documentation

3 posts · Closed

Grant Michaud Guest
12 May 2022

Hello,
Is this a misprint? At the bottom of this page.

This will make Windows think the route through NIC2 is "cheaper" and it will route local traffic via this NIC properly. However, this will also break the Internet connection. In order to fix it, you need to execute the following command at a command prompt:

route -p add 192.168.0.1 mask 255.255.255.255 192.168.0.2

Should it not be
route -p add 192.168.0.1 mask 255.255.255.0 192.168.0.2
?

Should the mask be 255.255.255.255 or 255.255.255.0 ?

Grant

Andrew SoftPerfect
12 May 2022

The documentation is correct about the mask being 255.255.255.255.

In that example, NIC2 was configured "cheaper". It would make Windows access any 192.168.0.x address via NIC2, including the 192.168.0.1 gateway.

To make Windows access 192.168.0.1 via NIC1, while any other 192.168.0.x via NIC2, we add a route to the 192.168.0.1 gateway address only.

Grant Michaud Guest
12 May 2022

Thank you for the clarity, was wanting to run the command and it seemed a little odd.

Thanks again for your quick reply.

Grant

This topic is closed. It has had no new posts for over a year, so the software versions it talks about may be out of date. Start a new topic in Bandwidth Manager if you have a similar question.