Bash script for ping in your own subnet

10 More Discussions You Might Find Interesting

1. IP Networking

Loop in /24 Subnet, No ping beyond .1 and .2

Running 3650 switch. I have this odd issue where I cannot get 4 new Centos 7 boxes pinging out on public IPs (nor pinging in), only gateway .1 and first public IP .2 This is what I see, which doesn't look normal. How do I fix this? The server itself is configured fine (Centos 7) # cat...

2. Shell Programming and Scripting

How to write bash script to subdivide a given subnet into a pre-defined number of smaller subnets?

Bash script to subdivide a given subnet into a pre-defined number of smaller subnets. Show network/broadcast address, number of hosts and assign gateway. For example: Input: ./subnetter.sh 192.168.0.0/24 3 Output: 192.168.0.0/128 subnet 192.168.0.0 broadcast 192.168.0.127 gateway...

3. Shell Programming and Scripting

How to write bash script to subdivide a given subnet into a pre-defined number of smaller subnets?

4. Solaris

Guest LDOMS on same subnet cant ping eachother

Hi all, New to this forum. I have just been reading through a historical thread about some issues with IPMP. Some tips from "Peasant" where very useful. Please see below "Just couple of more hints regarding VM. For VDS, use one VDS - one guest LDOM, don't put everything in primary-vds....

5. Shell Programming and Scripting

Need bash script to ping the servers and rename the output file each time the script is ran

HI, I have a file serverlist in that all host names are placed. i have written a small script #./testping #! /bin/bash for i in `cat serverlist` do ping $i >> output.txt done so now it creates a file output.txt till here fine.. now each time i run this script the output file...

6. Linux

Ping check failed from Nagios master server on windows hosts in the same subnet

Hello All, We have added a windows host and its config files to Nagios master server and wanted to do a ping check alone at the moment however, the nagios master server identifies the host in its GUI and immediately disappears can anyone let me know the right approach to this one, We want to...

7. UNIX for Dummies Questions & Answers

Ping bash script to file

Hello: I have this script: #!/bin/bash #for loop for ip in `cat ips` do ping $ip | grep "is alive">>pingtestlog done And its working properly with this input: ericadm@amxcruas1> cat ips 10.196.60.4 10.196.61.210 10.196.62.73 10.196.61.152

8. IP Networking

Migrating existing Subnet to a new subnet and changing ip addresses in UNIX

Hi, My project needs to migrate the existing Subnet (255.255.255.0) to a new subnet and change the ipaddresses (currently C class). How can I do that. I need some information. John

9. UNIX for Dummies Questions & Answers

Unix TCP/IP ping to other subnet

I have Digital UNIX V4.0B (Rev. 564) on alpha machine. I'm trying to acces network in subnet (192.168.1.x). Ip on Alpha comp. is from 192.168.3.X subnet. My default gateway on this network is 192.168.3.1 and it working OK from other machines. This machine is visible from same subnet...

10. Shell Programming and Scripting

Ping script using Redhat and BAsh

Alright, I have being checking out various posting here trying to hack together something for a friend Needed: A script that can run in cron doing: ping of several hosts and notifying via email when they are unavailable. I am not going to post my non working messes (I am a basic...

LEARN ABOUT FREEBSD

nos-tun

NOS-TUN(8)						    BSD System Manager's Manual 						NOS-TUN(8)

NAME

     nos-tun -- implement ``nos'' or ``ka9q'' style IP over IP tunnel

SYNOPSIS

     nos-tun -t tunnel -s source -d destination -p protocol_number [source] target

DESCRIPTION

     The nos-tun utility is used to establish an nos style tunnel, (also known as ka9q or IP-IP tunnel) using a tun(4) kernel interface.

     Tunnel is the name of the tunnel device /dev/tun0 for example.

     Source and destination are the addresses used on the tunnel device.  If you configure the tunnel against a cisco router, use a netmask of
     ``255.255.255.252'' on the cisco.	This is because the tunnel is a point-to-point interface in the FreeBSD end, a concept cisco does not
     really implement.

     Protocol number sets tunnel mode.	Original KA9Q NOS uses 94 but many people use 4 on the worldwide backbone of ampr.org.

     Target is the address of the remote tunnel device, this must match the source address set on the remote end.

EXAMPLES

     This end, a FreeBSD box on address 192.168.59.34:

	   nos-tun -t /dev/tun0 -s 192.168.61.1 -d 192.168.61.2 192.168.56.45

     Remote cisco on address 192.168.56.45:

	   interface tunnel 0
	   ip address 192.168.61.2 255.255.255.252
	   tunnel mode nos
	   tunnel destination 192.168.59.34
	   tunnel source 192.168.56.45

AUTHORS

     Nickolay N. Dudorov <nnd@itfs.nsk.su> wrote the program, Poul-Henning Kamp <phk@FreeBSD.org> wrote the man-page.  Isao SEKI
     <iseki@gongon.com> added a new flag, IP protocol number.

BUGS

     We do not allow for setting our source address for multihomed machines.

BSD
								  April 11, 1998							       BSD

Shell Programming and Scripting