Viscosity client default route?

[FunkyChicken 0]

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.

 

[FunkyChicken 0]

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.

[Support 243]

no problem, glad you figured that out