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 ---
I have been using OpenWRT for year
Who needs telnet when nc is there ?
> Op 18 feb. 2018, om 19:25 heeft Philip Prindeville
> het volgende geschreven:
>
>
>
>> On Feb 18, 2018, at 2:27 AM, John Crispin wrote:
>>
>>
>>
>>> On 20/06/17 19:13, Stefan Tomanek wrote:
>>> While sshd should be favoured over telnetd, having a teln
Am 19.02.2018 um 18:57 schrieb p.wa...@gmx.at:
> I remember something related to the definition of Sundays.
> IIRC, cron accepts '0' and '7' as Sunday whereas Busybox' cron does not
> understand '7',
> so you have to use '0' for Sundays there.
> Maybe this causes the behaviour you perceived.
Yes,
This patch fixes a bug when someone tries to set up a Wireguard tunnel
to an endpoint where its ip belongs to a local subnet, e.g. in a Freifunk
olsr mesh. The call of proto_add_host_dependency() is just needed in cases
where the endpoint is reachable via a default gateway but not in such cases
whe
I suggest that this gets merged to OpenWRT/LEDE before this makes
mainline and the long term support branches of the upstream Kernel.
Nick
-- Forwarded message --
From: Toke Høiland-Jørgensen
Date: Fri, Feb 2, 2018 at 10:36 AM
Subject: [PATCH] ath9k: Protect queue draining by rc
Hi John,
> currently units will have ~300k on flash for mac files
So, by 'for mac files' you mean the /arch/.../mach-*.c ?
Then there'd additionally be some kBytes for etc/board.d/* and all the
other case statements in the shell scripts at other locations.
(-> per-device-root-filesystem; what's t
Hi Hartmut,
> Every of this jobs will be executed on all weekdays. Is something wrong in my
> definition or does cron from busybox has a
> bug?
I remember something related to the definition of Sundays.
IIRC, cron accepts '0' and '7' as Sunday whereas Busybox' cron does not
understand '7',
so y
Op ma, 19 feb 2018 om 6:23 , schreef Stijn Segers
:
Op ma, 19 feb 2018 om 1:43 , schreef Syrone Wong
:
It's fixed by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.9.y&id=83946c33b9b99b5bc6157cfbf3970265f006c2bf
Best Regards,
Syrone Wong
Thanks
Op ma, 19 feb 2018 om 1:43 , schreef Syrone Wong
:
It's fixed by
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.9.y&id=83946c33b9b99b5bc6157cfbf3970265f006c2bf
Best Regards,
Syrone Wong
Thanks, will send in a new patch.
Stijn
On Mon, Feb 19, 2
Hello,
I try to use cron to run some jobs depend on the weekday. It looks like that
the weekday definition is completely ignored:
15 9 * * 1,2,3,4,5 mosquitto_pub -h mosquitto.lan -q 1 -r -p 1883 -t
"cmnd/iRobot/POWER" -m "1"
15 10 * * 6,7 mosquitto_pub -h mosquitto.lan -q 1 -r -p 1883 -t
"cmn
On Wed, Feb 14, 2018 at 2:58 PM, Jo-Philipp Wich wrote:
> Support configuration in the form...
>
> list ip6prefix 2001:db8:1234::/64
> list ip6prefix 2001:db8:5678::/64
>
> ... to allow specifying multiple routed IPv6 prefixes.
>
> Implements feature request FS#1361.
>
> Signed-off-by: Jo-
On Mon, Feb 19, 2018 at 3:41 PM, John Crispin wrote:
> please dont top post.
Apologies! Thank you for the kind reminder.
> ath79 is the same as ar71xx but uses dts files instead of mach files
Right, does that mean there might be an ath79 target, which is not
ready yet, or am I confusing things?
On Wed, Feb 14, 2018 at 2:58 PM, Jo-Philipp Wich wrote:
> Support configuration in the form...
>
> list ip6prefix 2001:db8:1234::/64
> list ip6prefix 2001:db8:5678::/64
>
> ... to allow specifying multiple additional IPv6 prefixes.
>
> Implements feature request FS#1361.
>
> Signed-off-by:
Hi,
Am Sonntag, 18. Februar 2018, 22:43:42 CET schrieb Hauke Mehrtens:
> ...
>
> The following targets are on kernel 4.9 and are fine:
> ...
> * mxs
> ...
a few weeks ago, I was in contact with Zoltan who started working
on 4.14 support for mxs. I found some patches in his staging repo
and added
On 19/02/18 13:54, Maciej Soltysiak wrote:
Hi John,
As a user of an ar71xx (WNDR3800) on OpenWrt, I'd like to ask if your
desire is that ar71xx never gets bumped up to anything higher than 4.9
or it's just not 4.14 because of some specific reasons related to 4.14?
IOW, shall I be looking f
On 2018-02-19 11:47, Andrey Jr. Melnikov wrote:
Koen Vandeputte wrote:
The current implementation only checked if uqmi itself executed
correctly which is also the case when the returned value is actually
an error.
Rework this, checking that CID is a numeric value, which can only
be true if uq
On 19/02/18 12:09, Arjen de Korte wrote:
Citeren John Crispin :
On 18/02/18 22:43, Hauke Mehrtens wrote:
The next OpenWrt release will use kernel 4.9 and kernel 4.14 depending
on the target. All targets that are *not* on either kernel 4.9 or 4.14
will not be included in the next release.
I
Citeren John Crispin :
On 18/02/18 22:43, Hauke Mehrtens wrote:
The next OpenWrt release will use kernel 4.9 and kernel 4.14 depending
on the target. All targets that are *not* on either kernel 4.9 or 4.14
will not be included in the next release.
I did some overview of the kernel version some
Koen Vandeputte wrote:
> The current implementation only checked if uqmi itself executed
> correctly which is also the case when the returned value is actually
> an error.
> Rework this, checking that CID is a numeric value, which can only
> be true if uqmi itself also executed correctly.
Why ig
On 2018-02-19 12:42, Karl Palsson wrote:
Hauke Mehrtens wrote:
The following targets are on kernel 4.4 and will probably not
be included in the next release:
* gemini
This is a platform that upstream seems to be actually working on,
would it not be at least polite to keep it alive while it's
On 2018-02-15 13:29, Felix Fietkau wrote:
On 2018-02-14 16:20, Rosen Penev wrote:
On Tue, Feb 13, 2018 at 11:10 PM, Felix Fietkau wrote:
On 2018-02-13 23:53, Rosen Penev wrote:
Based on Qualcomm driver. Improves iperf3 throughput by ~20mbps on
transmit on Archer C7v4.
Signed-off-by: Rosen P
Hauke Mehrtens wrote:
> The following targets are on kernel 4.4 and will probably not
> be included in the next release:
> * gemini
This is a platform that upstream seems to be actually working on,
would it not be at least polite to keep it alive while it's
landing in mainline? I don't have any
The current implementation only checked if uqmi itself executed
correctly which is also the case when the returned value is actually
an error.
Rework this, checking that CID is a numeric value, which can only
be true if uqmi itself also executed correctly.
Signed-off-by: Koen Vandeputte
---
pac
This issue is also present in kernel 4.9 starting from 4.9.71
Adapted the patch, as the fixed function is in another location here.
Signed-off-by: Koen Vandeputte
---
.../pending-4.9/812-pci-dwc-fix-enumeration.patch | 62 ++
1 file changed, 62 insertions(+)
create mode 100
2018-02-19 1:40 GMT+03:00 Hauke Mehrtens :
> On 02/18/2018 11:21 PM, Andrey Jr. Melnikov wrote:
>> Fix this patch before release. Or drop it if no one has seen this damage and
>> does not complain.
>
> Hi Andrey,
>
> What is the problem with this patch?
It's bkoren.
code from 4.4 kernel:
@@
Hi,
I have a few PCEngines APUs and Alix running OpenWrt. At times the
filesystem is found to be in read-only mode and I need to do fsck and
then reboot in order to make config changes.
How can I enable automatic fsck.ext4 on x86?
Thanks in advance.
Regards,
Nishant
___
26 matches
Mail list logo
