Re: [LEDE-DEV] [RFC 2/3] ipq: Don't force selection of the IPQ4019 firmware.

On 11/03/2017 05:58 PM, Christian Lamparter wrote: On Friday, November 3, 2017 5:05:39 PM CET gree...@candelatech.com wrote: From: Ben Greear This will allow us to select the CT IPQ4019 firmware instead if desired. Signed-off-by: Ben Greear

Re: [LEDE-DEV] [RFC 2/3] ipq: Don't force selection of the IPQ4019 firmware.

On Friday, November 3, 2017 5:05:39 PM CET gree...@candelatech.com wrote: > From: Ben Greear > > This will allow us to select the CT IPQ4019 firmware instead if > desired. > > Signed-off-by: Ben Greear > --- >

[LEDE-DEV] [RFC 3/3] ath10k-firmware: Support CT IPQ4019 firmware.

From: Ben Greear Initial beta release of the CT IPQ4019 firmware. Features are somewhat similar to the CT 9984 firmware, but more testing and tweaking is yet to come. Signed-off-by: Ben Greear --- package/firmware/ath10k-firmware/Makefile |

[LEDE-DEV] [RFC 2/3] ipq: Don't force selection of the IPQ4019 firmware.

From: Ben Greear This will allow us to select the CT IPQ4019 firmware instead if desired. Signed-off-by: Ben Greear --- package/firmware/ipq-wifi/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[LEDE-DEV] [RFC 1/3] Update to latest ath10k-ct driver, enable AHB.

From: Ben Greear The driver updates include: ath10k driver backport to fix WPA 'pn' related security bugs (4.13 based driver only currently), a fix for off-channel TX for CT wave-1 firmware, a likely fix for napi related crashes, and a backport of the firmware fetch

[LEDE-DEV] [PATCH procd] service: Start services normally when seccomp is disabled

When service init file declares seccomp support (procd_set_param seccomp), but procd is compiled without seccomp support, the service should be started normally, because seccomp-trace and utrace are not available. Older procd versions decided about whether to start a service in seccomp sandbox or

[LEDE-DEV] [PATCH] procd: Always tell cmake whether to include seccomp support or not

Without this change, when a user disables seccomp support in .config, procd does not get recompiled unless the package is cleaned manually. It is because when -D option is missing from cmake command line, cmake uses cached value from the previous run where seccomp was enabled. Signed-off-by:

Re: [LEDE-DEV] umdns fails to launch (seccom related)?

On Fri, Nov 3, 2017 at 4:28 PM, Michal Sojka wrote: > you're right, I'm aware of the problem. I already have a patch with the > fix. I need to do a few cleanups before posting it - I'll look at that > tonight. Fantastic, Michal! I look forward to the fix. In the meantime I

Re: [LEDE-DEV] umdns fails to launch (seccom related)?

Hi Bryan, On Fri, Nov 03 2017, Bryan Mayland wrote: > I use a custom LEDE build as the basis for an open source project and > noticed recently that the umdns daemon has stopped loading. This also > occurs with the standard development snapshot with the umdns package > installed. > root@LEDE:~#

[LEDE-DEV] [PATCH v1] wireguard: version bump to 0.0.20171101

Update wireguard to latest snapshot: 9fc5daf version: bump snapshot 748ca6b compat: unbreak unloading on kernels 4.6 through 4.9 7be9894 timers: switch to kees' new timer_list functions 6be9a66 wg-quick: save all hooks on save 752e7af version: bump snapshot 2cd9642 wg-quick: fsync the temporary

[LEDE-DEV] [PATCH v2] firewall3: ubus: parse the firewall data within the service itself

It gives the ability to create firewall rules within the service itself and independently of the instances. Changes since v1: - align coding style - if no instance is given (within the service), do not write it Signed-off-by: Pierre Lebleu --- ubus.c | 99

[LEDE-DEV] umdns fails to launch (seccom related)?

I use a custom LEDE build as the basis for an open source project and noticed recently that the umdns daemon has stopped loading. This also occurs with the standard development snapshot with the umdns package installed. root@LEDE:~# /etc/init.d/umdns restart Command failed: Request timed out

Re: [LEDE-DEV] 17.01.4 on Mikrotik RB951Ui-2HnD

On 03/11/2017 11:22, Nishant Sharma wrote: Hi Alberto, On Friday 03 November 2017 01:44 PM, Alberto Bursi wrote: On 03/11/2017 08:04, Nishant Sharma wrote: I am not able to find the documentation to install Lede 17.01.x on RB951Ui-2HnD. The device has since then gone into a boot

[LEDE-DEV] [PATCH] dropbear: make syslog support configurable

By default dropbear logs to syslog which discloses info about account names when doing connection attempts (e.g. "Bad password attempt for 'engineer' from x.x.x.x:y") As this facilitates brute force attempts against account names; make syslog support configurable in order not to leak sensitive

[LEDE-DEV] WhiteBox Wireless Router Supplier

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Were looking for a (White

Re: [LEDE-DEV] 17.01.4 on Mikrotik RB951Ui-2HnD

Hi Alberto, On Friday 03 November 2017 01:44 PM, Alberto Bursi wrote: On 03/11/2017 08:04, Nishant Sharma wrote: I am not able to find the documentation to install Lede 17.01.x on RB951Ui-2HnD. The device has since then gone into a boot loop. I searched on the forum as well, but

[LEDE-DEV] Bringing young people in the community: Google Code-In 2017

Hi everyone, I'm Federico Capoano, some of you may know me for my involvement with Ninux, NetJSON, OpenWISP and contribution to several editions of the Google Summer of Code with Freifunk. OpenWISP has been accepted into the Google Code-In:

[LEDE-DEV] [PATCH mountd 0/2] mount: improve handling unsupported filesystems

From: Rafał Miłecki While debugging mountd through adding some prints, I noticed that mount_dev_add will be called every second for unsupported filesystems. Even though LEDE's master branch switched to the blockd, mountd may be still used by some (e.g. LEDE 17.01 release

[LEDE-DEV] [PATCH mountd 2/2] mount: add mount with ignore=1 for unsupported filesystems

From: Rafał Miłecki So far a check for unsupported filesystem was in the mount_add_list which was simply stopping mount from being added to the global list. This resulted in mount_dev_add continuously not being able to find a mount for the given block device and trying to add

[LEDE-DEV] [PATCH mountd 1/2] mount: drop duplicated filesystem check from mount_add_list

From: Rafał Miłecki At the very beginning of this function there is following code: if(fs <= MBR || fs > LASTFS) return; There is no point in checking for the same range again as these checks will always evaluate into true. Signed-off-by: Rafał Miłecki

Re: [LEDE-DEV] 17.01.4 on Mikrotik RB951Ui-2HnD

On 03/11/2017 08:04, Nishant Sharma wrote: Hi, I am not able to find the documentation to install Lede 17.01.x on RB951Ui-2HnD. I used to install OpenWrt 15.05 using TFTP boot, mtd erase and unpacking the tar.gz of the rootfs to mtdblock2 and copying the kernel to mtdblock1. But with

Re: [LEDE-DEV] 17.01.4 on Mikrotik RB951Ui-2HnD

Alright, replying to myself. Here are the steps to flash Lede 17.01.4 on Mikrotik RB951Ui-2HnD: 1. TFTP boot with vmlinux-initramfs.elf as bootfile 2. Use Luci GUI to upload and flash nand-large-squashfs-sysupgrade.bin 3. Fun I have tried it using a self compiled 17.01.4 image, so LuCI was

[LEDE-DEV] 17.01.4 on Mikrotik RB951Ui-2HnD

Hi, I am not able to find the documentation to install Lede 17.01.x on RB951Ui-2HnD. I used to install OpenWrt 15.05 using TFTP boot, mtd erase and unpacking the tar.gz of the rootfs to mtdblock2 and copying the kernel to mtdblock1. But with Lede 17.01.4, there is no tar.gz. I tried doing: