From mkitchin.public at gmail.com  Tue Jun  7 17:28:02 2011
From: mkitchin.public at gmail.com (Matthew Kitchin (public/usenet))
Date: Tue, 07 Jun 2011 16:28:02 -0500
Subject: reconnect script
In-Reply-To: <1306658033.2029.349.camel@i7.infradead.org>
References: <4DE008CB.8040305@gmail.com>	
	<1306531663.2029.173.camel@i7.infradead.org>
	<4DE1BD3E.7020205@gmail.com>
	<1306658033.2029.349.camel@i7.infradead.org>
Message-ID: <4DEE97E2.4030104@gmail.com>

On 5/29/2011 3:33 AM, David Woodhouse wrote:
> On Sat, 2011-05-28 at 22:27 -0500, Matthew Kitchin (public/usenet)
> wrote:
>> I tried to compile a package for Openwrt last time, and it didn't go
>> very well. I spent a great deal of time, and made little progress. I
>> believe that is why I'm running a patched version.
> I don't think your current problem is related to the fact that you're
> running v2.25.
>
>>>> After about 3 days, I lose all connectivity between the devices on my
>>>> 192.168.1.x subnet. The devices can still get to the internet, still get
>>>> to the remote vpn subnets, but cannot see each other.
>>> How are the machines connected to one another? And if they can still
>>> happily see everything but each other, wtf is your 'ping 10.85.0.1'
>>> doing?
>>>
>> All the machines at my house are connected by wifi to the Openwrt box.
>> Openwrt has the vpn connection to remote office. All home machines are
>> on the 192.168.1.X subnet. 10.85.0.1 is a router IP at my corporate
>> office I ping to check if the VPN connection is up or not.
> OK, but you said that when the problem happens, they can still get to
> the remote VPN subnets. So this 'ping 10.85.0.1' check would still be
> *working*, and thus fail to detect the problem?
>
> Or did I misunderstand, and your 'reconnect script' isn't actually
> solving the problem with the 192.168.1.x hosts on the wireless not being
> able to talk to each other? Except that when it *happens* to trigger
> because the VPN goes down, that somehow solves the (unrelated?) wlan
> issue?
>
> It sounds like this is an OpenWRT routing problem. If hosts on your
> *wireless* cannot see each other, that really shouldn't be anything to
> do with openconnect. If restarting openconnect 'fixes' it then that
> really makes me suspect the routing setup, because that's all that
> openwer will really change. So I'll need to see those routing tables in
> all three cases.
>
Like taking a car to the mechanic... Still hasn't happened since I 
posted this. Maybe it is because I'm using my local LAN much more now 
than before. Maybe a coincidence. I don't know.


From dwmw2 at infradead.org  Mon Jun 27 08:56:55 2011
From: dwmw2 at infradead.org (David Woodhouse)
Date: Mon, 27 Jun 2011 13:56:55 +0100
Subject: KDE support, autotools
Message-ID: <1309179415.21969.14.camel@macbook.infradead.org>

Ilia Kats has implemented KDE support for NetworkManager 0.9 with
OpenConnect: https://bugs.kde.org/show_bug.cgi?id=226028#c47

Now that we have a second independent user of the 'libopenconnect'
library, it's time to make it a real shared library instead of static.

And although I've always hated libtool, I concede it *is* the easiest
way for me to portably build a shared library on all platforms, so I've
reluctantly switched the build system to autoconf/automake/libtool.

It would be very useful if people could test the tarball from 
ftp://ftp.infradead.org/pub/openconnect/openconnect-3.02-12-g78f3559.tar.gz on as many platforms as possible, and let me know if they have any issues with it.

If all goes well, I'll probably do a 3.10 release some time next week.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse at intel.com                              Intel Corporation



From cweiske at cweiske.de  Tue Jun 28 04:40:21 2011
From: cweiske at cweiske.de (Christian Weiske)
Date: Tue, 28 Jun 2011 10:40:21 +0200
Subject: Storing passwords in the wallet
Message-ID: <20110628104021.5d958b13@cyberdyne>

Hi,


I'd like to see the possibility for storing the OpenConnect VPN
password in the Gnome wallet (seahorse IIRC) and would sponsor the
development.

Anyone interested in implementing this?

-- 
Regards/Mit freundlichen Gr??en
Christian Weiske

-= Geeking around in the name of science since 1982 =-


From dwmw2 at infradead.org  Wed Jun 29 20:03:38 2011
From: dwmw2 at infradead.org (David Woodhouse)
Date: Thu, 30 Jun 2011 01:03:38 +0100
Subject: OpenConnect 3.10 release
Message-ID: <1309392219.19230.7.camel@i7.infradead.org>

The biggest change here is that the authentication library is now a
*shared* library; my requirement of a second independent user has now
been met, because the kde-plasma-networkmanagement tool now supprts
OpenConnect.

To facilitate building of shared libraries on all supported platforms,
I've bitten the bullet and actually used libtool ? even though I *hate*
libtool, it is the easiest way of doing it portably. And since automake
and autoconf only give me mild gnashings of teeth in comparison with my
all-consuming passionate hatred of libtool, and libtool wasn't playing
ball when used directly from real Makefiles, I've just gone the whole
way and used them too.


David Woodhouse (15):
      Update web page to document NetworkManager auth-dialog move
      Add --non-inter option
      Use 'openssl' pkgconfig not 'libssl'. Debian doesn't include -lcrypto in libssl
      Add 'reconnect' invocation of vpnc-script, to re-ensure routing/DNS setup
      Explicitly require pkg-config. It's not installed by default on OS X
      Add openconnect_vpninfo_new_with_cbdata() function to ease C++ integration
      Switch to using autohate :(
      Update changelog
      Fix dist-hook to enforce being at $(VERSION)
      Check for repeated tags in 'make tag'
      Add 'make tmp-dist' for testing tarballs, to work around the tag check
      Remove debugging from uncommitted-check rule
      Silence output from tag checks
      Note the existence of KDE support for NetworkManager + openconnect
      Tag version 3.10

Thomas Schwinge (1):
      Clarify that --script [...] will be evaluated by the shell.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse at intel.com                              Intel Corporation



