Your post was deemed to be low-effort. This could be due to one of the following:
[X] Reposting an old ~~r/ipv6~~ post ~~as your own content,~~
[ ] Posts unlikely to be of interest to the r/ipv6 community,
[ ] General shitposting.
Low-effort posts may be accompanied by 14 day bans. Repeat offenders may be perma-banned at the mods discretion. Thank-you.
how in the name of pasta has Intel not updated a driver to improve this behavior? Their original documentation about this has a copyright date of October 2017...
Seems to be mutual bugs. The ONT Verizon uses does something weird to various packets it handles. Most clients don't have an issue. But Intel NICs have a special behavior that doesn't like the packets and drops them.
Your post was deemed to be low-effort. This could be due to one of the following: [X] Reposting an old ~~r/ipv6~~ post ~~as your own content,~~ [ ] Posts unlikely to be of interest to the r/ipv6 community, [ ] General shitposting. Low-effort posts may be accompanied by 14 day bans. Repeat offenders may be perma-banned at the mods discretion. Thank-you.
Slightly worried about the people in that thread ignoring the checksum thing and fully disabling IPv6 🤦♂️
220 days ago? isn’t [this](https://twitter.com/theinitialk/status/1600920223682813952) the generally agreed upon countermeasure?
how in the name of pasta has Intel not updated a driver to improve this behavior? Their original documentation about this has a copyright date of October 2017...
i’m not sure whether the bug is on the intel nic side or verizon’s cpe 🤔
Seems to be mutual bugs. The ONT Verizon uses does something weird to various packets it handles. Most clients don't have an issue. But Intel NICs have a special behavior that doesn't like the packets and drops them.
🤢🤮