Hi David,
I did not personally attend but from a quick private talk with blogic it
sounded to me like there's been some constructive discussion in a calm
atmosphere that at least helped to clear up the status quo.
Hauke currently tries to organize a follow up conference call to further
discuss to
what happened with the in-person discussions in Berlin between the OpenWRT folks
and the LEDE folks?
David Lang
On Tue, 25 Oct 2016, Sami Olmari wrote:
Long time lurker here. I personally wish we'd get things rolling again
nicely... I don't know what would be the ultimate doctorine for this,
Long time lurker here. I personally wish we'd get things rolling again
nicely... I don't know what would be the ultimate doctorine for this, but
I'd hate OpenWrt, or whatever the name would be, to die because opinion
diffirences and personal argues etc...
--
Sami Olmari
On Mon, Oct 24, 2016 at
From: Rafał Miłecki
This release fixes bugs introduced in 1.4.40 and 1.4.41.
Signed-off-by: Rafał Miłecki
---
Hi Michael,
Since we use the same version in for-15.05 branch, could you backport
this patch there as well, please?
---
net/lighttpd/Makefile | 4 ++--
1 file changed, 2 insertions(+)
Hi,
> IIUC, your change makes the type of fields vary upon their values.
> I'm wondering how you suggest applications parse the resulting blob messages?
you're right, this doesn't make sense. In my case, the only consumer was
using blobmsg_format_json(), which handles element types dynamically.
Add interface config support to enable or disable ARP proxy in the
kernel per device.
Signed-off-by: Hrvoje Varga
---
bridge.c | 5 +
device.c | 9 +
device.h | 3 +++
system-linux.c | 18 ++
system.h | 1 +
5 files changed, 36 insertions(+
Similar as when updating a vif; call wireless_interface_handle_link removing
the vif from
the network when deleting a vif
Signed-off-by: Hans Dedecker
---
wireless.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/wireless.c b/wireless.c
index 9109ce1..387f4ba 100644
--- a/wireless.c
+++ b/
The bridge name is a copy of the device name; but the device name can
change which is the case when an aliased interface is used as bridge member.
This will result into unwanted side effects like bridge reload triggering
a topology change effect after doing network reload; therefore use the
configu
Hi,
On Wed, Oct 19, 2016 at 1:10 PM, Florian Larysch wrote:
> Currently, libubox uses json_object_get_int when converting a JSON
> document into a blobmsg. However, json-c stores integers as int64_t
> values and may clamp the value when asked to return it as an int32_t.
>
> Always use json_object
