A problem with openconnect On Windows
Nikos Mavrogiannopoulos
n.mavrogiannopoulos at gmail.com
Fri Nov 7 14:11:27 PST 2014
On Fri, Nov 7, 2014 at 2:59 AM, xiao <mybluebluesky2 at 163.com> wrote:
> Hello,
>
> I compiled the newest openconnect in git for Windows,And run it on Win 7 (in a LAN) to connect the ocserv 0.8.4 (in the public network)。
> Everything is OK when connecting.
>
> And I can visit the internet by browser through the VPN tunnel.
>
> But sometimes I can't visit the internet through the VPN tunnel,although the VPN tunnel exists well.
> At this moment ,I find the route table is right. like below
[...]
> But when I use the tracert tool under cmd ,I find that the first hop is not the interface " 10.1.1.209" but my real public IP.
> And when I wait for sometime, I use the tracert tool under cmd ,the first hop change to the interface " 10.1.1.208" ,And at this moment I can visist the internet Again.
As far as I understand that is because you have two default routes.
Your real public IP gw has one with metric 20, and your VPN's has
metric 2.
You'll have to play with vpnc-script-win.js to achieve what you'd like
to do. Once you do, please let us know too...
regards,
Nikos
More information about the openconnect-devel
mailing list