I can rebuild again but doesn't my current log say:
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
Doesn't it mean it supports ap mode and it was built with ap support?
On Jun 7, 2016 2:13 PM, "Dan Williams"
On Tue, Jun 7, 2016 at 11:02 AM, Samuel Casa wrote:
> On Sun, May 29, 2016 at 3:14 PM, Thomas Haller wrote:
>> On Fri, 2016-05-27 at 09:59 +0200, Samuel Casa wrote:
>>> On Mon, Apr 18, 2016 at 8:02 PM, Thomas Haller
>>> wrote:
>>> >
On Wed, 2016-06-08 at 08:29 -0700, Ali Nematollahi wrote:
> I can rebuild again but doesn't my current log say:
>
> Supported interface modes:
>
> * IBSS
>
> * managed
>
> * AP
>
> * AP/VLAN
>
> Doesn't it mean it supports
Ah I see. I understand now. Thanks Dan. I'll get that going and will post
my results!
Thanks!!
On Wed, Jun 8, 2016 at 9:26 AM, Dan Williams wrote:
> On Wed, 2016-06-08 at 08:29 -0700, Ali Nematollahi wrote:
> > I can rebuild again but doesn't my current log say:
> >
> >
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
---
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
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
+++
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 +
The following patches add ofono modem/wwan support
to NetworkManager.
One caveat is that these patches have only been
tested using ofono's rilmodem driver ( as used by
Ubuntu Touch ), however other then the 'Preferred'
APN logic in the settings plugin, and the usage of
urfkill for flight-mode,
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
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 +
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
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
---
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
On Wed, 2016-06-08 at 16:20 -0400, Tony Espy wrote:
> 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
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
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
On Wed, 2016-06-08 at 16:20 -0400, Tony Espy wrote:
> 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
On Wed, 2016-06-08 at 12:14 +0300, matti kaasinen wrote:
> Hi!
>
> I got into same conclusion as as Eli (http://billauer.co.il/blog/2012
> /10/dhcp-ip-ntpdate-rtc/) that dhclient notices that time has
> advanced over lease "expire" moment after time jump due to ntpdate.
> As a consequence it
Thanks for this information,
This sounds like dhclient bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1093803
>
> The internal DHCP plugin (from systemd's network library) doesn't have
> issue with resetting time.
>
I hope internal DHCP plugin can also tolerate/ignore IPv4LL addresses so
that
Hi!
I got into same conclusion as as Eli (
http://billauer.co.il/blog/2012/10/dhcp-ip-ntpdate-rtc/) that dhclient
notices that time has advanced over lease "expire" moment after time jump
due to ntpdate. As a consequence it rejects old IP and claims new one. I
tried more elegant way to get this
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() now :) That should go in
the last
On Wed, 2016-06-08 at 16:20 -0400, Tony Espy wrote:
> 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
23 matches
Mail list logo