Re: [PATCH] plugins: ifupdown: support source-directory stanza

On 09/06/2016 02:05 PM, Michael Biebl wrote: Am 06.09.2016 um 15:41 schrieb Tony Espy: From: Scott Sweeny <scott.swe...@canonical.com> Enable the ifupdown settings plugin to read interface definitions from the source directory: Hm, I must be missing something. Doesn't the plugin a

[PATCH v3] plugins: ifupdown: support source-directory stanza

From: Scott Sweeny Enable the ifupdown settings plugin to read interface definitions from the source directory: /etc/network/interfaces.d/ --- src/settings/plugins/ifupdown/interface_parser.c | 47 -- .../plugins/ifupdown/tests/test-ifupdown.c

[PATCH v2] plugins: ifupdown: support source-directory stanza

From: Scott Sweeny Enable the ifupdown settings plugin to read interface definitions from the source directory: /etc/network/interfaces.d/ --- src/settings/plugins/ifupdown/interface_parser.c | 47 -- .../plugins/ifupdown/tests/test-ifupdown.c

[PATCH] plugins: ifupdown: support source-directory stanza

From: Scott Sweeny Enable the ifupdown settings plugin to read interface definitions from the source directory: /etc/network/interfaces.d/ --- src/settings/plugins/ifupdown/interface_parser.c | 45 -- .../plugins/ifupdown/tests/test-ifupdown.c

Re: [PATCH v2 0/9] ofono/wwan modem support

On 06/17/2016 11:47 AM, Thomas Haller wrote: On Fri, 2016-06-17 at 10:05 -0400, Tony Espy wrote: On 06/17/2016 07:47 AM, Thomas Haller wrote: Also, sorry for mangled formatting/indentation. There doesn't seem to have been much consistency in the Ubuntu patches in the past

Re: [PATCH v2 0/9] ofono/wwan modem support

On 06/17/2016 07:47 AM, Thomas Haller wrote: On Mon, 2016-06-13 at 13:52 -0500, Dan Williams wrote: On Mon, 2016-06-13 at 18:51 +0200, Thomas Haller wrote: Here: https://cgit.freedesktop.org/NetworkManager/NetworkManager/lo g/ ?h=th/review/ofono Cleanups look good so far, though we need to

[PATCH v2 2/2] Clear WiFi requested_scan if suppl exits

It's possible for wpa_supplicant to exit with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. Gbp-Pq: Name Clear-WiFi-requested_scan-if-suppl-exits.patch --- src/devices/wifi/nm-device-wifi.c | 5 + 1 file changed, 5 insertions(+)

[PATCH v2 1/2] Clear WiFi requested_scan if suppl goes INACTIVE

It's possible for wpa_supplicant to transition to INACTIVE state with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. Gbp-Pq: Name Clear-WiFi-requested_scan-if-suppl-goes-INACTIVE.patch --- src/devices/wifi/nm-device-wifi.c | 4 1

Re: [PATCH v2 2/9] Ignore rild modem devices.

On 06/14/2016 03:52 PM, Dan Williams wrote: On Tue, 2016-06-14 at 15:28 -0400, Tony Espy wrote: On 06/14/2016 12:42 PM, Dan Williams wrote: On Fri, 2016-06-10 at 17:56 -0400, Tony Espy wrote: From: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@canonical. com> Gbp-Pq: Name Ignor

Re: [PATCH v2 2/9] Ignore rild modem devices.

On 06/14/2016 12:42 PM, Dan Williams wrote: On Fri, 2016-06-10 at 17:56 -0400, Tony Espy wrote: From: Mathieu Trudel-Lapierre <mathieu.trudel-lapie...@canonical.com> Gbp-Pq: Name Ignore-rild-modem-devices.patch --- src/nm-manager.c | 8 1 file changed, 8 insertions(+) diff

[PATCH] Ignore wifi p2p devices

Gbp-Pq: Name: Ignore-wifi-p2p-devices.patch --- src/devices/wifi/nm-wifi-factory.c | 9 + 1 file changed, 9 insertions(+) diff --git a/src/devices/wifi/nm-wifi-factory.c b/src/devices/wifi/nm-wifi-factory.c index 2d5f8fa..7b1312d 100644 --- a/src/devices/wifi/nm-wifi-factory.c +++

Re: [PATCH 8/9] Track killswitch change signals from urfkill

On 06/08/2016 05:55 PM, Dan Williams wrote: On Wed, 2016-06-08 at 16:20 -0400, Tony Espy wrote: From: Mathieu Trudel-Lapierre <mathieu.trudel-lapie...@canonical.com> ... Also do that rather than resetting the killswitch to the NM saved WirelessEnabled state if urfkill support is enabled

[PATCH v2 6/9] Add modem reconnect delay to policy

This patch introduces a 5s delay between retry activations for modem devices. Otherwise, the activation attempts can flood the modem all at once, and then trigger the reset_retries timeout ( which defaults to 300s ). Bug-Ubuntu: https://bugs.launchpad.net/bugs/1461593 Gbp-Pq: Name

[PATCH v2 9/9] Fix ofono connection problems

This patch fixes three (re) connection problems with the ofono plugin: 1) If the modem is connected, and registrations drops, and then is restored, the connection isn't re-activated. The fix was simply to change modem_state_cb to not return after setting the state to failed, which allows

[PATCH v2 7/9] Modify NMDeviceModem's available logic

This patch modifies NMDeviceModem's available logic such that the device is only considered available if the modem_state is >= NM_MODEM_STATE_REGISTERED. NMDevice defines 'available' as meaning the device is in such a state that it can be activated. This change prevents NM from trying to activate

[PATCH v2 8/9] Track killswitch change signals from urfkill

From: Mathieu Trudel-Lapierre ... Also do that rather than resetting the killswitch to the NM saved WirelessEnabled state if urfkill support is enabled. Gbp-Pq: Name Track-killswitch-change-signals-from-urfkill.patch --- configure.ac | 11 ++

[PATCH v2 3/9] wwan: add support for using oFono as a modem manager

From: Mathieu Trudel-Lapierre This patch adds core wwan support for ofono, as used by Ubuntu Touch. Signed-off-by: Mathieu Trudel-Lapierre Gbp-Pq: Name wwan-add-support-for-using-oFono-as-a-modem-manager.patch ---

[PATCH v2 5/9] Let NetworkManager read oFono settings file and create connections

From: Mathieu Trudel-Lapierre Gbp-Pq: Name Let-NetworkManager-read-oFono-settings-file-and-crea.patch --- configure.ac | 6 + src/settings/plugins/Makefile.am | 4 +

[PATCH v2 4/9] Add new NMSettingsConnection reset_retries get/set methods

This patch adds get/set methods to NMSettingsConnection for the reset_retries_timeout. This allows sub-classes to override the default setting ( 300s ). Bug-Ubuntu: https://bugs.launchpad.net/bugs/1461593 Gbp-Pq: Name Add-new-NMSettingsConnection-reset_retries-get-set-m.patch ---

[PATCH v2 0/9] ofono/wwan modem support

as a modem manager Let NetworkManager read oFono settings file and create connections Track killswitch change signals from urfkill Tony Espy (4): Add new NMSettingsConnection reset_retries get/set methods Add modem reconnect delay to policy Modify NMDeviceModem's available logic Fix ofono

[PATCH v2 2/9] Ignore rild modem devices.

From: Mathieu Trudel-Lapierre Gbp-Pq: Name Ignore-rild-modem-devices.patch --- src/nm-manager.c | 8 1 file changed, 8 insertions(+) diff --git a/src/nm-manager.c b/src/nm-manager.c index e64c68a..be21baa 100644 --- a/src/nm-manager.c +++

[PATCH v2 1/9] Check at runtime whether to start ModemManager

From: Didier Raboud This makes NetworkManager use runtime detection to manage the ModemManager lifecycle when not run by systemd. Under systemd, we expect the ModemManager service to be started by systemd, under non-systemd, we use the dbus activation feature to start

Re: [PATCH 3/9] wwan: add support for using oFono as a modem manager

On 06/09/2016 06:42 PM, Thomas Haller wrote: On Wed, 2016-06-08 at 16:20 -0400, Tony Espy wrote: From: Mathieu Trudel-Lapierre <mathieu.trudel-lapie...@canonical.com> This patch adds core wwan support for ofono, as used by Ubuntu Touch. Signed-off-by: Mathieu Trudel-Lapierre <mathi

Re: [PATCH 1/9] Ignore rild modem devices.

On 06/08/2016 05:37 PM, Dan Williams wrote: On Wed, 2016-06-08 at 16:20 -0400, Tony Espy wrote: From: Mathieu Trudel-Lapierre <mathieu.trudel-lapie...@canonical.com> Gbp-Pq: Name Ignore-rild-modem-devices.patch --- src/nm-manager.c | 8 1 file changed, 8 insertions(+) diff

Re: [PATCH 2/2] Clear WiFi requested_scan if suppl exits

On 06/08/2016 05:36 PM, Dan Williams wrote: On Wed, 2016-06-08 at 16:24 -0400, Tony Espy wrote: It's possible for wpa_supplicant to exit with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. Oh, I see the fixup for cancel_pending_scan

Re: [PATCH 1/2] Clear WiFi requested_scan if suppl goes INACTIVE

On 06/08/2016 05:33 PM, Dan Williams wrote: On Wed, 2016-06-08 at 16:24 -0400, Tony Espy wrote: It's possible for wpa_supplicant to transition to INACTIVE state with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. Gbp-Pq: Name Clear

[PATCH 1/2] Clear WiFi requested_scan if suppl goes INACTIVE

It's possible for wpa_supplicant to transition to INACTIVE state with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. Gbp-Pq: Name Clear-WiFi-requested_scan-if-suppl-goes-INACTIVE.patch --- src/devices/wifi/nm-device-wifi.c | 15

[PATCH 2/2] Clear WiFi requested_scan if suppl exits

It's possible for wpa_supplicant to exit with an outstanding requested_scan pending. This can lead to a stall condition where scanning no longer occurs. Gbp-Pq: Name Clear-WiFi-requested_scan-if-suppl-exits.patch --- src/devices/wifi/nm-device-wifi.c | 9 - 1 file changed, 8

[PATCH 9/9] Fix ofono connection problems

This patch fixes three (re) connection problems with the ofono plugin: 1) If the modem is connected, and registrations drops, and then is restored, the connection isn't re-activated. The fix was simply to change modem_state_cb to not return after setting the state to failed, which allows

[PATCH 8/9] Track killswitch change signals from urfkill

From: Mathieu Trudel-Lapierre ... Also do that rather than resetting the killswitch to the NM saved WirelessEnabled state if urfkill support is enabled. Gbp-Pq: Name Track-killswitch-change-signals-from-urfkill.patch --- config.h.in | 6 +

[PATCH 7/9] Modify NMDeviceModem's available logic

This patch modifies NMDeviceModem's available logic such that the device is only considered available if the modem_state is >= NM_MODEM_STATE_REGISTERED. NMDevice defines 'available' as meaning the device is in such a state that it can be activated. This change prevents NM from trying to activate

[PATCH 1/9] Ignore rild modem devices.

From: Mathieu Trudel-Lapierre Gbp-Pq: Name Ignore-rild-modem-devices.patch --- src/nm-manager.c | 8 1 file changed, 8 insertions(+) diff --git a/src/nm-manager.c b/src/nm-manager.c index 10aa3d7..c2ed1da 100644 --- a/src/nm-manager.c +++

[PATCH 3/9] wwan: add support for using oFono as a modem manager

From: Mathieu Trudel-Lapierre This patch adds core wwan support for ofono, as used by Ubuntu Touch. Signed-off-by: Mathieu Trudel-Lapierre Gbp-Pq: Name wwan-add-support-for-using-oFono-as-a-modem-manager.patch ---

[PATCH 4/9] Add new NMSettingsConnection reset_retries get/set methods

This patch adds get/set methods to NMSettingsConnection for the reset_retries_timeout. This allows sub-classes to override the default setting ( 300s ). Bug-Ubuntu: https://bugs.launchpad.net/bugs/1461593 Gbp-Pq: Name Add-new-NMSettingsConnection-reset_retries-get-set-m.patch ---

[PATCH 5/9] Let NetworkManager read oFono settings file and create connections

From: Mathieu Trudel-Lapierre Gbp-Pq: Name Let-NetworkManager-read-oFono-settings-file-and-crea.patch --- configure.ac | 6 + src/settings/plugins/Makefile.am | 5 +

[PATCH 6/9] Add modem reconnect delay to policy

This patch introduces a 5s delay between retry activations for modem devices. Otherwise, the activation attempts can flood the modem all at once, and then trigger the reset_retries timeout ( which defaults to 300s ). Bug-Ubuntu: https://bugs.launchpad.net/bugs/1461593 Gbp-Pq: Name

[PATCH 0/9] ofono modem/wwan support

Tony Espy (5): Ignore p2p wifi devices from android Add new NMSettingsConnection reset_retries get/set methods Add modem reconnect delay to policy Modify NMDeviceModem's available logic Fix ofono connection problems config.h.in |6 + configure.ac

[PATCH 2/9] Ignore p2p wifi devices from android

This patch causes NMManager to ignore any p2p WiFi devices exposed by Android WiFi drivers. Bug-Ubuntu: https://bugs.launchpad.net/bugs/1099983 Gbp-Pq: Name Ignore-p2p-wifi-devices-from-android.patch --- src/nm-manager.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

Re: RFC: NetworkManager Device Statistics

On 05/25/2016 12:45 PM, Dan Williams wrote: On Wed, 2016-05-25 at 18:10 +0200, Thomas Haller wrote: On Tue, 2016-05-24 at 12:51 -0400, Tony Espy wrote: We have a new requirement to add a data activity indicator to Ubuntu Touch for certification in certain markets. We've had some internal

Re: RFC: NetworkManager Device Statistics

On 05/25/2016 12:10 PM, Thomas Haller wrote: On Tue, 2016-05-24 at 12:51 -0400, Tony Espy wrote: We have a new requirement to add a data activity indicator to Ubuntu Touch for certification in certain markets. We've had some internal debate about whether or not we should extend NetworkManager

RFC: NetworkManager Device Statistics

We have a new requirement to add a data activity indicator to Ubuntu Touch for certification in certain markets. We've had some internal debate about whether or not we should extend NetworkManager to provide this information to the rest of the system vs. adding logic directly to our

Re: Help with Ubuntu Touch update to NM 1.2

On 05/11/2016 02:19 AM, Thomas Haller wrote: On Tue, 2016-05-10 at 20:49 -0400, Tony Espy wrote: Hi Tony, After we recently landed NM 1.1.93 to Ubuntu 16.04 desktop, I started working on back-porting it to Vivid/15.04 for use by Ubuntu Touch which is still currently pinned to a 0.9.10 version

Help with Ubuntu Touch update to NM 1.2

After we recently landed NM 1.1.93 to Ubuntu 16.04 desktop, I started working on back-porting it to Vivid/15.04 for use by Ubuntu Touch which is still currently pinned to a 0.9.10 version of NM. Very little needed to be changed to get it running. One thing to note is that most of the devices

Re: NM/ofono FlightMode problem

On 06/12/2015 05:16 PM, Dan Williams wrote: On Wed, 2015-06-03 at 20:40 -0400, Tony Espy wrote: Dan -- I'd like to hear your opinion about the following problem I'm trying to solve, and your take on an idea I have of how to fix it. This occurs with the current version of NetworkManager we're

Re: NetworkManager autoconnect

On 06/04/2015 03:38 AM, poma wrote: On 04.06.2015 02:37, Tony Espy wrote: On 06/03/2015 04:24 PM, Pieter Cardoen wrote: I've tested it with WiFi but I also need to know the behaviour of the wwan case. WiFi scanning interval was set to 10 seconds. I'll try it again tomorrow and verify the scan

NM/ofono FlightMode problem

Dan -- I'd like to hear your opinion about the following problem I'm trying to solve, and your take on an idea I have of how to fix it. This occurs with the current version of NetworkManager we're using for Ubuntu on phones, 0.9.10.0-4ubuntu15.1.1 ( see [1] for bzr packaging branch ). One

Re: NetworkManager autoconnect

On 06/03/2015 04:24 PM, Pieter Cardoen wrote: I've tested it with WiFi but I also need to know the behaviour of the wwan case. WiFi scanning interval was set to 10 seconds. I'll try it again tomorrow and verify the scan interval in advance. The WPA_supplicant application has the possibility to

Re: Vanishing nm-applet icon?

On 03/15/2010 07:27 PM, Dan Williams wrote: On Fri, 2010-03-12 at 09:19 +0900, Jacobs Shannon wrote: From searching in the archives, I believe this is the correct terminology, but I couldn't find a clear match to what I saw, nor any workaround or fix. Not even sure what happened. If I did

Re: dhcp client support broken on karmic with latest NM build

On 02/26/2010 06:53 PM, Dan Williams wrote: On Sat, 2010-02-27 at 00:49 +0100, Alessandro Bono wrote: On Fri, 2010-02-26 at 15:19 -0800, Dan Williams wrote: On Fri, 2010-02-26 at 10:47 +0100, Alessandro Bono wrote: On Thu, 2010-02-25 at 11:53 -0800, Dan Williams wrote: On Thu, 2010-02-25 at

Re: does/can networkmanager ever set rfkill?

On 02/25/2010 03:42 PM, Paul Fox wrote: i'm revisiting our ability to kill power to the wireless device for the XO-1.5 laptop. this time around, we're using rfkill to do so. (the XO-1 used a private mechanism.) since there's no dedicated rfkill button, we need to invoke rfkill from a UI. i

Re: [NM 0.7.996] impossible to connect internet (DSL)

Dan Williams wrote: On Thu, 2010-02-04 at 14:16 +0900, Yann Ubuntu wrote: up Is this taken into account? do you need more information? If NM 0.7.998 works for you, then the best thing to do is to request in Launchpad that Ubuntu update the version of NM that they ship. I'm pretty sure they

Re: net manager wireless disabled

shelt...@berkeley.edu wrote: Hi folks When I click the Network Manager Icon (Ubuntu 9.10) it says: Wired Networks device not managed Wireless Networks wireless is disabled I did not disable wireless and I have no idea why the wired network would not be managed by NetworkManager. How do I

Re: net manager wireless disabled

shelt...@berkeley.edu wrote: Hi Tony Thanks for the info. Similar bugs have been reported to Ubuntu and there oddly appears to be no fix yet. That's because it's not a single bug. First, there are many brands of Wi-Fi cards each requiring different drivers. This is then compounded by the

Re: net manager wireless disabled

shelt...@berkeley.edu wrote: Thanks again Tony There is a kill hardware on/off switch for wireless on my machine which I never noticed before. I have turned wireless on but still not working. Have you tried re-booting after turning it on? Strangely Ubuntu 9.04 was unaffected by this

Re: Network Manager patched on Ubuntu Karmic 9.10

Louigi Verona wrote: This is something I understand completely. But those bugs have been reported in great detail with logs and everything in launchpad. If it would be helpful I can find them in launchpad and place links here. Would it be helpful? Yes, that would be helpful, especially if

Re: [PATCH] Easy patch (help out!): preserve wireless-enabled and networking-enabled

On 10/27/2009 07:58 AM, Jirka Klimes wrote: On Friday 23 October 2009 19:19:14 Dan Williams wrote: Anyone want to do a really simple patch? It would close some bugs and help out a lot: Hello Dan, I've done the patch. Please, review it. Jirka -- You beat me to the punch...

Re: Easy patch (help out!): preserve wireless-enabled and networking-enabled

On 10/23/2009 01:19 PM, Dan Williams wrote: Anyone want to do a really simple patch? It would close some bugs and help out a lot: NM 0.8 merged nm-system-settings and NetworkManager, and so now we have a config file. We should be using that config file to store the state of nm-manager.c's

Re: Hidden ESSID, WPA-Enterprise -- troubleshooting help?

On 10/15/2009 02:32 PM, Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dan Williams wrote: On Mon, 2009-09-14 at 10:57 -0400, Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there a document someplace that tells me what information

[Patch] Debian: Kill 0.7 nm-system-setttings on restart

1a1f53520a9d9d0da75d5abcc7743225385b7359 Mon Sep 17 00:00:00 2001 From: Tony Espy e...@ubuntu.com Date: Fri, 21 Aug 2009 17:28:57 -0400 Subject: [PATCH] Make sure to kill NM 0.7 system settings daemon on restart (lp: #410244). --- initscript/Debian/NetworkManager.in |2 ++ 1 files changed, 2 insertions(+), 0

Meru Virtual Cell Technology and NetworkManager?

Just wanted to see if anyone on the list has had any experience with NetworkManager and a company called Meru's Virtual Cell Technology? I recently ran into a problem with their per-Station BSSID configuration and WPA-PSK. I tried a number of different netbooks running Ubuntu 8.04 ( NM 0.6.6

Re: How to connect to a WPA network that uses 10 hexadecimal digits as password

John Mahoney wrote: WPA-psk is the basic method which uses any passphrase of 8 to 63 chars. As far as 10 digit hex, are you sure it is not a WEP 64 hex key because that would fit the description better. As far as I know, a WPA-PSK setup can also use a full 256 byte key specified via 64 ASCII

Re: Flush scan list on resume

Dan Williams wrote: On Wed, 2009-02-04 at 12:45 -0500, Dan Williams wrote: On Tue, 2009-02-03 at 22:38 -0800, Howard Chu wrote: I haven't gone looking for this in the code yet, does NM get a DBUS event on standby/suspend and/or resume? It would be nice if it would flush its AP list at (one

Re: Flush scan list on resume

Dan Williams wrote: On Wed, 2009-02-04 at 15:40 -0800, Howard Chu wrote: Dan Williams wrote: On Wed, 2009-02-04 at 18:04 -0500, Tony Espy wrote: Dan Williams wrote: So here's why old access points show up after resume... Executive summary: exclusively a *driver* problem Detailed

Re: Prevent auto scan in wireless devices

Aloisio Almeida wrote: Hi all, I noticed that wireless devices are always scanning, and this is very bad to power consuption in embedded systems. Having looked at Wi-Fi power consumption last year while working on a MID project, we did some measurements with a Marvell SD8686 card and found

Re: howto disable default multiple device activation?

Dan Williams wrote: On Tue, 2008-11-25 at 09:50 +0100, Nikolaus Filus wrote: Hello, with the switch to Intrepid I finally got the long awaited NM 0.7 features and although it incorporates several enhancements I would really like to set it back to the 0.6 behaviour of 1 active (physical)

Re: Log Directory

Zaki Akhmad wrote: Hai All Where is networkmanager log directory? I am using wireless connection with networkmanager. Unfortunately, the signal is up and down. Switch between connect and disconect, very quickly. Something wrong? what distro/version? what version of network-manager? you'll

Re: Monitor wireless signal on manual mode

Gabriel Ortiz Lour wrote: Hi all, I was wondering how could I monitor the wireless signal on the NM tray icon when I am with the network manually configured, just like when its in roaming mode. What distro/release? What version of NetworkManager? It's important to include this kind of

Re: NetworkManager and rf_kill

via my launchpad PPA ( personal package archive ), and will drop a note to the list when the code's available ( hopefully tomorrow ). Regards, Tony Espy Canonical ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http

NM-0.6.6: Cancel 'Wireless Key Required' Dialog, can't connect again...

We've run into a network-manager ( 0.6.6 ) bug in Ubuntu 8.04 ( it actually was reported in a pre-release version of 7.10 ): If a user cancels the 'Wireless Network Key Required' dialog, when they try to re-connect to the same access point, nothing seems to happen.

Re: How to get NetworkManager connect to known WIFI networks upon BOOT

or not the global settings service, if fully implemented on Ubuntu, would alleviate the need to create a pw-less keyring as mentioned in this bug. 2. Could you explain how the 'ifcfg' backend will work? Thanks, Tony Espy --- Jazz isn't dead, it just smells funny. -- FZ