This sort of endearing Internet-scale thing reminds me of how NTT changes their reverse DNS's ( https://mailman.nanog.org/pipermail/nanog/2016-February/0841... ). There's other vanity reverse-DNS tricks that you can see in traceroutes, but this is done with a global-scale IPv4/IPv6 network that actually is carrying a lot of customer traffic. Try "traceroute ntt.net" now, you'll see hops like: 9 ae-19.sayonara-todd.r0…
After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
31–40 of 114 posts
Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#32I am as curious as the next guy but just a link to a random graph and no explanation... Uninteresting
Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#33This sort of endearing Internet-scale thing reminds me of how NTT changes their reverse DNS's ( https://mailman.nanog.org/pipermail/nanog/2016-February/0841... ). There's other vanity reverse-DNS tricks that you can see in traceroutes, but this is done with a global-scale IPv4/IPv6 network that actually is carrying a lot of customer traffic. Try "traceroute ntt.net" now, you'll see hops like: 9 ae-19.sayonara-todd.r0…
Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#34OMG. The ingenuity (and geek level) of achieving this with something that is essentially invisible to 99.99999% of the human race (even most network admins) and planning ahead to do this is... indescribable. (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.
Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#35Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#36Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#37This sort of endearing Internet-scale thing reminds me of how NTT changes their reverse DNS's ( https://mailman.nanog.org/pipermail/nanog/2016-February/0841... ). There's other vanity reverse-DNS tricks that you can see in traceroutes, but this is done with a global-scale IPv4/IPv6 network that actually is carrying a lot of customer traffic. Try "traceroute ntt.net" now, you'll see hops like: 9 ae-19.sayonara-todd.r0…
What about those domains says vanity reverse DNS to you? They look like bog standard location-named routers to me.
Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#38In similar category of doing fun things with internet tools, you can play tetris on IPv6 traceroute: traceroute -I -q 1 trh.milek7.pl Game is controlled by appending chars into subdomain: w – rotate, s – drop, a – move left, d – move right. Example: tracerouting wwddds.trh.milek7.pl rotates 2x, moves right 3x and drops piece. After dropping to request new piece it is required to traceroute trh.milek7.pl without comma…
# traceroute -I -q 1 trh.milek7.pl
connect: Network is unreachableRe: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#39This sort of endearing Internet-scale thing reminds me of how NTT changes their reverse DNS's ( https://mailman.nanog.org/pipermail/nanog/2016-February/0841... ). There's other vanity reverse-DNS tricks that you can see in traceroutes, but this is done with a global-scale IPv4/IPv6 network that actually is carrying a lot of customer traffic. Try "traceroute ntt.net" now, you'll see hops like: 9 ae-19.sayonara-todd.r0…
What about those domains says vanity reverse DNS to you? They look like bog standard location-named routers to me.
Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface
#40Earlier quoted context omitted.
A cursory Google search would have revealed that BGP is Border Gateway Protocol.
Why did people downvote a pretty appropriate snark while not downvoting a question that took longer to ask than the google search would have taken?