It is reasonable for routers not to forward, but drop them (you cannot
reject them with ICMP unreachable, as the sender address will never be
reachable). Although, that involves a check and I assume that the
routers in large transit networks do not have such checks enabled to
save CPU cycles.
Interesting thought.
I would assume such drop rules are implemented in TCAM
On 2026-08-06 16:07, Marco Moock wrote:
Am 06.08.26 um 13:08 schrieb Michael Kafka via ripe-atlas:
I'm surprised to see an IPv6 packet with link local scope source and a
global scope destination.
According to RFC3848 and RFC6724 this should not happen (prefer the
larger scope, when choosing a source address from several candidates).
True, but some machines do not implement that properly and generate such
message. Some may also do that intentionally for attacks etc.
It is reasonable for routers not to forward, but drop them (you cannot
reject them with ICMP unreachable, as the sender address will never be
reachable). Although, that involves a check and I assume that the
routers in large transit networks do not have such checks enabled to
save CPU cycles.
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the
email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
--
NetCaT GmbH, Bennogasse 13/5, 1080 Wien
FN 433437 h, Handelsgericht Wien, UID: ATU69635335
GF: Michael Kafka, Georg Kraus
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
