From: "Bill Sommerfeld via illumos-developer" <developer@lists.illumos.org>
To: developer@lists.illumos.org
Subject: [developer] [REVIEW] 16585 ping ignores ipv6 scope id in target address
Date: Mon, 28 Oct 2024 12:43:23 -0700 [thread overview]
Message-ID: <3d9ac932-06d4-4d97-bd8e-4bbdd574155f@hamachi.org> (raw)
Issue: https://www.illumos.org/issues/16585
CR: https://code.illumos.org/c/illumos-gate/+/3755
Diff:
https://code.illumos.org/~diff/91dc2df4483aaa88d9a9bc35b73956d795bcf4d0
Next in my queue of ipv6 scope fixes, the "ping" command:
Ping accepts addresses with attached scope, as in this link-local
multicast "all nodes" ping:
ping ff02::1%lan0
but discards the scope, leading to potential confusion (it sends the
ping out the wrong interface). The fix generally involves deferring
disassembly of the "struct sockaddr_in6" so the scope is available
alongside the address.
Also along for the ride (and, alas, dominating the diffs) are some
other source cleanups:
- Printing the scope tag for received traffic.
- Printing a warning when a scoped address is used along with the
"-i" option (another way to specify a specific output interface).
- Moving function prototype declarations for external functions from
ping*.c to ping.
- Restructuring the "pr_name" function into address-family-specific
variants to reduce the amount of casting required.
- cstyle whitespace fixes
Thanks in advance for your review.
- Bill
------------------------------------------
illumos: illumos-developer
Permalink: https://illumos.topicbox.com/groups/developer/T935428f17dc3d883-M02a7f11076aad391c565761a
Delivery options: https://illumos.topicbox.com/groups/developer/subscription
reply other threads:[~2024-10-28 19:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d9ac932-06d4-4d97-bd8e-4bbdd574155f@hamachi.org \
--to=developer@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).