Ping Sweep With Bash
Monday, December 8, 2008
I'm adding this entry for the following reasons:
- Bash scripting is fun!
- I like minimalistic ways of doing things
- It makes me laugh
Why
I know this doesn't matter but adds to why I'm doing this. I'm trapped in a far off land for three months and even though I've setup my servers in a remote location, I failed to realized how little a VMWare ESX server has from command line. I discovered this when I had forgotten all of the IP's for the other servers on my network. I know someone is going to say why didn't you just create a tunnel with ssh and blah blah blah but yes, ESX has limited configuration settings for that as well.
So here is what no one is waiting for: the extremely slow way of performing a ping sweep on your network from bash. If nothing else, it's given me an even better appreciation for nmap and other network scanning tools.
UPDATE: 3/4/2009 Just look at this and realized a for loop would be better.
Obviously change 10.0.0. to whatever your subnet is.
I'm adding this entry for the following reasons:
- Bash scripting is fun!
- I like minimalistic ways of doing things
- It makes me laugh
Why
I know this doesn't matter but adds to why I'm doing this. I'm trapped in a far off land for three months and even though I've setup my servers in a remote location, I failed to realized how little a VMWare ESX server has from command line. I discovered this when I had forgotten all of the IP's for the other servers on my network. I know someone is going to say why didn't you just create a tunnel with ssh and blah blah blah but yes, ESX has limited configuration settings for that as well.
So here is what no one is waiting for: the extremely slow way of performing a ping sweep on your network from bash. If nothing else, it's given me an even better appreciation for nmap and other network scanning tools.
UPDATE: 3/4/2009 Just look at this and realized a for loop would be better.
Obviously change 10.0.0. to whatever your subnet is.
<< Home