linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: wietse@porcupine.org (Wietse Venema)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Christopher Friesen <cfriesen@nortelnetworks.com>,
	Matthias Andree <matthias.andree@stud.uni-dortmund.de>,
	Wietse Venema <wietse@porcupine.org>,
	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: Wed, 5 Sep 2001 17:23:26 -0400 (EDT)	[thread overview]
Message-ID: <20010905212326.1B82DBC06C@spike.porcupine.org> (raw)
In-Reply-To: <E15ehVC-0006Rx-00@the-village.bc.nu> "from Alan Cox at Sep 5, 2001 07:34:18 pm"

On a more serious note, what portable primitives does Linux offer
to look up all interface IP addresses and their corresponding
netmasks?

The primitives used in Postfix work on all supported systems, except
for Linux where they work partially.

Portability is a relative thing - it would be wonderful already if
your primitive supports the past three years of kernel releases.

	Wietse

Alan Cox:
> > > the mask for the requested address. This doesn't matter as long as
> > > eth0:0-style aliases are configured with ifconfig, but it does matter as
> > > soon as ip comes into play and both addresses are assigned to eth0
> > > rather than eth0 and eth0:0.
> > 
> > I think the silence you are hearing from the lkml is a bunch of people thinking
> > "Oh, crap!".
> 
> Actually its probably a bunch of people thinking "I wonder if someone else
> forwarded this to netdev@oss.sgi.com"
> 


  reply	other threads:[~2001-09-05 21:23 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 [this message]
2001-09-06 18:36           ` Andi Kleen
2001-09-06 18:51             ` Wietse Venema
2001-09-06 19:05               ` Andi Kleen
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=20010905212326.1B82DBC06C@spike.porcupine.org \
    --to=wietse@porcupine.org \
    --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 \
    /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).