Skip to main content

Ping to many host/node in one command

We can use "for loop" in interactive command, here is the example:
we want to ping host/node from 10.100.11.1 until 10.100.11.10:

We use "i" as a variable, values of "i" are 1 until 10. In the ping option, we use "-c 1" this means that we send ping packet only one (default in linux is continues until stopped).

here is the result:
[syam@borneo03 ~]$ for i in {1..10}; do ping 10.100.11.$i -c 1; done
PING 10.100.11.1 (10.100.11.1) 56(84) bytes of data.
64 bytes from 10.100.11.1: icmp_seq=1 ttl=64 time=1.58 ms

 --- 10.100.11.1 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.587/1.587/1.587/0.000 ms
PING 10.100.11.2 (10.100.11.2) 56(84) bytes of data.
64 bytes from 10.100.11.2: icmp_seq=1 ttl=64 time=1.09 ms

 --- 10.100.11.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.093/1.093/1.093/0.000 ms
PING 10.100.11.3 (10.100.11.3) 56(84) bytes of data.
64 bytes from 10.100.11.3: icmp_seq=1 ttl=64 time=1.69 ms

 --- 10.100.11.3 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.696/1.696/1.696/0.000 ms
PING 10.100.11.4 (10.100.11.4) 56(84) bytes of data.
64 bytes from 10.100.11.4: icmp_seq=1 ttl=64 time=1.70 ms

 --- 10.100.11.4 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.700/1.700/1.700/0.000 ms
PING 10.100.11.5 (10.100.11.5) 56(84) bytes of data.
64 bytes from 10.100.11.5: icmp_seq=1 ttl=64 time=1.68 ms

 --- 10.100.11.5 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.686/1.686/1.686/0.000 ms
PING 10.100.11.6 (10.100.11.6) 56(84) bytes of data.
64 bytes from 10.100.11.6: icmp_seq=1 ttl=64 time=1.70 ms

 --- 10.100.11.6 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.703/1.703/1.703/0.000 ms
PING 10.100.11.7 (10.100.11.7) 56(84) bytes of data.
64 bytes from 10.100.11.7: icmp_seq=1 ttl=64 time=1.70 ms

 --- 10.100.11.7 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.702/1.702/1.702/0.000 ms
PING 10.100.11.8 (10.100.11.8) 56(84) bytes of data.
64 bytes from 10.100.11.8: icmp_seq=1 ttl=64 time=0.721 ms

 --- 10.100.11.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.721/0.721/0.721/0.000 ms
PING 10.100.11.9 (10.100.11.9) 56(84) bytes of data.
64 bytes from 10.100.11.9: icmp_seq=1 ttl=64 time=1.67 ms

 --- 10.100.11.9 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.671/1.671/1.671/0.000 ms
PING 10.100.11.10 (10.100.11.10) 56(84) bytes of data.
64 bytes from 10.100.11.10: icmp_seq=1 ttl=64 time=1.68 ms

 --- 10.100.11.10 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 1ms
rtt min/avg/max/mdev = 1.683/1.683/1.683/0.000 ms
[syam@borneo03 ~]$
we can combine with grep to filter the result, for example we "grep" the ping:
for i in {1..10}; do ping 10.100.11.$i -c1 | grep 64; done
 Just guess the result ;-)
Labels:

Comments

Post a Comment

Popular posts from this blog

Shrink LVM without data loss

assume we have 3 logical volume: lv1 40GB, lv2 8GB, lv3 200GB in volume group called data . we want to resize lv3 become 180GB. here is the steps: booting to single mode enter init 1 (type: init 1) umount logical volume that you want to resize, e.g. umount /dev/data/lv3 check the filesystem: e2fsck -f /dev/data/lv3 resize the filesystem: resize2fs -p /dev/data/lv3 180G lvreduce -L -20G /dev/data/lv3 Ref: askubuntu.com
Post a Comment
Read more

Mikrotik Bruteforce Login Prevention

Reference: WIKI FTP Bruteforce prevention This configuration allows only 10 FTP login incorrect answer per minutes add chain=input protocol=tcp dst-port=21 src-address-list=ftp_blacklist action=drop comment="drop ftp brute forcers" add chain=output action=accept protocol=tcp content="530 Login incorrect" dst-limit=1/1m,9,dst-address/1m add chain=output action=add-dst-to-address-list protocol=tcp content="530 Login incorrect" address-list=ftp_blacklist address-list-timeout=3h SSH Bruteforce prevention This will prevent SSH bruteforcer to be banned for 10 days after repetitive attemps add chain=input protocol=tcp dst-port=22 src-address-list=ssh_blacklist action=drop comment="drop ssh brute forcers" disabled=no add chain=input protocol=tcp dst-port=22 connection-state=new src-address-list=ssh_stage3 action=add-src-to-address-list address-list=ssh_blacklist address-list-timeout=10d comment="" disabled=no add chain=input...
Post a Comment
Read more