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 Mon, 9 Oct 2017 01:31:29 +0300
On Mon, Oct 9, 2017 at 12:00 AM, Nerijus Baliunas
wrote:
> On Sun, 8 Oct 2017 23:44:58 +0300 Sergey Ryazanov
> wrote:
>> > I assigned IP with a command
>> > ip a a 192.168.0.10/24 dev eth0
>> >
>> > but ping from PC does not answer.
>>
>>
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 Sun, 8 Oct 2017 23:44:58 +0300
On Sun, Oct 8, 2017 at 11:12 PM, Nerijus Baliunas
wrote:
> I assigned IP with a command
> ip a a 192.168.0.10/24 dev eth0
>
> but ping from PC does not answer.
>
> ifconfig -a shows a few RX and TX packets:
> eth0 Link encap:Ethernet HWaddr 00:18:39:21:0D:AE
>
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 Tue, 3 Oct 2017 03:27:21 +0300
Citeren Paul Blazejowski :
Will this also work on WNDR3700v4?
I guess so, the image for the WNDR3700v4 is the same as for the
WNDR4300v1. I can confirm the version from Hauke's staging tree works
on the latter, so it is likely that it will also work for the
One usecase not currently supported is managing dnsmasq ipset lists
through LuCI, which enables anyone to maintain them. With ipset-dns
this is easy to do using LuCI "dhcp.@dnsmasq[0].server" entries.
If it was added, I think ipset-dns could be deprecated.
On 10/08/2017 09:25 PM, p.wa...@gmx.at wrote:
> Hi Hauke,
>
>> When the kernel gets uncompressed and is bigger than
>> BZ_TEXT_START - LOADADDR it overwrote the loader which was currently
>> uncompressing
>> it and made the board crash.
>
> Currently, BZ_TEXT_START - LOADADDR = 0x8040 -
Citeren p.wa...@gmx.at:
Hi Hauke,
When the kernel gets uncompressed and is bigger than
BZ_TEXT_START - LOADADDR it overwrote the loader which was
currently uncompressing
it and made the board crash.
Currently, BZ_TEXT_START - LOADADDR = 0x8040 - 0x80001000 =
3FF000 = 4190208 bytes
Hi Hauke,
> When the kernel gets uncompressed and is bigger than
> BZ_TEXT_START - LOADADDR it overwrote the loader which was currently
> uncompressing
> it and made the board crash.
Currently, BZ_TEXT_START - LOADADDR = 0x8040 - 0x80001000 = 3FF000 =
4190208 bytes
Today's trunk brcm47xx
Thanks.
I compiled kernel 4.9 for my old WNDR3700v2 and WNDR3800. Both routers booted
ok and seem to work ok at the first glance.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Citeren Hauke Mehrtens :
On 10/08/2017 01:31 PM, Andrey Jr. Melnikov wrote:
Arjen de Korte wrote:
Citeren Hauke Mehrtens :
This adds support for kernel 4.9.
Please test this, I am lacking especially NAND devices.
The most
On 10/08/2017 08:29 AM, Hauke Mehrtens wrote:
> On 10/08/2017 05:06 PM, Hauke Mehrtens wrote:
>> The boot process on a WRT54GL works the following way:
>> 1. CFE gets loaded by the boot rom from flash
>> 2. CFE loads the loader from the flash and gzip uncompresses it
>> 3. CFE starts the loader
Hi Stijn,
That was quick. Thanks!
Jason
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
By default we are reusing the stack provided by CFE, like it is intended
by CFE. On my WRT54GS it is located at 0x8043BF30, so a big kernel image
could overwrite it. Relocate it to a different memory region which is
still under the 8MB RAM, but in the higher area. We only need this
memory region
On 07-10-17 14:43, Hauke Mehrtens wrote:
> What is your opinion on this topic? Am I missing some arguments?
> Currently I would prefer solution 3 going with kernel 4.9 and 4.14.
I actually preferred to have a 2nd major release in 2017, using only
kernel 4.9, and then a 3rd major release early 2018
On 25-09-17 18:43, Stijn Tintel wrote:
> On 25-09-17 00:20, Baptiste Jonglez wrote:
>> On 24-09-17, Stijn Tintel wrote:
>>> My bad. When we update a package, we bump the version in the Makefile
>>> and remove the current hash, then run "make package/foo/dowload; make
>>> package/foo/check
The boot process on a WRT54GL works the following way:
1. CFE gets loaded by the boot rom from flash
2. CFE loads the loader from the flash and gzip uncompresses it
3. CFE starts the loader
4. The loader stores the FW arguments and relocates itself to
BZ_TEXT_START (now 0x8060)
5. The
Hello Mathias,
On Thu, Oct 5, 2017 at 9:13 AM, Mathias Kresin wrote:
> At the moment I'm reviewing https://github.com/lede-project/source/pull/1399
[skipped]
> The PR drops any hardcoded board params from mktplinkfw2.c in favour of
> commandline arguments, to provide only one
On 08-10-17 16:20, Jason A. Donenfeld wrote:
> On Sun, Oct 8, 2017 at 3:04 PM, Jason A. Donenfeld wrote:
>> In that case, I'll take a closer look at the patches LEDE ships for
>> the package and merging them into the upstream repo.
> If you don't wind up removing that, future
On Sun, Oct 8, 2017 at 3:04 PM, Jason A. Donenfeld wrote:
> In that case, I'll take a closer look at the patches LEDE ships for
> the package and merging them into the upstream repo.
If you don't wind up removing that, future packages won't need to
include that patch any longer:
On 10/08/2017 01:31 PM, Andrey Jr. Melnikov wrote:
> Arjen de Korte wrote:
>> Citeren Hauke Mehrtens :
>
>>> This adds support for kernel 4.9.
>>> Please test this, I am lacking especially NAND devices.
>>>
>>> The most recent version of these patches
On Sun, Oct 8, 2017 at 3:02 PM, Florian Fainelli wrote:
> Still using ipset-dns here, thanks for the reminder, I should probably
> migrate to dnsmasq now to achieve the same goals. There may be other
> users out there though ;)
Cool, okay, good to know!
In that case, I'll
Hi,
On 10/07/2017 04:48 PM, Jason A. Donenfeld wrote:
> Hey,
>
> I'm upstream on the ipset-dns project:
> https://git.zx2c4.com/ipset-dns/about/
>
> It's a part of a core LEDE repo:
> https://git.lede-project.org/?p=source.git;a=tree;f=package/network/services/ipset-dns
>
> Pretty soon after I
Hello Hauke,
On 07.10.2017 13:43, Hauke Mehrtens wrote:
[...]
What is your opinion on this topic? Am I missing some arguments?
Currently I would prefer solution 3 going with kernel 4.9 and 4.14.
I prefer option 3 as well.
--
Cheers,
Piotr
___
Hi Yangbo,
I am seeing the following build problem in the layerscape target in the
master tree.
I fixed the missing config symbol problem, found by the build bots, but
they will run into this in the next run. I saw this on the 64bit and the
32 bit build.
Refresh patches.
Compile-tested for: ar71xx Archer C7 v2
Run-tested on: ar71xx Archer C7 v2
Signed-off-by: Kevin Darbyshire-Bryant
---
include/kernel-version.mk | 4 ++--
Arjen de Korte wrote:
> Citeren Hauke Mehrtens :
> > This adds support for kernel 4.9.
> > Please test this, I am lacking especially NAND devices.
> >
> > The most recent version of these patches can be found here:
> >
Citeren Hauke Mehrtens :
This adds support for kernel 4.9.
Please test this, I am lacking especially NAND devices.
The most recent version of these patches can be found here:
https://git.lede-project.org/?p=lede/hauke/staging.git;a=shortlog;h=refs/heads/ar71xx
Hauke Mehrtens
29 matches
Mail list logo