From: "Pali Rohár" <pali@kernel.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] netdevice.7: Update documentation for SIOCGIFADDR SIOCSIFADDR SIOCDIFADDR
Date: Sat, 2 Jan 2021 19:36:04 +0100 [thread overview]
Message-ID: <20210102183604.ocbhegclbkugm45l@pali> (raw)
In-Reply-To: <20210102181054.pspqz7tj24wviu5i@pali>
On Saturday 02 January 2021 19:10:54 Pali Rohár wrote:
> Hello!
>
> On Saturday 02 January 2021 19:04:06 Alejandro Colomar (man-pages) wrote:
> > I've seen there's ifr_ifindex too (see SIOCGIFNAME).
> > Can it be used in the same way as ifr6_ifindex?
>
> Sorry, I do not know too. In all applications I saw that they are using
> ifr_name for IPv4 stuff.
>
> This needs to be tested if ifr_ifindex instead of ifr_name works for
> specifying IPv4 address.
Now I can answer, no, it cannot be used. ifr_ifindex is part of union
structure where is also ifr_addr. So you can specify either ifr_ifindex
or ifr_addr, but not both fields at the same time.
Therefore network interface for IPv4 address can be specified only via
ifr_name.
next prev parent reply other threads:[~2021-01-02 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 14:02 [PATCH] netdevice.7: Update documentation for SIOCGIFADDR SIOCSIFADDR SIOCDIFADDR Pali Rohár
2021-01-02 18:04 ` Alejandro Colomar (man-pages)
2021-01-02 18:10 ` Pali Rohár
2021-01-02 18:36 ` Pali Rohár [this message]
2021-01-02 18:39 ` [PATCH v2] " Pali Rohár
2021-01-10 16:38 ` Pali Rohár
2021-01-10 19:57 ` Alejandro Colomar (man-pages)
2021-01-12 19:26 ` Pali Rohár
2021-01-16 0:41 ` Alejandro Colomar (man-pages)
2021-01-16 22:35 ` Pali Rohár
2021-01-11 8:13 ` Michael Kerrisk (man-pages)
2021-01-10 17:47 ` Dmitry V. Levin
2021-01-12 17:51 ` Pali Rohár
2021-01-16 22:36 ` [PATCH v3] " Pali Rohár
2021-01-19 20:18 ` Alejandro Colomar (man-pages)
2021-01-27 19:29 ` Pali Rohár
2021-01-28 14:05 ` Alejandro Colomar (man-pages)
2021-01-28 14:04 ` Alejandro Colomar (man-pages)
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=20210102183604.ocbhegclbkugm45l@pali \
--to=pali@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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).