Hi,
> On 7 Oct 2020, at 22:41, Alexander 'lynxis' Couzens wrote:
>
> On Fri, 25 Sep 2020 21:09:26 +0200
> Thibaut wrote:
>
>> Ping?
>
> LGTM.
>
> What's in the "$wdata/data_0" file? Is it the BDF?
My understanding is (disclaimer: I don’t own any hardware that exposes these
new files) that
Give possibility to wait forever the registration by setting timeout
option to 0.
No timeout can be useful if the interface starts whereas no network is
available, because at the end of timeout the interface will be stopped
and never restarted.
Signed-off-by: Thomas Richard
---
package/network/
Hi Hans,
The issue I have involved adding an external device to the lan bridge
through add_device ubus call. Sometimes this operation fails to add
the new bridge port with the following device debug traces:
Wed Oct 7 04:22:57 2020 daemon.err netifd[2843]:
device_create_default(525): Create simple
Hi Alin,
On Thu, Oct 8, 2020 at 1:31 PM Alin Nastac wrote:
Could you add which issue this fixes ?
Thx
Hans
>
> Signed-off-by: Alin Nastac
> ---
> system-linux.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/system-linux.c b/system-linux.c
> index 6778b1d..9188899 100644
> --- a/sy
Signed-off-by: Alin Nastac
---
system-linux.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/system-linux.c b/system-linux.c
index 6778b1d..9188899 100644
--- a/system-linux.c
+++ b/system-linux.c
@@ -904,6 +904,8 @@ failure:
int system_if_resolve(struct device *dev)
{
struct ifr
> As briefly mentioned on IRC, I have concerns that this might interfere with
> clients using buggy wireless implementations. I've noticed 802.11g clients
> not connecting / listing networks which do not offer a 6 Mbit/s basic rate.
Yes, completely agree. This setting does have interoperability
im
