On Sun, 2011-11-27 at 11:26 +0800, Antonio Borneo wrote:
> On Sat, Nov 26, 2011 at 5:14 PM, David Woodhouse <dw...@infradead.org> wrote:
> > On Fri, 2011-11-25 at 08:24 +0800, Antonio Borneo wrote:
> >> no reason, should be applied.
> >> I'll commit it in the weekend.
> >
> > If you don't want to just delete vpnc-script from the vpnc repo, then it
> > would be best to pull in *all* the fixes from the git tree rather than
> > diverging.
> 
> Hi David,
> for openvpn the script vpnc-script is one of the possible options. It
> is acceptable to have it on a separate repository.
> For vpnc, the script is a mandatory component. I prefer keeping it
> inside the same repository.

... unless you're using NetworkManager or ConnMan, of course. Those each
have their own alternative version that just passes the information back
to NM/CM via DBus.

The situation is exactly the same for openconnect which was designed to
use a vpnc-script identical to vpnc's. When used from the command line,
the vpnc-script is mandatory.

To start with, distributions made the openconnect package depend on the
vpnc package — but now they tend to have a separate 'vpnc-script'
package which both vpnc and openconnect packages can depend on, so that
you don't *have* to have vpnc installed.

> I would like to pull all the fixes from your repository and I'm
> checking all of them.
> I have some concern about IPv6 patches.
> So far vpnc doesn't have real support for IPv6. Just few macro
> definition and a check in the script.
> Should we consider these patches as a early IPv6 support in the
> script, waiting for contribution in the core code?
> Are they required by systems configured for IPv6 and running current vpnc?

No, not using vpnc. Only openconnect. But it shouldn't be particularly
hard to make it work for vpnc too, if someone can set up a test server
with IPv6. It doesn't even need to be *real* globally-routable IPv6;
just site-local addresses where you can only reach the server and no
further would be sufficient to test basic connectivity and setup.

-- 
dwmw2

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to