mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
To: pflau@us.ibm.COM (Allen Lau)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Subtleties of the 0.0.0.0 netmask (inet_ifa_match)
Date: Fri, 27 Jul 2001 04:32:00 +0400 (MSD)	[thread overview]
Message-ID: <200107270032.EAA00456@mops.inr.ac.ru> (raw)
In-Reply-To: <OFDE143062.D41C03AC-ON85256A95.000B439D@raleigh.ibm.com> from "Allen Lau" at Jul 26, 1 06:15:01 am

Hello!

>   o Does addresses with 0.0.0.0 netmask have scope RT_SCOPE_NOWHERE?

Why?

>   o and does it imply that routing would never route to them?

Even if you set this, it does not imply anything, but that address
will not be used on any packet while automaitc source address selection.


>   o Are there subtle differences between 0.0.0.0 and 255.255.255.255 netmasks?

Subtle? :-) They are on exactly opposite poles.


> The inet_ifa_match function seems to be wrong with 0.0.0.0 netmask.
...
> The 0.0.0.0 netmask matches everything!

Of course. Zero mask matches everything.


> Will there be any routing problems if we use the 0.0.0.0 netmask?

No problems provided you wanted this.
F.e. default route is route with netmask zero, it matches all,
so that all the addresses are routed there.
It is exactly which happens in your setup, but all the addresses
fall to loopback.


Looking at your original purpose, you wanted mask 255.255.255.255.

Alexey

  reply	other threads:[~2001-07-27 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26  2:04 Allen Lau
2001-07-27  0:32 ` Alexey Kuznetsov [this message]
2001-07-27 19:03 Allen Lau
     [not found] <OFA1B2627C.7E519218-ON85256A96.00641020@raleigh.ibm.com >
2001-07-27 19:06 ` kuznet
2001-07-27 21:27   ` Joshua M. Thompson

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=200107270032.EAA00456@mops.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pflau@us.ibm.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

all inboxes | Powered by JetHome®