Mailing List Archive

Re: Bug#640978: Bug#640978: vpnc-script requires an update for recent iproute
On Thu, Nov 24, 2011 at 6:29 AM, Florian Schlichting
<fschlich@zedat.fu-berlin.de> wrote:
> David, Antonio, Eric:
>
> On Sat, Sep 10, 2011 at 09:45:17AM +0100, David Woodhouse wrote:
>> On Sat, 2011-09-10 at 15:52 +0800, Antonio Borneo wrote:
>> >
>> > In the fix you provide,
>> > 1) you add ";s/ipid 0x....//g" at the end of string.
>> >    This does not impact backward compatibility. I'm in favour to
>> > commit it.
>>
>> It's not suHi Florian,fficient. We originally had this in the vpnc-scripts.git
>> repository¹ since about May, but then the iproute command grew *more*
>> unrecognised output options so we have since changed it to be 'opt-in'
>> instead of 'opt-out'².
>
>> ¹ http://git.infradead.org/users/dwmw2/vpnc-scripts.git/shortlog
>> ² http://git.infradead.org/users/dwmw2/vpnc-scripts.git/commitdiff/4deaaf9a32
>
> is there a reason why this improved patch should not be applied to SVN
> as well as to the Debian package of vpnc? Corrected for fuzz, that would
> be

Hi Florian,

no reason, should be applied.
I'll commit it in the weekend.

Best Regards
Antonio

>
> --- a/vpnc-script.in
> +++ b/vpnc-script.in
> @@ -116,7 +116,8 @@ destroy_tun_device() {
>
>  if [ -n "$IPROUTE" ]; then
>        fix_ip_get_output () {
> -               sed 's/cache//;s/metric \?[0-9]\+ [0-9]\+//g;s/hoplimit [0-9]\+//g'
> +        sed -e 's/ /\n/g' | \
> +            sed -ne '1p;/via/{N;p};/dev/{N;p};/src/{N;p};/mtu/{N;p}'
>        }
>
>        set_vpngateway_route() {
>
>
>> I was just thinking that I should submit a patch which removes the
>> out-of-date script from vpnc altogether. There have been a number of
>> other fixes in the git tree too.
>
> What do you mean "remove" the script from vpnc - how would routes pushed
> from the concentrator be configured on the client without this script?
>
>
> From my point of view, vpnc without this patch is severely broken - it's
> not just "not working", it also leaves networking in a non-working state
> after it has been terminated regularly. Ubuntu managed to release with
> the version currently in Debian, which causes some trouble to support,
> and I'd like to make sure that the version in Debian at least works on
> Debian when Ubuntu syncs for their upcoming LTS release.
>
> Florian
>
>
>
>
_______________________________________________
vpnc-devel mailing list
vpnc-devel@unix-ag.uni-kl.de
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/
Re: Bug#640978: Bug#640978: vpnc-script requires an update for recent iproute [ In reply to ]
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.

In fact, if you want to convert the vpnc repo from Subversion to git, it
would then be easy to automatically pull in the changes from
vpnc-scripts.git. I can help you with that (and give you somewhere to
host it) if it helps.

--
dwmw2
Re: Bug#640978: Bug#640978: vpnc-script requires an update for recent iproute [ In reply to ]
On Sat, Nov 26, 2011 at 5:14 PM, David Woodhouse <dwmw2@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.

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?

> In fact, if you want to convert the vpnc repo from Subversion to git, it
> would then be easy to automatically pull in the changes from
> vpnc-scripts.git. I can help you with that (and give you somewhere to
> host it) if it helps.

Locally, I already run all my development on git through git-svn.
No problems to pull in from your tree.

Ragards,
Antonio
_______________________________________________
vpnc-devel mailing list
vpnc-devel@unix-ag.uni-kl.de
https://lists.unix-ag.uni-kl.de/mailman/listinfo/vpnc-devel
http://www.unix-ag.uni-kl.de/~massar/vpnc/
Re: Bug#640978: Bug#640978: vpnc-script requires an update for recent iproute [ In reply to ]
On Sun, 2011-11-27 at 11:26 +0800, Antonio Borneo wrote:
> On Sat, Nov 26, 2011 at 5:14 PM, David Woodhouse <dwmw2@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