reconnect script

[Matthew Kitchin (public/usenet)]

On 5/27/2011 4:27 PM, David Woodhouse wrote:
> On Fri, 2011-05-27 at 15:25 -0500, Matthew Kitchin (public/usenet)
> wrote:
>> Openconnect version: OpenConnect version v2.25-unknown (That is what it
>> reports)
> That'll be because it's patched so it's not a "clean" v2.25. You ought
> to upgrade to v3.02.
> i
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.
>> 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.
> What does your routing table look like before you kill the offending
> openconnect process, what does it look like when openconnect is dead,
> and what does it look like when you've run a new openconnect process and
> everything is working again?
>
Will do as soon as it dies again.

>>   Killing the openconnect process fixes this. Rebooting the router
>> fixes everything.
> Where does the router fit in the network? Can you describe your network
> topology? I'm completely lost.
6 devices at home on 192.168.1.x network. Router is Openwrt backfire 
with openconnect. IT connects to corporate office, and routes traffic 
for 10.85.0.x and 10.92.x.x
> Do you have 'openconnect -v' output from the time when this goes wrong?
> I assume it thinks it's still working correctly, given that traffic
> *over* it is still working OK?
>
Will do when it dies again.