[PATCH 3/3] device: when IP config is unchanged, only install updated lifetimes

After DHCP RENEW/REBIND events occur (in particular), do not update the installed routes if there were no relevant IP config changes. Aside from being an optimization, this behavior is needed to avoid unnecessarily interfering with standalone, commerical VPN clients which follow remote security po

Re: [PATCH 3/3] device: when IP config is unchanged, only install updated lifetimes

There is one more line that I modified, which was missing from the last patch. Sorry about that. Resending. On 05/05/2015 08:32 PM, David Ward wrote: > After DHCP RENEW/REBIND events occur (in particular), do not update > the installed routes if there were no relevant IP config changes. > > Aside

[PATCH 3/3] device: when IP config is unchanged, only install updated lifetimes

After DHCP RENEW/REBIND events occur (in particular), do not update the installed routes if there were no relevant IP config changes. Aside from being an optimization, this behavior is needed to avoid unnecessarily interfering with standalone, commerical VPN clients which follow remote security po

[PATCH 1/3] nm-ip[64]-config: check return value from nm_platform_ip[64]_address_sync()

Signed-off-by: David Ward --- src/nm-ip4-config.c | 10 +- src/nm-ip6-config.c | 4 +++- 2 files changed, 8 insertions(+), 6 deletions(-) diff --git a/src/nm-ip4-config.c b/src/nm-ip4-config.c index abc8af8..bd99961 100644 --- a/src/nm-ip4-config.c +++ b/src/nm-ip4-config.c @@ -265,19 +

[PATCH 2/3] device: commit IP config after determining if there are changes

Reorder the code so that it is possible to pass has_changes as a parameter to nm_ip[64]_config_commit(). Also, ensure that the IP config is exported to D-Bus after it is successfully committed, even if old_config is not NULL (because the previous attempt to commit it may have failed). Signed-off-

Re: ModemManager and Thuraya XT

On Tue, 2015-05-05 at 12:21 +0200, Thomas Sailer wrote: > I would like to use my Thuraya XT phone (firmware v5) with ModemManager. > It seems to be detected but then MM seems to choke on its response to > AT+CGREG?. > > Below is the dialog between MM (1.4.4, stock fedora 21) with the phone > after

Re: [PATCH] vpn: don't fail if no system secrets exist

On Mon, 2015-05-04 at 13:56 +0200, Thomas Haller wrote: > On Fri, 2015-05-01 at 15:15 -0500, Dan Williams wrote: > > The VPN connection requests secrets a few times; first it retrieves > > only system-owned secrets to see if they are sufficient (and thus > > doesn't need to bother the user), then i

Re: ANN: NetworkManager 1.0.2 released

On Tue, 2015-05-05 at 15:39 +0200, Lubomir Rintel wrote: > Hi, > > I'm pleased to announce the release of NetworkManager 1.0.2, the > latest stable release in the 1.0.x series. We recommend that users > of 1.0.x series as well as users of older 0.9.10.x series upgrade to > this release which is D-

ANN: NetworkManager 1.0.2 released

Hi, I'm pleased to announce the release of NetworkManager 1.0.2, the latest stable release in the 1.0.x series. We recommend that users of 1.0.x series as well as users of older 0.9.10.x series upgrade to this release which is D-Bus and C API backwards compatible. The 1.0.2 release is mostly a bu

ANN: NetworkManager 1.0.2 released

Hi, I'm pleased to announce the release of NetworkManager 1.0.2, the latest stable release in the 1.0.x series. We recommend that users of 1.0.x series as well as users of older 0.9.10.x series upgrade to this release which is D-Bus and C API backwards compatible. The 1.0.2 release is mostly a bu

ModemManager and Thuraya XT

I would like to use my Thuraya XT phone (firmware v5) with ModemManager. It seems to be detected but then MM seems to choke on its response to AT+CGREG?. Below is the dialog between MM (1.4.4, stock fedora 21) with the phone after it has acquired the network. Does anyone have an idea how to make