From: Weijie Gao
This patch fixed the problem that kernel will crash when WAN port is
linked-up in QCA9561.
When GMAC0 is configured as GMII, it's connected to the internal switch.
In this situation, there's no need to adjust the speed of GMAC0, and the
function
And I also do not want opkg to invoke the init scripts of the just upgraded
packages until I have finished all my checks and stuff.
I thought it might be useful for others too, if opkg has this option that let
you control the upgrade process a bit more.
What do you think ?
On 02/17/2017 06:17
Hi again,
my previous change was incomplete, please use the following two changes
for testing:
https://git.lede-project.org/71ab6d6.patch
https://git.lede-project.org/e9bd98e.patch
Bye,
Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
On 17/02/2017 17:06, Matthew McClintock wrote:
> Cool, still personally missing a Dakota board myself. Maybe I'll get one soon.
>
> -M
>
i used your v4.7-rc for-next tree as basis for the 4.9 support ;)
John
___
Lede-dev mailing list
Hi,
I am writing an auto update shell script with special install handlers
for some of my packages. The auto updater is a package itself and can
also be updated.
Without --no-configure, opkg would kill my auto updater while it is updating
itself.
On 02/17/2017 06:17 AM, Jonas Gorski wrote:
>
On 17 February 2017 at 17:56, Rafał Miłecki wrote:
> On 17 February 2017 at 16:06, Jonas Gorski wrote:
>> On 17 February 2017 at 15:38, Rafał Miłecki wrote:
>>> On 17 February 2017 at 15:14, Jonas Gorski wrote:
On 17 February 2017 at 16:06, Jonas Gorski wrote:
> On 17 February 2017 at 15:38, Rafał Miłecki wrote:
>> On 17 February 2017 at 15:14, Jonas Gorski wrote:
>>> On 17 February 2017 at 14:53, Rafał Miłecki wrote:
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 ---
On Friday, February 17, 2017
On Thu, Feb 16, 2017 at 6:22 AM, Koen Vandeputte
wrote:
> Hi Felix,
> Hi Tim,
>
> commit "imx6: move to Linux 4.9 kernel" introduces some regression on wlan
> level.
>
>
> When starting wpa_supplicant to initiate an IBSS link, the handshake fails.
> Inspecting it
On 17/02/2017 15:46, Christian Lamparter wrote:
> On Monday, October 31, 2016 10:38:18 PM CET Christian Mehlis wrote:
>> Hi,
>>
>> is there someone working on QCA Dakota support for lede?
> Heads-up!
>
>
What the... This discussion has become a bit out of hand!
My goal was to have consistency at LuCI and CLI. I see how enforcing passwords
of a particular kind, as well as enforcing passwords at all, is not an
engineering decision. I have no problem with this patch being rejected.
So, since we
On 2017-02-15 15:48, Alexey Brodkin wrote:
> arc-2016.09 is the most recent toolchain for ARC cores and
> it is based on top of upstream Binutils 2.27 and GCC 6.2.1.
>
> With updated major version of GCC we copied all GCC 6.x patches
> for ARC as well as Bintils 2.27 patches.
>
> Note that
On 2017-02-16 11:00, Martin Schiller wrote:
> This is needed to use the nflog interface with tcpdump
>
> Signed-off-by: Martin Schiller
> ---
> package/libs/libpcap/Config.in | 5 +
> package/libs/libpcap/Makefile | 7 +--
> 2 files changed, 10 insertions(+), 2
On 17 February 2017 at 15:38, Rafał Miłecki wrote:
> On 17 February 2017 at 15:14, Jonas Gorski wrote:
>> On 17 February 2017 at 14:53, Rafał Miłecki wrote:
>>> I was doing some fun experiments with ssb/bcma/b43 as a research based on:
On 17 February 2017 at 15:14, Jonas Gorski wrote:
> On 17 February 2017 at 14:53, Rafał Miłecki wrote:
>> I was doing some fun experiments with ssb/bcma/b43 as a research based on:
>> [PATCH RFC] kernel: allow selecting kmod-ssb on
On 8 February 2017 at 04:56, Florian Fainelli wrote:
> Le 02/07/17 à 12:36, Daniel Gonzalez Cabanelas a écrit :
>> Fix the register for configuring rising/falling edge
>>
>> Rising should be sense=1, and falling sense=0.
>> The old driver used these values, but the new one
2017-02-17 15:06 GMT+01:00 Jonas Gorski :
> Hi,
>
> On 14 February 2017 at 16:36, Daniel Gonzalez Cabanelas
> wrote:
>> Leds are wrong and a button is missing, fix them.
>>
>> Signed-off-by: Daniel Gonzalez Cabanelas
>> diff --git
Hi,
On 16 February 2017 at 02:14, Daniel Danzberger wrote:
> Calling opkg with --no-configure prevents opkg
> from running the configuration of the package (postinstall scripts ..etc)
>
> This way opkg will only install the package, without restarting the service
> for
Hi,
On 17 February 2017 at 14:53, Rafał Miłecki wrote:
> I was doing some fun experiments with ssb/bcma/b43 as a research based on:
> [PATCH RFC] kernel: allow selecting kmod-ssb on TARGET_brcm47xx_mips74k
>
> I was trying to build 2 variants of ssb package and 2 variants of
Hi,
Please Cc me for brcm63xx patches, this makes it easier for me to
apply them (especially if they get mangled by patchwork).
On 12 February 2017 at 14:48, Anthony Sepa via Lede-dev
wrote:
> The sender domain has a DMARC Reject/Quarantine policy which disallows
>
Hi,
On 14 February 2017 at 16:36, Daniel Gonzalez Cabanelas
wrote:
> Leds are wrong and a button is missing, fix them.
>
> Signed-off-by: Daniel Gonzalez Cabanelas
> diff --git a/target/linux/brcm63xx/dts/cpva502plus.dts
>
I was doing some fun experiments with ssb/bcma/b43 as a research based on:
[PATCH RFC] kernel: allow selecting kmod-ssb on TARGET_brcm47xx_mips74k
I was trying to build 2 variants of ssb package and 2 variants of b43 package.
It didn't work, most likely because of the way PROVIDES is handled. I
On Fri, 17 Feb 2017, Alberto Bursi wrote:
On 02/17/2017 12:52 PM, David Lang wrote:
On Fri, 17 Feb 2017, Alberto Bursi wrote:
And having no password is a much bigger change than having a short
password when you are testing things. It makes a lot of sense to be
excercising the password routine
On 02/17/2017 12:52 PM, David Lang wrote:
> On Fri, 17 Feb 2017, Alberto Bursi wrote:
>
> And having no password is a much bigger change than having a short
> password when you are testing things. It makes a lot of sense to be
> excercising the password routine when doing tests, and very little
On 02/17/2017 12:51 PM, John Crispin wrote:
>
>
> regardless of you liking my use case or not its still a NAK
>
> John
>
Who cares, really. I just posted my opinion.
-Alberto
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
On 17/02/2017 12:35, Alberto Bursi wrote:
>
>
> On 02/17/2017 12:26 PM, John Crispin wrote:
>>
>>
>> On 17/02/2017 12:16, Dan Lüdtke wrote:
>>> Hi David,
>>>
>>> thanks for the fast response!
>>>
On 17 Feb 2017, at 11:54, David Lang wrote:
But deciding that you know
On Fri, 17 Feb 2017, Alberto Bursi wrote:
On 02/17/2017 12:26 PM, John Crispin wrote:
On 17/02/2017 12:16, Dan Lüdtke wrote:
Hi David,
thanks for the fast response!
On 17 Feb 2017, at 11:54, David Lang wrote:
But deciding that you know better than the admin of the system
On 17.2.2017 12.42, danrl wrote:
We are trying to make passwords on LEDE a tiny bit more secure by refusing weak
or short (read: less than 6 characters) passwords.
Please see related discussion over here, where the inconsistencies were
discovered:
https://github.com/openwrt/luci/pull/878
On 17/02/2017 12:16, Dan Lüdtke wrote:
> Hi David,
>
> thanks for the fast response!
>
>> On 17 Feb 2017, at 11:54, David Lang wrote:
>> But deciding that you know better than the admin of the system is not.
>
> Not that I am a fan of telling admins what to do, but do you see
Hi David,
thanks for the fast response!
> On 17 Feb 2017, at 11:54, David Lang wrote:
> But deciding that you know better than the admin of the system is not.
Not that I am a fan of telling admins what to do, but do you see any chance
that we can get an consistent and
By what does this have to do with wpad, I mean that there should be no
dependency on EAP features being present for 802.11w to work.
Nick
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi,
The patch committed here does not seem to be correct as it hides
802.11w support with the full hostapd package:
https://git.lede-project.org/?p=project/luci.git;a=commit;h=07e01d094eb25e1f036e85b8cfc5aceccc56003c
With the hostapd package installed, not mini, the output of hostapd -veap is:
The BT Home Hub routers described in the scenario(s) below are connected
also on the LAN side.
I ran further tests in the first SCENARIO (Red Ethernet as eth0.2)
monitoring the red Ethernet WAN end with wireshark and I saw arp
requests coming from the Red Ethernet that have both mac address
On Fri, 17 Feb 2017, danrl wrote:
Date: Fri, 17 Feb 2017 11:42:14 +0100
From: danrl
To: lede-dev@lists.infradead.org
Cc: Dan Luedtke
Subject: [LEDE-DEV] [PATCH] utils/busybox: prevent weak root passwords
Hi devs,
We are trying to make passwords on LEDE a tiny
> "David" == David Woodhouse writes:
David> On Wed, 2017-02-15 at 14:03 -0800, Russell Senior wrote:
>>
>> I just tried r3499 (master branch), and it works too,
David> Nice. Do you want to reinstate the default configuration for it,
David> which was removed in commit
This patches the busybox passwd source so that even root is not allowed to set
a weak (too short) password. This enables us to define a minimum password length
that is consistent over graphical interfaces (e.g. LuCI) and CLI.
Signed-off-by: Dan Luedtke
---
Hi devs,
We are trying to make passwords on LEDE a tiny bit more secure by refusing weak
or short (read: less than 6 characters) passwords.
Please see related discussion over here, where the inconsistencies were
discovered:
https://github.com/openwrt/luci/pull/878
Here is what the patch
37 matches
Mail list logo