[02:10] *** km_ has left 
[11:59] *** mercutio has quit IRC (Read error: Connection reset by peer)
[12:02] *** mercutio has joined #arpnetworks
[12:02] *** ChanServ sets mode: +o mercutio
[13:05] <RandalSchwartz> you can now "ping 1.0" and "ping 1.1"
[13:14] <brycec> Huh, I knew CF had 1.0.0.1 but sounds like they're listening on 1.0.0.0 too?
[13:24] <RandalSchwartz> maybe
[16:07] <mercutio> you ping 1.2 too it seems
[16:07] <mercutio> this 1.1.1.1 thing made me learn about 9.9.9.9
[16:42] <mike-burns> ping: no address associated with name
[17:43] *** kevr is now known as `0000000000
[17:43] *** `0000000000 is now known as `100101011100101
[17:43] *** `100101011100101 is now known as kevr
[18:02] <brycec> ping 1.2 \\ PING 1.2 (1.0.0.2) 56(84) bytes of data. \\ 64 bytes from 1.0.0.2: icmp_seq=1 ttl=57 time=10.6 ms
[18:03] <brycec> mike-burns: what were you trying to ping?
[18:03] <mike-burns> 1.0
[18:03] <mike-burns> OpenBSD.
[18:03] <mike-burns> ~% ping 1.0
[18:03] <mike-burns> ping: no address associated with name
[18:03] <brycec> ping 1.0 \\ PING 1.0 (1.0.0.0): 56 data bytes \\ 64 bytes from 1.0.0.0: icmp_seq=0 ttl=61 time=8.804 ms
[18:03] <brycec> ^ OpenBSD ping for me
[18:03] <brycec> (OpenBSD 5.8 but whatever, I know it's old)
[18:03] <mike-burns> 6.2 GENERIC.MP#312
[18:03] <mike-burns> Fascinating.
[18:03] <mike-burns> Oh huh.
[18:04] <mike-burns> I wonder whether they re-wrote ... something.
[18:05] <brycec> Works on 6.0
[18:05] * brycec has a 6.1 host around here somewhere.....
[18:06] <brycec> 6.1 fails
[18:06] <mike-burns> Maybe that happened when they merged ping6(8) into ping(8).
[18:07] <brycec> 6.1 still has ping6 separated (at least as commands go)
[18:07] <brycec> (oh they're hardlinked to the same binary)
[18:07] <mike-burns> Right yeah.
[18:07] <mike-burns> That might be it.
[18:07] <brycec> "ping(8) and ping6(8) are now the same binary and share the engine." https://www.openbsd.org/61.html
[18:08] <mike-burns> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin/ping/ping.c.diff?r1=1.212&r2=1.213 - found it.
[18:08] <brycec> <3 you for finding that mike-burns
[18:08] <mike-burns> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin/ping/ping.c?rev=1.213&content-type=text/x-cvsweb-markup - better link.
[18:08] <mike-burns> Eh neither link is perfect.
[18:09] <brycec> "Only allow standard dot notation for IPv4 addresses." :/
[18:09] <brycec> Is "1.0" not standard dot notation?
[18:09] <mike-burns> Are you about to make me read an RFC?
[18:09] <brycec> lol no
[18:10] <brycec> I have a hard time believing that "standard dot notation" is an RFC term.
[18:11] <brycec> https://en.wikipedia.org/wiki/Dot-decimal_notation seems to be buried in that
[18:11] <BryceBot> Dot-decimal notation :: Dot-decimal notation is a presentation format for numerical data. It consists of a string of decimal numbers, each pair separated by a full stop (dot).  A common use of dot-decimal notation is in information technology where it is a method of writing numbers in octet-grouped base-10 (decimal) numbers separated by dots (full stops). In computer networking, Internet Protocol Version 4 addresses are commonly written using...
[18:13] <brycec> So basically it's an "intermediate representation" that inet_aton was nice enough to decode
[18:13] <brycec> "it also supported intermediate syntax forms of octet.24bits (e.g. 10.1234567; for Class A addresses) and octet.octet.16bits (e.g. 172.16.12345; for Class B addresses)"
[18:15] <mike-burns> Ah yeah, right in the manpage -- you can pass a, a.b, a.b.c, or a.b.c.d to inet_aton(3).
[18:15] <brycec> I'm still boggled to read materials from a time when the Internet (address allocations etc) could be documented in a short RFC https://tools.ietf.org/html/rfc790
[18:15] <brycec> (Yeah, I'm "young", not yet 32 :P )
[18:16] <mike-burns> I love short RFCs.
[18:17] <mike-burns> I was hoping to find a post on tech@ but alas, nothing. I wonder where those OKs came from ...
[18:58] <brycec> ICB I assume
[18:58] <mike-burns> Must be.
[18:58] <mike-burns> How secretive.