Re: resolvconf update script failure leads to forgotten device

2016-06-14 Thread corey kasten
Tobias, Thanks for getting this done. I'd like to try it out the changes, but my system is Ubuntu 14.04. Will you be backporting the changes for it? If not, will it be available for a later Ubuntu release? Thanks! Corey On Mon, Jun 13, 2016 at 12:50 AM, Tobias Brunner wrote: > Hi Corey, > > FY

Re: resolvconf update script failure leads to forgotten device

2016-06-13 Thread Tobias Brunner
Hi Corey, FYI, I pushed a couple of commits ([1], [2]) that address this to master so they will be included in our next release. Regards, Tobias [1] https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=f4a20b74 [2] https://git.strongswan.org/?p=strongswan.git;a=commitdiff;h=f1064ca5 --

Re: resolvconf update script failure leads to forgotten device

2016-05-06 Thread corey kasten
Hi Tobias: Thank you for your quick and thoughtful response! On Fri, May 6, 2016 at 6:03 AM, Tobias Brunner wrote: > Hi Corey, > > > 1. Call "resolvconf --disable-updates" > > 2. Call resolvconf the way it is currently in > > invoke_resolveconf(). This has the effect of

Re: resolvconf update script failure leads to forgotten device

2016-05-06 Thread Tobias Brunner
Hi Corey, > 1. Call "resolvconf --disable-updates" > 2. Call resolvconf the way it is currently in > invoke_resolveconf(). This has the effect of installing or > deleting the interface without running the update script, and > the exit code returned by "pclos

Re: resolvconf update script failure leads to forgotten device

2016-05-05 Thread corey kasten
Tobias and Yves-Alexis: I would appreciate it if you could take at look at the below. Thanks! Corey Kasten On Thu, May 5, 2016 at 10:21 AM, corey kasten wrote: > Hi! > > I'm using strongswan 5.1.2-0ubuntu2.4 on ubuntu 14.04, and I noticed a > scenario where resolvconf is run which correctly add

resolvconf update script failure leads to forgotten device

2016-05-05 Thread corey kasten
Hi! I'm using strongswan 5.1.2-0ubuntu2.4 on ubuntu 14.04, and I noticed a scenario where resolvconf is run which correctly adds the interface, but when the triggered update scripts run, one of them fails, and resolvconf exits non-zero, which causes invoke_resolvconf() (in src/libhydra/plugins/res