Linus Lüssing writes:
> Currently there are mobile devices (e.g. Android) which are not able
> to receive and respond to MLD Queries reliably because the Wifi driver
> filters a lot of ICMPv6 when the device is asleep - including
> MLD. This in turn breaks IPv6 communication when MLD Snooping is
Sven Eckelmann writes:
> On Monday, 17 August 2020 10:39:00 CEST Bjørn Mork wrote:
>> Linus Lüssing writes:
> [...]
>> This is not a bug. They are deliberately breaking IPv6 because they
>> consider this a feature. You should not try to work around such issues.
>> It is a fight you cannot win.
Hello guys hope you are doing good! we are Bigbudsupply we grow and sell
the best medical marijuana product, we are looking for long time customers,
you can Email us /bigbudsupp...@gmail.com
Text/+14432672189
Looking forward to working with you guys
On Tue, 11 Aug 2020 at 18:30 syzbot <
On Monday, 17 August 2020 10:39:00 CEST Bjørn Mork wrote:
> Linus Lüssing writes:
[...]
> This is not a bug. They are deliberately breaking IPv6 because they
> consider this a feature. You should not try to work around such issues.
> It is a fight you cannot win. Any workaround will only
syzbot has found a reproducer for the following issue on:
HEAD commit:fb893de3 Merge tag 'tag-chrome-platform-for-v5.9' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1742b31c90
kernel config:
Hello,
syzbot found the following issue on:
HEAD commit:86cfccb6 Merge tag 'dlm-5.9' of git://git.kernel.org/pub/s..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1419de8a90
kernel config: https://syzkaller.appspot.com/x/.config?x=bcf489e08c9b8c5e
When using the ETF Qdisc in combination with a bridge and DSA, then all packets
gets dropped due to invalid time stamps. The setup looks like this:
Transmit path:
Application -> bridge (br0) -> DSA slave ports (lan0, lan1) -> ETF Qdisc
-> ethernet (eth0)
The user space application
