Dear Mathias,
I can confirm your patch is working fine. I am able to set a mtu of
1508 on the switch, giving me a mtu of 1500 on the pppoe-wan
connection. I am now able to ping 1472 bytes with the DF flag set. The
patch in question:
https://git.openwrt.org/?p=openwrt/staging/mkresin.git;a=commitdi
Hi,
(Accidentally hit send)
On Fri, May 25, 2018 at 7:06 PM, Kristian Evensen
wrote:
>> I know how to fix the issue by recovery, however, from the responses
>> in the topic on the Lede forum it seems more people are running into
>> this issue. This definitely needs to be fixed before a 18.06 rel
Hi,
On Fri, May 25, 2018 at 7:06 PM, Kristian Evensen
wrote:
>> I know how to fix the issue by recovery, however, from the responses
>> in the topic on the Lede forum it seems more people are running into
>> this issue. This definitely needs to be fixed before a 18.06 release.
>> Is there someone
Hi,
> I know how to fix the issue by recovery, however, from the responses
> in the topic on the Lede forum it seems more people are running into
> this issue. This definitely needs to be fixed before a 18.06 release.
> Is there someone with a mt7621 device that can reproduce the problem,
> and th
On Fri, May 25, 2018 at 1:35 PM, Levente wrote:
> Try upgrading the sysupgrade image using your bootloader.
>
> Lev
>
> On Fri, May 25, 2018 at 1:25 PM, Jaap Buurman wrote:
>> On Fri, May 25, 2018 at 1:14 PM, Jaap Buurman wrote:
>>> On Fri, May 25, 2018 at 12:43 PM, Mathias Kresin wrote:
2
Try upgrading the sysupgrade image using your bootloader.
Lev
On Fri, May 25, 2018 at 1:25 PM, Jaap Buurman wrote:
> On Fri, May 25, 2018 at 1:14 PM, Jaap Buurman wrote:
>> On Fri, May 25, 2018 at 12:43 PM, Mathias Kresin wrote:
>>> 2018-05-25 12:48 GMT+03:00 Jaap Buurman :
Dear Martin, M
On Fri, May 25, 2018 at 1:14 PM, Jaap Buurman wrote:
> On Fri, May 25, 2018 at 12:43 PM, Mathias Kresin wrote:
>> 2018-05-25 12:48 GMT+03:00 Jaap Buurman :
>>> Dear Martin, Mathias and the rest,
>>>
>>> Please scratch my previous message. It seems like the flash was not
>>> successful, and hence
On Fri, May 25, 2018 at 12:43 PM, Mathias Kresin wrote:
> 2018-05-25 12:48 GMT+03:00 Jaap Buurman :
>> Dear Martin, Mathias and the rest,
>>
>> Please scratch my previous message. It seems like the flash was not
>> successful, and hence I was still running the old firmware. However, I
>> have trie
2018-05-25 12:48 GMT+03:00 Jaap Buurman :
> Dear Martin, Mathias and the rest,
>
> Please scratch my previous message. It seems like the flash was not
> successful, and hence I was still running the old firmware. However, I
> have tried flashing 3 different times now, without any luck. The
> router
On Fri, May 25, 2018 at 11:30 AM, Jaap Buurman wrote:
> On Thu, May 24, 2018 at 8:00 PM, Martin Blumenstingl
> wrote:
>> Hello Jaap,
>>
>> On Thu, May 24, 2018 at 12:00 PM, Jaap Buurman wrote:
>>> Dear all,
>>>
>>> I found some additional information in the system log: Thu May 24
>>> 11:38:39 20
On Thu, May 24, 2018 at 8:00 PM, Martin Blumenstingl
wrote:
> Hello Jaap,
>
> On Thu, May 24, 2018 at 12:00 PM, Jaap Buurman wrote:
>> Dear all,
>>
>> I found some additional information in the system log: Thu May 24
>> 11:38:39 2018 kern.err kernel: [83864.729458] eth0: Invalid MTU 1508
>> reque
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 ---
Hello Jaap,
On Thu, May 24, 2018
Dear all,
I found some additional information in the system log: Thu May 24
11:38:39 2018 kern.err kernel: [83864.729458] eth0: Invalid MTU 1508
requested, hw max 1500
Digging deeper, this seems like a message that is spawned by a
function in /net/core.dev.c of the linux kernel:
if (dev->max_mtu
13 matches
Mail list logo
