From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 11987 invoked from network); 7 May 2022 23:22:34 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 7 May 2022 23:22:34 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 204169CF86; Sun, 8 May 2022 09:22:32 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 455759CEEF; Sun, 8 May 2022 09:19:59 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=iitbombay-org.20210112.gappssmtp.com header.i=@iitbombay-org.20210112.gappssmtp.com header.b="w9i3frFk"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 82F9E9CEEF; Sun, 8 May 2022 09:19:56 +1000 (AEST) Received: from mail-oi1-f175.google.com (mail-oi1-f175.google.com [209.85.167.175]) by minnie.tuhs.org (Postfix) with ESMTPS id 8DC2A9CEEE for ; Sun, 8 May 2022 09:19:55 +1000 (AEST) Received: by mail-oi1-f175.google.com with SMTP id w194so10306154oie.9 for ; Sat, 07 May 2022 16:19:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20210112.gappssmtp.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WuontrUC8NHKXHKMsJA6dt7JDD/lf/59Zz9kxy7TcrI=; b=w9i3frFkOdLtfnkZ74dTU33bLd++UsoD2v4+zCu0Mx44X47bYZVt1foCThb4oJ0rns NSOGxTIch2CN1ZcOYquC7EdpE6Hnu4inpWShn5ZsLacXXE8kZY3EZ6Z6cvuHaZW5HZyT sK9eml9ARC742YzMybE4iNBwCAD1A1cZ+yZR1gw90cchbDaUPqdNy4QiphsXrpv7xc60 oARPYKS1P2q04w47qdHjdePH8n2VePrgUZ7vVcRSYHGsOG3c/gDrlfxLw4kT2sB9lCRc 8wkyJDOhepoGvyD6dJGtzxIURwh5I/Gm5eEvtbPmMb4KEoYiFU+Rnc2GQtxG5uGt8jJW /5yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=WuontrUC8NHKXHKMsJA6dt7JDD/lf/59Zz9kxy7TcrI=; b=H2z8nhITSAevcG0GjvhOaxmDpQDM44gBNJoWfkVtE/dRdoBOnvWs+2U1abvGWI0/a2 bDlpmramfOfFLxYqqs99UpiP91919Hs11gm1NeV5QolT26dadoRR3sJAQ+1JlknJCq7i mVmUx7BmFLHbEuHk0kmI/vCTD/WtgBgydV07EuHJpG/+8J9qS7A67mavuGvEwgy7pfp+ mnpffe1f7SYRnPLUrbAK9uzb5W++uQS31eEYcIdjB+gdrZRnLr/d3KUG0TsTGHc/966v kg7beB82UvvsyJD5U1H56aFxj2eLzIz+P0uj6+9nLiHeZ/elTs9t6sy/kgKvC28WdLEy Nliw== X-Gm-Message-State: AOAM532gMgwuEyScG46XZ9NUvY0fyl5SGEmL5aWlxT30AyTKkE0iYQfp Z5tgeXhmmO3ek6aCEg+6Secprg== X-Google-Smtp-Source: ABdhPJx4wVWcYhbLpNg9UczBzfG0TfSd1gL4r4cjv0lz83v7qofsgcvfOsFOZac5CSjzbjToqT1mzg== X-Received: by 2002:a05:6808:1b11:b0:326:4608:4504 with SMTP id bx17-20020a0568081b1100b0032646084504mr4615854oib.145.1651965594763; Sat, 07 May 2022 16:19:54 -0700 (PDT) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id h15-20020a056870538f00b000e686d13881sm2844000oan.27.2022.05.07.16.19.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 May 2022 16:19:54 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) From: Bakul Shah In-Reply-To: Date: Sat, 7 May 2022 16:19:53 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Warner Losh X-Mailer: Apple Mail (2.3696.80.82.1.1) Subject: Re: [TUHS] conventions around zero padding in ip4 X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" On May 7, 2022, at 12:14 PM, Warner Losh wrote: >=20 > 10.2 is ambiguous. In a network context, it means, typically, = 10.2.0.0/16 (though your mileage may vary). > In a host context, it means 10.0.0.2. It's this confusion that has = lead to many efforts > to outright kill this notation. 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 =3D=3D 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 =3D=3D = 1000000) ping 1000000001 tries to ping 59.154.202.1 (59*2^24+154*2^16+202*2^8+1) ping 300.300 tries to ping 23.217.138.110 (I haven't worked this out! = Prob. a bug) So the last number is treated as the host number on a given net. This may have some sense in the classful network world but is very confusing in the CIDR world.