NIC config: internal bridging

Started by Grant Michaud

Grant Michaud

NIC config: internal bridging   12 May 2022, 11:18

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

Quote

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
SoftPerfect Support forum - Andrew avatar image

Re: NIC config: internal bridging   12 May 2022, 13:27

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

Re: NIC config: internal bridging   12 May 2022, 13:52

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

Thanks again for your quick reply.

Grant

Reply to this topic

Sometimes you can find a solution faster if you try the forum search, have a look at the knowledge base, or check the software user manual to see if your question has already been answered.

Our forum rules are simple:

  • Be polite.
  • Do not spam.
  • Write in English. If possible, check your spelling and grammar.

Author:

Email:

Subject

A brief and informative title for your message, approximately 4–8 words:

     

Spam prevention: please enter the following code in the input field below.

 ********   *******   **      **  **     **   ******   
 **        **     **  **  **  **  ***   ***  **    **  
 **        **         **  **  **  **** ****  **        
 ******    ********   **  **  **  ** *** **  **   **** 
 **        **     **  **  **  **  **     **  **    **  
 **        **     **  **  **  **  **     **  **    **  
 **         *******    ***  ***   **     **   ******   

Message: