Comparison is the thief of joy 🙃
Though if I push my scanner hard it could probably do 16k/sec on the single core and 1gig connection it is on. The problem is how reliably I could do 16k/sec over the network, since a good portion would be dropped even if the host’s hardware could keep up.
I’d probably need access to enterprise-level equipment that could handle the routing load if I were to do it in 5 seconds lol, it’s insane they managed to do that
about a month, since I ran it at about 6000 addresses / sec checking distinct addresses 4 times (round robin) or 1500 finished / sec. This was the fastest I went to avoid silent UDP drops and to hopefully not annoy my VPS hoster too much.
I left details out to be less verbose.
commenting because it may interest you, but have you looked at the pintos project? It is an educational OS framework with the instructions on how to implement basic things like threading, user programs, file systems
Here you go!!! Purple is reserved range. It’s a Hilbert curve as seen here https://www.caida.org/archive/id-consumption/census-map/images/20061108.png
This was a ping scan, so it wasn’t probing any TCP/UDP ports (see shodan.io). I suppose you could use ICMP control messages (Destination Unreachable) to determine if something was unused, but that assumes the other side is being friendly.