linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Wietse Venema <wietse@porcupine.org>
Cc: Andi Kleen <ak@suse.de>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Christopher Friesen <cfriesen@nortelnetworks.com>,
	Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
	Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
	linux-net@vger.kernel.org
Subject: Re: ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19
Date: Thu, 6 Sep 2001 21:05:23 +0200	[thread overview]
Message-ID: <20010906210523.A12207@gruyere.muc.suse.de> (raw)
In-Reply-To: <20010906203646.A11741@gruyere.muc.suse.de> <20010906185124.42C37BC06C@spike.porcupine.org>
In-Reply-To: <20010906185124.42C37BC06C@spike.porcupine.org>; from wietse@porcupine.org on Thu, Sep 06, 2001 at 02:51:24PM -0400

On Thu, Sep 06, 2001 at 02:51:24PM -0400, Wietse Venema wrote:
> > On Wed, Sep 05, 2001 at 05:23:26PM -0400, Wietse Venema wrote:
> > > On a more serious note, what portable primitives does Linux offer
> > > to look up all interface IP addresses and their corresponding
> > > netmasks?
> > 
> > man rtnetlink 7
> 
> It's not portable as you may believe.

The man pages are actually came years later than the code due to some accidents.
That doesn't change the existence of the code.

> 
>     [root@redhat52 /root]# man rtnetlink
>     No manual entry for rtnetlink
> 
> This was released only three years ago.
> 
> But it does not matter. The code needs to be written anyway.
> 
> Do you have more to share than RFTM? Pointers to code?

Most prominent example is iproute2. It should be included as source with any 
recent linux distribution. Others are zebra or bird.

-Andi

  reply	other threads:[~2001-09-06 19:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010905170037.A6473@emma1.emma.line.org>
     [not found] ` <20010905152738.C5912BC06D@spike.porcupine.org>
2001-09-05 16:20   ` ioctl SIOCGIFNETMASK: ip alias bug 2.4.9 and 2.2.19 Matthias Andree
2001-09-05 18:25     ` Christopher Friesen
2001-09-05 18:34       ` Alan Cox
2001-09-05 21:23         ` Wietse Venema
2001-09-06 18:36           ` Andi Kleen
2001-09-06 18:51             ` Wietse Venema
2001-09-06 19:05               ` Andi Kleen [this message]
2001-09-07  9:30               ` Henning P. Schmiedehausen
2001-09-07 11:15                 ` Matthias Andree
2001-09-05 22:08 jamal
2001-09-06 15:11 ` kuznet
2001-09-06 20:22 ` Matthias Andree
     [not found] <fa.k8o5i6v.4i8gis@ifi.uio.no>
     [not found] ` <fa.fuk70gv.mk6m09@ifi.uio.no>
2001-09-06 21:19   ` Sam Varshavchik
     [not found] <20010905170037.A6473@emma1.emma.line.org.suse.lists.linux.kernel>
     [not found] ` <20010905152738.C5912BC06D@spike.porcupine.org.suse.lists.linux.kernel>
     [not found]   ` <20010905182033.D3926@emma1.emma.line.org.suse.lists.linux.kernel>
2001-09-05 19:26     ` Andi Kleen
2001-09-06 13:11       ` Matthias Andree
2001-09-06 13:35       ` Andrey Savochkin
2001-09-06 14:04         ` Wietse Venema
2001-09-06 14:21           ` Matthias Andree
2001-09-06 14:51           ` Alan Cox
2001-09-06 14:17         ` Matthias Andree
2001-09-08 12:42     ` Kai Henningsen
2001-09-09  0:37       ` Matthias Andree

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=20010906210523.A12207@gruyere.muc.suse.de \
    --to=ak@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.de \
    --cc=wietse@porcupine.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).