This idea has been around for a long time; see e.g. Zalewski's paper from 2003: http://lcamtuf.coredump.cx/juggling_with_packets.txt
Cool to see an implementation though!
PingFS
11–17 of 17 posts
Re: PingFS
#12By the way, the linked slideshow is hilarious, never seen it before:
http://www.slideshare.net/tenderlove/worst-ideas-ever
Re: PingFS
#13How much data could you store if you pinged the voyager 2 probe?
When Voyager was at Jupiter, communications allowed for a bitrate of roughly 115kbit/s. The distance from Earth to Jupiter is about 5AU. The current distance to Voyager is 100AU, so let's say we still have a bitrate of 1kbit/s. According to WolframAlpha, Voyager 2 is about 50000 light seconds away from us. Now you can do the math.
Re: PingFS
#14By the way, the linked slideshow is hilarious, never seen it before: http://www.slideshare.net/tenderlove/worst-ideas-ever
A video of the talk is here: http://www.confreaks.com/videos/198-rubyconf2009-worst-ideas...
Re: PingFS
#15What exactly does this do?
seems like it essentially keeps data stored by catching data from ICMP (ping) packets, rewrapping them in another ping packet and shoving them back on the network. Think of it kind of like network RAM, the data isn't stored anywhere persay and if either host fails to bounce back the payload the data is lost since it wasn't stored on any single machine and only kept alive in limbo.
The data is stored somewhere. It's stored in the cache memory of all the routers in between.
Re: PingFS
#16Link to Google Cache because the server seems to be overloaded:
http://webcache.googleusercontent.com/search?q=cache:786NsZY...
Re: PingFS
#17> PingFS is a set of python scripts ...
> Each file ... sent over the wire in an ICMP echo request, and promptly erased from memory.
can you actually reliably erase anything from memory in python?