[vpn-help] -12 against ipsec-tools 0.6.6

[Peter Eisch]

It appears to be the same.  The LAN DHCP def gw still lingers with a metric
of 21 instead of the 20 before the client fiddles and the VPN def gw route
still has a metric of 30.

It looks like you tried to slide the DHCP addr down one and insert the
ISAKMP as one above, but something is still fiddling with it to make it 30
instead of less than the DHCP addr.


On 8/10/06 1:41 PM, "Matthew Grooms" <mgrooms at shrew.net> wrote:

> Brian Jones wrote:
>> With the same test, doing "route add 0.0.0.0 mask 0.0.0.0 10.1.202.2 metric
>> 20" on windows sent all my packets over the tunnel.
>> 
>> With the Cisco client it adds this route by default:
>> Network Destination        Netmask          Gateway       Interface  Metric
>>  0.0.0.0          0.0.0.0       10.1.202.2      10.1.202.2       1
>> 
>> 
>> 
> 
> Peter,
> 
> After seeing your route table, its pretty obvious the route management
> code has some serious issues. The good news is that I have rewritten
> this code but hadn't yet decided whether or not to merged it into the
> 1.0 branch. I would be very grateful if you could help me test it out.
> 
> Here is a new package based of the 1.1 branch. It contains a few new
> things like updated route management code, DPD support and Split DNS
> support.
> 
> http://www.shrew.net/vpn/vpn-client-1.1-alpha-1.exe
> 
> Could your please reboot the machine to clear out the route table and
> try this new package out. It would be helpful if you could keep an eye
> on the route table before and after connecting and then after disconnect
> to make sure things look sane. If this is an improvement for you, I will
> merge the new route table code into 1.0 for the next RC.
> 
> Thanks,
> 
> -Matthew
>