From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] conventions around zero padding in ip4
Date: Sun, 08 May 2022 11:28:46 +0100 [thread overview]
Message-ID: <20220508102846.55F3222158@orac.inputplus.co.uk> (raw)
In-Reply-To: <FA943880-F763-4548-A7AC-0BDB9991E731@iitbombay.org>
Hi Bakul,
> On FreeBSD:
> ping 10.2 tries to ping 10.0.0.2 and
> ping 192.168.300 tries to ping 192.168.1.44 (1*2^8+44 == 300)
> ping 10.2.300 tries to ping 10.2.1.44
> ping 192.1000000 tries to ping 192.15.66.64 (15*2^15+66*2^8+64 == 1000000)
> ping 1000000001 tries to ping 59.154.202.1 (59*2^24+154*2^16+202*2^8+1)
Ditto here on Linux with GNU libc.
> ping 300.300 tries to ping 23.217.138.110 (I haven't worked this out! Prob. a bug)
It doesn't parse as a numeric address. Given it's a.bcd, based on the
notation in my other email, the first 300 is ‘a’ but is bigger than one
byte so is invalid. Yes, a bug.
$ ping 300.300
ping: 300.300: Name or service not known
$
--
Cheers, Ralph.
next prev parent reply other threads:[~2022-05-08 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 16:14 ron minnich
2022-05-07 16:38 ` Bakul Shah
2022-05-07 16:48 ` Erik E. Fair
2022-05-07 18:49 ` Steffen Nurpmeso
2022-05-07 19:14 ` Warner Losh
2022-05-07 19:50 ` ron minnich
2022-05-07 19:57 ` ron minnich
2022-05-07 23:19 ` Bakul Shah
2022-05-07 23:49 ` Warner Losh
2022-05-08 10:28 ` Ralph Corderoy [this message]
2022-05-08 5:21 ` jason-tuhs
2022-05-08 10:22 ` Ralph Corderoy
2022-05-09 14:08 ` Steffen Nurpmeso
2022-05-10 10:49 ` Ralph Corderoy
2022-05-07 19:43 Noel Chiappa
2022-05-08 14:54 ` Michael Kjörling
2022-05-09 16:14 Noel Chiappa
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=20220508102846.55F3222158@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--cc=tuhs@minnie.tuhs.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).