Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

stat.ripe.net

Post reply on HN
Print view View original

41–50 of 114 posts

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#41

Post by garaetjjte »

jwilk wrote: post #38
garaetjjte wrote: post #25

In 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…

Doesn't work for me: # traceroute -I -q 1 trh.milek7.pl connect: Network is unreachable

Are you sure that you have IPv6?. I don't have 60k addresses to do it on IPv4 :)

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#42

Post by stestagg »

okreallywtf wrote: post #35
na85 wrote: post #4

Earlier 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?

Post gave off bad vibes. Bad vibes make people unhappy. Unhappy people make the internet have more bad vibes ..

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#43

Post by mcescalante »

job wrote: post #33
zkms wrote: post #15

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…

It might amuse you to know the same NTT people are behind the BGP Nyancat :-)

I am amazed/fascinated by this! I would love to hear more for all the non-experts here about how the BGP Nyancat came to be :)

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#44

Post by rsync »

Lanzaa wrote: post #9

That is amazing. Does anyone have similar examples of weird technological art?

I immediately thought of the test flight patterns that pilots draw across the US with their flight plans.

Here is a boeing test flight that drew out the boeing logo across the united states:

http://www.huffingtonpost.com/2012/02/13/787-dreamliner-draw...

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#45

Post by y4mi »

rcarmo wrote: post #22
fosco wrote: post #19

Earlier quoted context omitted.

thats why we use DNS more effectively. A tool is only useful is if it implemented correctly. it would be easier and faster with well thought out DNS to yell a name across the room. (would have been my response to that silly argument)

Yeah, well, DNS can't be used for core network configs - only to expose them to lesser networks :) 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.

and there are ... so many obscure and strange problems that are caused by a hiccup or simply misconfigured DNS... not saying you shouldn't use it, just ... don't claim it's the ultimate cool-aid that resolves everything.

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#46

Post by job »

zkms wrote: post #15

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…

On April 1st 2015 I tried to create new poems by remixing an existing body of work through reverse DNS: https://bandaancha.eu/foros/april-fools-ntt-1717230 - the original was better perhaps ;-)

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#48

Post by zitterbewegung »

rcarmo wrote: post #13

OMG. 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.

I guess instead of Nyan Cats on the internet we have Nyan cat as a part of it .

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#49

Post by job »

mcescalante wrote: post #43
job wrote: post #33

Earlier quoted context omitted.

It might amuse you to know the same NTT people are behind the BGP Nyancat :-)

I am amazed/fascinated by this! I would love to hear more for all the non-experts here about how the BGP Nyancat came to be :)

The starting point is a BMP file of the Nyan cat which is read into a simple two dimensional array by a small python script. The script looks at the current time and maps that to a column of pixels in the BMP. Each row of pixels in the BMP is represented by one IPv4 /24. If the pixel is "on" a BGP route announcement is generated, if the pixel is "off" the route is withdrawn. Each pixel in the BMP file represents 8 hours of announcing.

Re: After 3072 hours of manipulating BGP, a Nyancat was drawn on this RIPE interface

#50

Post by richardwhiuk »

rcarmo wrote: post #22
fosco wrote: post #19

Earlier quoted context omitted.

thats why we use DNS more effectively. A tool is only useful is if it implemented correctly. it would be easier and faster with well thought out DNS to yell a name across the room. (would have been my response to that silly argument)

Yeah, well, DNS can't be used for core network configs - only to expose them to lesser networks :) 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.

You can configure with DNS but it just needs to resolve and store the resolved address rather than storing the hostname
Post reply on HN