Jump to content
TorGuard
  • 0

Viscosity client default route?

Rate this question


FunkyChicken

Question

FunkyChicken
After loading viscosity and connecting, the following is my routing table.

 

Active Routes:

Network Destination        Netmask          Gateway       Interface  Metric

          0.0.0.0          0.0.0.0      192.168.1.1    192.168.1.115     20

          0.0.0.0        128.0.0.0       10.9.xx.yy       10.9.xx.zz     21

[rest deleted].

 

Shouldn't the netmask for the second line be 0.0.0.0?  If it's 128.0.0.0, then a host like 4.4.4.4 goes through the VPN, but a host like 206.107.23.5 won't match the netmask, and would go out the normal default route and not be encrypted wouldn't it?

 

Or alternately, adding 2 routes,  0.0.0.0/128.0.0.0 and 128.0.0.0/128.0.0.0 would work if for some reason viscosity doesn't want to lose the original default route.  As a more specific route, it would override the 0.0.0.0 netmask on the first line, so you'd get all traffic out the VPN.

 

I don't know, it just doesn't look right.

 

Link to post
Share on other sites

2 answers to this question

Recommended Posts

  • 0
FunkyChicken

Ifn't that the way it always is?  You post, and then the answer reaches out and smacks you along side the head.    I missed the 128 route down below scrolling through the ridiculously long routing table I have with all the stupid VPN's and VM's I was playing with.

 

My apologies, all is well.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...