科技回声

14 条评论

elvinyung大约 7 年前

Nice! Perhaps a Gibson quote is appropriate here:> Program a map to display frequency of data exchange, every thousand megabytes a single pixel on a very large screen. Manhattan and Atlanta burn solid white. Then they start to pulse, the rate of traffic threatening to overload your simulation. Your map is about to go nova...

anigbrowl大约 7 年前

I don't think straight hilbert curves:IP ranges are the best mapping, and would prefer something built around ping times or hop check routings in 3 dimensions. Or integrate it with geolocation data. But! It's still super useful. Or integrate it with geolocation data.On top of all of this, I also did a bonus scan of a few APNIC IP blocks every 30 mins for 24 hours. The data from that allows you to see the internet “breathe” as clients come online in the morning and offline at nightReally, I'm surprised there isn't a distributed/crowdsourced system to do this all the time and allow people to study the 'weather' in the datasphere.

评论 #16893060 未加载

评论 #16892681 未加载

评论 #16893764 未加载

walrus01大约 7 年前

Also for fun, ipv6 exhaustion counter.<a href="https://samsclass.info/ipv6/exhaustion-2016.htm" rel="nofollow">https://samsclass.info/ipv6/exhaustion-2016.htm</a>

评论 #16892585 未加载

评论 #16890552 未加载

no_identd大约 7 年前

I wish this used a good color mapping, like Viridis or cubehelix, or at least used HSLuv or HPLuv to map the parameters to colors. I bet we could see a lot more patterns in this then.Edit: I made a github issue for this:<a href="https://github.com/measurement-factory/ipv4-heatmap/issues/2" rel="nofollow">https://github.com/measurement-factory/ipv4-heatmap/issues/2</a>

zokier大约 7 年前

I did something similar few years back, mapping ipv4 address space owners.<a href="http://zokier.net/stuff/map_of_the_internet.png" rel="nofollow">http://zokier.net/stuff/map_of_the_internet.png</a>

swirepe大约 7 年前

You can scan the whole internet in about an hour. I had luck using AWS and zmap.<a href="https://github.com/zmap/zmap" rel="nofollow">https://github.com/zmap/zmap</a>

评论 #16891171 未加载

评论 #16890955 未加载

xvilka大约 7 年前

According to [1] IPv6 adoption is slowed down significantly, so we stick to NAT for a decade at least I think.[1] <a href="https://www.google.com/intl/ru/ipv6/statistics.html" rel="nofollow">https://www.google.com/intl/ru/ipv6/statistics.html</a>

LeoPanthera大约 7 年前

The 9MB PNG is unoptimized. By passing it through optipng and advdef I managed to losslessly squish it down to 7MB.Also, I would be remiss if I did not point out that this:cat ping.txt | pcregrep -o1 ': (\d+\.\d+\.\d+\.\d+)'is a Useless Use Of Cat.[1]It should be rewritten:pcregrep -o1 ': (\d+\.\d+\.\d+\.\d+)' <ping.txt[1] <a href="http://porkmail.org/era/unix/award.html" rel="nofollow">http://porkmail.org/era/unix/award.html</a>

评论 #16892636 未加载

toolslive大约 7 年前

You can do the same with LBA's of a block device. It's interesting to see where different file systems place the (meta) data.

bawana大约 7 年前

How do the number of internet connections relate to the number of nodes? Building fat pipes is not the answer just as more highways is not the answer to more destinations. The increase in traffic will consume more resources exponentially (factorially?)faster than the increase of address space

iod大约 7 年前

IPv6 Active Webhosts Hilbert also exist based on Akamai data as I found this d3 block by Vasco Asturiano:<a href="https://bl.ocks.org/vasturiano/0c0f60cf193fa3a04b5d414aed6f5834" rel="nofollow">https://bl.ocks.org/vasturiano/0c0f60cf193fa3a04b5d414aed6f5...</a>The author also has some other cool d3 visualizations of IPv6 Routes, AS, as well as IPv4 allocations.

infinity0大约 7 年前

Surprised that he missed out 192.168.0.0/16

评论 #16893669 未加载

评论 #16890919 未加载

inetknght大约 7 年前

It strikes me that we've "run out" of IPv4 address space but there's entire large blocks of space allocated to entities that don't appear to be using them.

eps大约 7 年前

Aye :)<a href="https://xkcd.com/195/" rel="nofollow">https://xkcd.com/195/</a>

14 条评论

elvinyung大约 7 年前

anigbrowl大约 7 年前

评论 #16893060 未加载

评论 #16892681 未加载

评论 #16893764 未加载

walrus01大约 7 年前

Also for fun, ipv6 exhaustion counter.<a href="https://samsclass.info/ipv6/exhaustion-2016.htm" rel="nofollow">https://samsclass.info/ipv6/exhaustion-2016.htm</a>

评论 #16892585 未加载

评论 #16890552 未加载

no_identd大约 7 年前

zokier大约 7 年前

swirepe大约 7 年前

You can scan the whole internet in about an hour. I had luck using AWS and zmap.<a href="https://github.com/zmap/zmap" rel="nofollow">https://github.com/zmap/zmap</a>

评论 #16891171 未加载

评论 #16890955 未加载

xvilka大约 7 年前

LeoPanthera大约 7 年前

评论 #16892636 未加载

toolslive大约 7 年前

You can do the same with LBA's of a block device. It's interesting to see where different file systems place the (meta) data.

bawana大约 7 年前

iod大约 7 年前

infinity0大约 7 年前

Surprised that he missed out 192.168.0.0/16

评论 #16893669 未加载

评论 #16890919 未加载

inetknght大约 7 年前

It strikes me that we've "run out" of IPv4 address space but there's entire large blocks of space allocated to entities that don't appear to be using them.

eps大约 7 年前

Aye :)<a href="https://xkcd.com/195/" rel="nofollow">https://xkcd.com/195/</a>

Mapping the internet with Hilbert curves

14 条评论

Mapping the internet with Hilbert curves

14 条评论