Sponsored Content
Top Forums Shell Programming and Scripting [ASK] How to check whether ipv4 or ipv6 and ping those IP Post 302532123 by franzramadhan on Monday 20th of June 2011 02:39:27 AM
Old 06-20-2011
I have tried your solution, but it doesnt seem to be running.But I have an idea, to get ping result from ping6 command from linux it self. The problem is, I still dont understand how to grep the ping result from this command, whether reply,request timed out, or destination unreachable? Somebody told me to use regex on perl. But I still confused, what kind of regex that I have to use..
Any solutions??

Thanks in advance,
Franz
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

convert from ipv4 to ipv6

hello i'm working on aix 5300-05-03 hacmp ver 5.4 well my issue is that when firewall (gateway to internet ) goes down my machine start to work very very slowly!!! the output of the sniffer is that on the output card , my machine try to convert ipv4 to ipv6 0.0.2.0 my machine is not configure... (1 Reply)
Discussion started by: ariec
1 Replies

2. AIX

convert ipv4 ti ipv6

hello i'm working on AIX 5300-05-03 P520 hacmp 5.4 when connection to the internet is going down , firewall down, my application work verey verey slowly!!! and on the sliffer output i'm got trys of my serevr to do convert from ipv4 ipv6 ( 0.0.2.0 and AAAAAAAA). some one have an idea why... (1 Reply)
Discussion started by: ariec
1 Replies

3. IP Networking

How to configure Samba 3 for IPv6 operation with Window XP for IPv4

Need help...! I want to configure Samba 3 for IPv6 operation with Window XP for IPv4. I appreciate any guide. Thanks HSV (0 Replies)
Discussion started by: Sovan
0 Replies

4. Solaris

(Help) IPv6 tunneling over existing IPv4 in Solaris

Hi folks, i hope you'll help me to configure my ipv6 tunnel. First, i create my tunnel in: Hurricane Electric Free IPv6 Tunnel Broker My IP is 83.228.93.34 in HE: ------------------------ Server IPv4 address: 216.66.84.46 Server IPv6 address: 2001:470:1f14:16a::1/64 Client IPv4 address: ... (2 Replies)
Discussion started by: static
2 Replies

5. Red Hat

IPv4 and IPv6 Related Question to CentOS VMs

Hello, I was wondering if it would be possible to run two VMs one with services for IPv4 and the other one with services for IPv6. The main physical system would be connected to a IPv6 switch. I think it should be fine but I would like to hear out your comments. (1 Reply)
Discussion started by: svalenciatech
1 Replies

6. Solaris

ISC DHCP ipv4 and ipv6 options

Hi I am looking to set-up ISC DHCP to support ipv6, and to migrate my existing SUN DHCP ipv4 to ISC, finding the ipv4 options for the SUN DHCP options was ok eg TFTPsrvN = tftp-server-name OptBootF = bootfile-name However if I set up a DHCPv6 does anyone know what the equivalent... (1 Reply)
Discussion started by: eeisken
1 Replies

7. AIX

IPv6/IPv4 Only in AIX

Hi all, I have setup ipv6 in AIX machine using autoconf6 command. I was successfull in doing this. after execution of the command local link address was assigned to one of the interfaces (en1).But I have to setup the following environment as well. 1) Machine with only IPv6 support(IPv4... (0 Replies)
Discussion started by: ard
0 Replies

8. Solaris

Ntp between ipv4 and ipv6

Hi, I am looking for a solution to configure ntp between ipv4 ( ntp server ) to ipv6 ( client) . I had google, but lot many sites suggest to have dual stock or tunnaling. my issue is I have client has only ipv6 address ans server has ipv4 address. is it possible to sync time,... (4 Replies)
Discussion started by: naveen.surisett
4 Replies

9. Solaris

How to assign IPv4 and IPv6 addresses with same interface?

Hello dears how to assign IPv4 and IPv6 addresses with same interface on solaris 10 (1 Reply)
Discussion started by: ttashman
1 Replies
External(3pm)						User Contributed Perl Documentation					     External(3pm)

NAME
Net::Ping::External - Cross-platform interface to ICMP "ping" utilities SYNOPSIS
In general: use Net::Ping::External qw(ping); ping(%options); Some examples: use Net::Ping::External qw(ping); # Ping a single host my $alive = ping(host => "127.0.0.1"); print "127.0.0.1 is online" if $alive; # Or a list of hosts my @hosts = qw(127.0.0.1 127.0.0.2 127.0.0.3 127.0.0.4); my $num_alive = 0; foreach (@hosts) { $alive = ping(hostname => $_, timeout => 5); print "$_ is alive! " if $alive; $num_alive++; } print "$num_alive hosts are alive. "; # Using all the fancy options: ping(hostname => "127.0.0.1", count => 5, size => 1024, timeout => 3); DESCRIPTION
Net::Ping::External is a module which interfaces with the "ping" command on many systems. It presently provides a single function, "ping()", that takes in a hostname and (optionally) a timeout and returns true if the host is alive, and false otherwise. Unless you have the ability (and willingness) to run your scripts as the superuser on your system, this module will probably provide more accurate results than Net::Ping will. Why? o ICMP ping is the most reliable way to tell whether a remote host is alive. o However, Net::Ping cannot use an ICMP ping unless you are running your script with privileged (AKA "root") access. o The system's "ping" command uses ICMP and does not usually require privileged access. o While it is relatively trivial to write a Perl script that parses the output of the "ping" command on a given system, the aim of this module is to encapsulate this functionality and provide a single interface for it that works on many systems. ping() OPTIONS This module is still "alpha"; it is expected that more options to the "ping()" function will be added soon. o "host, hostname" The hostname (or dotted-quad IP address) of the remote host you are trying to ping. You must specify either the "hostname" option or the "ip" option. "host" and "hostname" are synonymous. o "ip" A packed bit-string representing the 4-byte packed IP address (as returned by "Socket.pm"'s "inet_aton()" function) of the host that you would like to ping. o "timeout" The maximum amount of time, in seconds, that "ping()" will wait for a response. If the remote system does not respond before the timeout has elapsed, "ping()" will return false. Default value: 5. o "count" The number of ICMP ping packets to send to the remote host. Eventually, Net::Ping::External will return the number of packets that were acknowledged by the remote host; for now, however, "ping()" still returns just true or false. Default value: 1. o "size" Specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data. Default value: 56. SUPPORTED PLATFORMS Support currently exists for interfacing with the standard ping utilities on the following systems. Please note that the path to the `ping' should be somewhere in your PATH environment variable (or your system's closest equivalent thereof.) Otherwise, Net::Ping::External will be unable to locate your system's `ping' command. o Win32 Tested OK on Win98, Win XP. It should work on other Windows systems as well. o Cygwin Tested OK on Cygwin 1.5.21. Problem is that we may be running windows ping. They have different options. o Linux Tested OK on Debian 2.2 and Redhat 6.2. It appears that different versions of Linux use different versions of ping, which support different options. Not sure how I'm going to resolve this yet; for now, all the options but "count" are disabled. o BSD Tested OK on OpenBSD 2.7 and 3.0, Netbsd 1.5.3, Freebsd 4.6.2, 5.4. Needs testing for BSDi. o Solaris Tested OK on Solaris 2.6 and 2.7. o IRIX Tested OK on IRIX 6.5. o AIX, DEC OSF, UNICOSMK, NeXTStep, HP-UX, BSD/OS (BSDi), BeOS Support for these systems is integrated into this module but none have been tested yet. If you have successful or unsuccessful test results for any of these systems, please send them to me. On some of these systems, some of the arguments may not be supported. If you'd like to see better support on your system, please e-mail me. More systems will be added as soon as any users request them. If your system is not currently supported, e-mail me; adding support to your system is probably trivial. BUGS
This module should be considered beta. Bugs may exist. Although no specific bugs are known at this time, the module could use testing on a greater variety of systems. See the warning below. WARNING
This module calls whatever "ping" program it first finds in your PATH environment variable. If your PATH contains a trojan "ping" program, this module will call that program. This involves a small amount of risk, but no more than simply typing "ping" at a system prompt. Beware Greeks bearing gifts. AUTHOR
Alexandr Ciornii (alexchorny AT gmail.com), Colin McMillen (colinm AT cpan.org) This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. CREDITS
Dan Moore contributed command-line options and code for NeXT, BeOS, HP-UX, and BSD/OS. Jarkko Hietaniemi contributed a huge list of command-line options and results for the `ping' command on 9 different systems. Randy Moore contributed several patches for Win32 support. Marc-Andre Dumas contributed a patch for FreeBSD support. Jonathan Stowe fixed a bug in 0.09 that prevented the module from running on some systems. Numerous people sent in a patch to fix a bug in 0.10 that broke ping on Windows systems. Peter N. Lewis contributed a patch that works correctly on Mac OS X 10.2 (and hopefully other versions as well). SEE ALSO
Net::Ping perl v5.10.1 2008-12-18 External(3pm)
All times are GMT -4. The time now is 11:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy