vpnc-scripts patch to support split tunneling in windows.

[Diego Garcia del Rio]

Dear Daniel,  Ľubomír

It seems the github repo has more recent changes than those in gitlab.
Also, the gitweb (and plain git)  interface
http://git.infradead.org/users/dwmw2/vpnc-scripts.git/blob_plain/HEAD:/vpnc-script-win.js
seems to be dead / non-responsive.

I see that Ľubomír's github repo seems to have a newer version of the
script, with more commits added compared to the gitlab one. IT seems
the gitlab one has the 2nd to last commit in mart 17, 2015 (this
commit a64e23b  ) , while the Horar's github repo kept adding a lot
more commits after that. Also, gitlab seems to complaining that its no
longer able to sync from the infradead git itself.

It seems that Ľubomír's github has hosted more of the development of
the windows script at least as opposed to gitlab

Best regards,

On Tue, Jun 23, 2020 at 2:09 PM Daniel Lenski <dlenski at gmail.com> wrote:
>
> On Tue, Jun 23, 2020 at 10:04 AM Diego Garcia del Rio <garci66 at gmail.com> wrote:
> >
> > I meant the GitHub repo here: https://github.com/horar/vpnc-scripts. From what I understood horar was one of the devs and when I first found the GitHub repo I created the PR against that one.
> >
> > I will try to create an account on gitlab though and apply the patch there.
> >
> > You can see the PR on GitHub here : https://github.com/horar/vpnc-scripts/pull/5
>
> Thanks. Yeah, Horar (aka Ľubomír Carik) has done a ton of work on
> Windows support. Gitlab hosts the "official" upstream repositories for
> OpenConnect and vpnc-scripts for various platform.
>
> > I didn't think too much about corner cases to be honest, just using the example for split tunnel with included routes but built it for excluded routes using the same default gateway that is added For the VPN gateway. If that logic works it should work for the other excluded routes. Got it from this line: 124
> >
> > exec("route add " + env("VPNGATEWAY") + " mask 255.255.255.255 " + gw);
>
> Gotcah.
>
> > I'll see in more detail what's different with the gitlab repo that might not make it apply
>
> Most likely it's just that we have subsequent/newer changes in the Gitlab repo.
>
> -Dan