From: Krzysztof Halasa <khc@pm.waw.pl>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Stephen Hemminger <shemminger@vyatta.com>,
Krzysztof Oledzki <ole@ans.pl>,
netdev@vger.kernel.org
Subject: Re: Error: an inet prefix is expected rather than "0/0".
Date: Wed, 15 Oct 2008 20:52:47 +0200 [thread overview]
Message-ID: <m3y70pn11c.fsf@maximus.localdomain> (raw)
In-Reply-To: <1224086831.3984.196.camel@achroite> (Ben Hutchings's message of "Wed\, 15 Oct 2008 17\:07\:10 +0100")
Ben Hutchings <bhutchings@solarflare.com> writes:
> It's a Berkeley extension which spread via BSD and its inet_aton()
> function. I don't believe it's specified in any RFC.
You may be right, I won't start searching now :-)
Anyway it was like that for years and I guess we shouldn't change it
(except perhaps for removing).
> No, a single number is treated by inet_aton() as a 32-bit address, so 10
> is equivalent to 0.0.0.10.
Hmm, I remember some routes being used without a dot, as a single
number, but OTOH you're right, it was also possible to ping
12345678. Perhaps 10 -> 10.0 was specific to something rather than
used generally, I don't know.
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-10-15 18:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 21:05 Error: an inet prefix is expected rather than "0/0" Krzysztof Oledzki
2008-10-08 21:32 ` Krzysztof Oledzki
2008-10-14 14:01 ` Herbert Xu
2008-10-14 17:46 ` Stephen Hemminger
2008-10-14 19:15 ` Krzysztof Oledzki
2008-10-14 19:18 ` Stephen Hemminger
2008-10-14 19:38 ` Ben Hutchings
2008-10-14 21:52 ` Patrick McHardy
2008-10-14 21:54 ` Patrick McHardy
2008-10-15 1:46 ` Herbert Xu
2008-10-15 15:35 ` Krzysztof Halasa
2008-10-15 16:07 ` Ben Hutchings
2008-10-15 18:52 ` Krzysztof Halasa [this message]
2008-10-27 17:39 ` Stephen Hemminger
2008-10-28 1:51 ` Herbert Xu
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=m3y70pn11c.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=bhutchings@solarflare.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
--cc=shemminger@vyatta.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).