Page 1 of 1

Routing Table Corruption

Posted: Wed Dec 19, 2012 2:09 pm
by jamesmomber
Version: 1.4.2
OS: WHS 2011

Hello. I have a weird glitch with trying to selectively route traffic through vpn. Whenever I enter IP addresses in the routing table for my VPN Connection, it is initially accepted and everything works fine. However, these IP addresses slowly get pushed toward the right, being replaced with a "4" value. That is, the value in the IP address column is replaced by a four, and appears in the Route column. Next time I restart Viscosity, IP and Mask read four, and the IP address value is moved over to gateway, and finally metric. After a few restarts of Viscosity, my routing table reads all "4's". Anyone else experience this and have a solution?

Thanks in advance.

Re: Routing Table Corruption

Posted: Wed Dec 19, 2012 4:44 pm
by Eric
Hi James,

That's quite bizzare. Are you able to post up a couple of copies of your routing table as this progresses through a few connections? Also are you able to post up a copy of your connection as exported from Viscosity so we can have a look at how your routes are setup? You may wish to email this to us instead if you do not want this information on the public web.
https://www.sparklabs.com/support/#contact

Regards,
Eric

Re: Routing Table Corruption

Posted: Fri Dec 21, 2012 1:09 pm
by jamesmomber
Thanks for the prompt reply. Here is a succession I'm seeing on the routing table. Note - I have "send all traffic over vpn" box checked as a workaround. Symptoms are reproduced regardless of whether this box is checked.
2.jpg
2.jpg (64.79 KiB) Viewed 4644 times
3.jpg
3.jpg (62.83 KiB) Viewed 4644 times
4.jpg
4.jpg (62.15 KiB) Viewed 4644 times

Re: Routing Table Corruption

Posted: Fri Dec 21, 2012 1:48 pm
by Eric
Hi James,

Thanks for reporting this. It appears to be only graphical. If you don't save your connection after viewing it with the altered routes like this, the routes are still stored and applied correctly when connecting. We will look at getting this fixed as soon as we can.

Regards,

Eric