All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Efros <ben@xgendev.com>
To: Simon Lodal <simonl@parknet.dk>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: RFC: Partial IP4 syntax
Date: Tue, 28 Sep 2004 20:56:19 -0700	[thread overview]
Message-ID: <415A3263.7080708@xgendev.com> (raw)
In-Reply-To: <415A12AE.1060901@parknet.dk>

Simon Lodal wrote:

> Examples:
> 10 = 10.0.0.0/8

<SNIP>

> Iknow IP address syntax should not change every day. But this will not 
> break or exclude old syntax. I do not see it clashing with 
> other/future syntax.

Wrong.  IP numbers can also be written in 32-bit unsigned notation.  In 
your first example:
10 being  10.0.0.0/8
10 is actually treated as unsigned 32bit int, meaning you're address is 
actually 0.0.0.10
Try this command and see for yourself:
"ping 5000"
Notice how ping is actually sending to "0.0.19.136" ?

This is done because 32-bit addresses should be representable as a 32bit 
number and not just as a string representation of the address for a 
variety of reasons.

Unfortunately your idea would break a LOT of very useful tools and ways 
of representing valid ip numbers.

Ben

  reply	other threads:[~2004-09-29  3:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29  1:41 RFC: Partial IP4 syntax Simon Lodal
2004-09-29  3:56 ` Ben Efros [this message]
2004-09-29  5:42   ` Simon Lodal
2004-09-29  8:55     ` Henrik Nordstrom
2004-09-29 16:38       ` Simon Lodal
2004-09-29 17:05         ` Henrik Nordstrom
2004-09-29 18:45           ` Simon Lodal
2004-09-29 19:11             ` Cedric Blancher
2004-09-29 22:41               ` Simon Lodal
2004-09-29 19:39             ` Henrik Nordstrom
2004-09-29  8:50 ` Henrik Nordstrom
2004-09-29 16:37   ` Simon Lodal
2004-09-29 16:54     ` Henrik Nordstrom
2004-09-29 18:21       ` Simon Lodal
2004-09-29 19:30         ` Henrik Nordstrom

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=415A3263.7080708@xgendev.com \
    --to=ben@xgendev.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=simonl@parknet.dk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.