(the AS holder is http://instituut.net/~job/, to those uninitiated - I had to double check my comment)
Sir, I take my many virtual hats off to you.
Is that tmux, with some ip config on the left, and an empty shell (with a fortune) on the right?
Do the sunflowers represent anything? :)
traceroute -I -q 1 trh.milek7.pl
8 points.22 (2001:470:1f13:202:c000::16) 20.135 ms
9 I----------I (2001:470:1f13:202:8000::) 20.071 ms
10 I----------I (2001:470:1f13:202:8000::) 20.108 ms
11 I----------I (2001:470:1f13:202:8000::) 20.109 ms
12 I----------I (2001:470:1f13:202:8000::) 20.113 ms
13 I---XXXX---I (2001:470:1f13:202:8000:0:333:3000) 20.132 ms
14 I----------I (2001:470:1f13:202:8000::) 20.120 ms
15 I----------I (2001:470:1f13:202:8000::) 20.098 ms
16 I----------I (2001:470:1f13:202:8000::) 20.097 ms
17 I----------I (2001:470:1f13:202:8000::) 17.422 ms
18 I----------I (2001:470:1f13:202:8000::) 17.262 ms
19 I----------I (2001:470:1f13:202:8000::) 17.280 ms
20 I----------I (2001:470:1f13:202:8000::) 17.279 ms
21 I----------I (2001:470:1f13:202:8000::) 17.267 ms
22 I----------I (2001:470:1f13:202:8000::) 17.268 ms
23 I----------I (2001:470:1f13:202:8000::) 17.211 ms
24 I----------I (2001:470:1f13:202:8000::) 17.193 ms
25 I----------I (2001:470:1f13:202:8000::) 17.187 ms
26 I---O------I (2001:470:1f13:202:8000::1000) 17.219 ms
27 I---OO--O--I (2001:470:1f13:202:8000:0:1001:1000) 17.306 ms
28 IOOOOO--OOOI (2001:470:1f13:202:8000:11:1001:1111) 17.036 ms
29 IIIIIIIIIIII (2001:470:1f13:202::) 16.975 ms
traceroute -m 50 bad.horse
# traceroute -I -q 1 trh.milek7.pl
connect: Network is unreachable
9 ae-19.sayonara-todd.r04.sttlwa01.us.bb.gin.ntt.net (184.108.40.206) 17.225 ms 17.166 ms 17.171 ms
10 ae-5.sayonara-todd.r21.sttlwa01.us.bb.gin.ntt.net (220.127.116.11) 16.257 ms 16.156 ms 16.101 ms
11 ae-3.sayonara-todd.r23.snjsca04.us.bb.gin.ntt.net (18.104.22.168) 33.097 ms 33.125 ms 31.566 ms
12 ae-7.sayonara-todd.r23.dllstx09.us.bb.gin.ntt.net (22.214.171.124) 69.840 ms 69.764 ms 69.763 ms
13 ae-6.sayonara-todd.r10.dllstx09.us.bb.gin.ntt.net (126.96.36.199) 69.634 ms 74.424 ms 72.319 ms
14 ae-0.sayonara-todd.a01.dllstx09.us.bb.gin.ntt.net (188.8.131.52) 74.050 ms 74.046 ms 74.035 ms
3 ae-13.sayonara-todd.r05.plalca01.us.bb.gin.ntt.net (2001:418:0:5000::bae) 1.324 ms 1.307 ms 1.205 ms
4 ae-15.sayonara-todd.r02.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::172) 2.505 ms
5 ae-10.sayonara-todd.r23.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::cd) 2.091 ms 2.067 ms
6 ae-7.sayonara-todd.r23.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::1fa) 38.386 ms 39.757 ms 38.312 ms
7 ae-6.sayonara-todd.r10.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::1c1) 41.586 ms
8 ae-1.sayonara-todd.a02.dllstx09.us.bb.gin.ntt.net (2001:418:0:2000::135) 51.986 ms
These guys are from GIN and are some of the best people I've had the pleasure of working with, both on a personal and professional level.
At least't that's my hunch. We could check the same monitor though :)
I couldn't care less about the IPv6 prefixes, but the IPv4 ones are all /24s made from 184.108.40.206/16, which is registered to NTT (AS2914). 209.24/16 is publicly announced (and has been for a very long time), and is routed through NTT Amsterdam routers.
I haven't looked at BGPlay to review all the data, but it looks like many of the /24s that make up that /16 were individually announced through AS15562, then later withdrawn, gradually over 4 months, to make said graph. I would hope this would be unused v4 space. That AS announced almost 98% of a /16 (probably 209.24/16): https://stat.ripe.net/AS15562#tabId=routing
Another user voiced their concerns, particularly if it was actively used: https://news.ycombinator.com/item?id=14621859 -- there's no way any of us could know this; NTT would be authoritative, and jwhois -h rwhois.gtt.net.net -p 4321 220.127.116.11/16 doesn't give any clues.
While the antic made me smirk, it doesn't (publicly) "look good" when we're living in a world that lacks (or has greatly limited) v4 space. What this says is: "NTT has a /16 they're fooling around with publicly", even though it (presumably) is harmless.
NTT is one of the larger Tier 1 ISPs. Having some unused IPv4 address space is a good thing when you're such a huge network operator -- it means you can dedicate some globally-routed IPs for testing/prototyping/renumbering and also have some extra IP space for new devices. Given what happens to ISPs that run out of IPs, I am frankly glad NTT has enough free IPs to fool around with nyan cats.
If NTT was dragging its feet on IPv6, then yeah, such a stunt might look awkward, but NTT hasn't -- they've been on the forefront of IPv6 for a while. AFAICT they were the first to offer commercial IPv6 connectivity and their global IP network has been native IPv4/IPv6 since 2004, and anecdotally I see their routers in my IPv6 traceroutes all the time.
While this may be a lot for typical users, it's not huge for a large IT company. You know that HP has 2 /8s, right?
I'm also aware many of those places have either refused to relinquish space, or have done so but have no more to give back. Quoting Doug Barton, former manager at IANA, July 2015: "... Many orgs did give back space and/or swap allocations. But that well ran dry long ago" (if you need a reference link for that quote, let me know).
A recent example of relinquishing space is 18.104.22.168/8 (previously MIT) as of April 2017, which now has many /16 and /24 segments delegated to companies such as Comcast (ex. 22.214.171.124/16), Amazon (ex. 126.96.36.199/16), and Akamai (ex. 188.8.131.52/24), while many larger portions still reside with MIT (ex. 184.108.40.206/12, 220.127.116.11/9, 18.104.22.168/16).
My point of giving examples: note all the /16s. If you need further examples, refer to IANA's Recovered Address Space document and note the subnet sizes (many are much smaller than a /16): https://www.iana.org/assignments/ipv4-recovered-address-spac...
Every little bit counts.
Jump to 5:20 to hear Aphex Twin's face.
Here is a boeing test flight that drew out the boeing logo across the united states:
(Editted to add See also https://web.archive.org/web/20130917012514/http://www.chipwo...)
This interface is the historical bgp announcements for this particular ASN. The X access is time. The Y axis is ip address blocks.
If you want to play with BGP, download Quagga - its interface emulates the Cisco router interface. Documentation is poor but you can just reference Cisco docs.
1. It allows me to understand that I am not the only one who doesn't understand the terminology involved, allowing the discussion to be more educational and inclusive.
2. Sometimes searching for terminology is ambiguous and without prior knowledge of the subject domain, can result in lack of confirmation as to whether the definition is the same as the one in the article.
3. For one person to ask here and have it answered, can save 100 people having to search for themselves when reading the comments.
Better yet, as I see people do around here from time to time, go read a brief synopsis and then post a "For other people who didn't know what BGP was: BGP is ....". I'm not for creating a hostile stuck up community but rewarding pure laziness seems pointless to me.
"Be civil. Don't say things you wouldn't say in a face-to-face conversation. Avoid gratuitous negativity."
There are things people don't know. I find xkcd's attitude a useful one to keep in mind:
Or is it because I'm behind a corporate firewall....
this shows the routing history of the prefixes originated by AS 8283 - and their observed reachability
Still, pretty neat. :)
On a more serious note, I've been watching IPv6 "rolling out" since 2004 (which is when I had an active role in mobile network planning), and I'm somewhat saddened that we haven't yet been able to switch over completely (even if it is somewhat more awkward to shout IPv6 addresses across the room, which was one of the arguments one of my colleagues had against it.)
To clarify those of you who haven't worked in a telco core: You can't rely on DNS to configure core network gear. EVERYTHING of consequence is done using IP addresses, DNS is a convenience/comfort service for outer layers and end users.
The question is whether or not the /16 (of which most of the advertised/withdrawn /24s make up) was used by actual devices, or if it's address space NTT has yet to use. If it is assigned to NTT but unused space, then effectively no harm done. If it's actually used IP space, then that would be very inappropriate.