10-18-2007
By default (when packet-size is not specified), the size of transmitted packets is 64 bytes. The minimum value allowed for packet-size is 8 bytes, and the maximum value is 4095 bytes, on some systems is even 65000. If packet-size is smaller than 16 bytes, there is not enough room for timing information. In that case, the round-trip times are not displayed. In your case, the -n flag probably means something else, not the count number.]
The error number looks like AIX, I just tested AIX, and I seem to be right : -n flag means "packet-size", as well as "-s" whereas the count is "-c" flag.
9 More Discussions You Might Find Interesting
1. HP-UX
how to get network packet size
I would like get network output rate(kb/sec)
I type command "netstat -i"
Ipkts Ierrs Opkts Oerrs 653387 0 678202 0
but i didn't know what is it packet size ,
how could i get it? (1 Reply)
Discussion started by: alert0919
1 Replies
2. UNIX for Advanced & Expert Users
We're running Solaris 7 on FDDI n/w on an E6500 host and wish to use MTU (packet size) > 1500, more like 3072 bytes to begin with and possibly up to 4096 bytes.
Linux has /etc/network/interfaces. Does ANYONE remember the equivalent in Unix? When I do ifconfig eth0 mtu 4000, I get the error... (0 Replies)
Discussion started by: sharique
0 Replies
3. Solaris
Greetings, I'm stuck in a time warp using ancient machines from the prehistoric era that should be rightfully displayed in the Smithsonian.
We're running Solaris 7 on FDDI n/w on an E6500 host and wish to use MTU (packet size) > 1500, more like 3072 bytes to begin with and possibly up to 4096... (9 Replies)
Discussion started by: sharique
9 Replies
4. IP Networking
Hi!
I'm writing an application (using BSD sockets on a Linux host) which communicates over TCP/IP with an embedded device. This embedded device has an old and real slow integrated circuit (Epson S1S6000) which handles all of the TCP/IP communication for it.
Problem is, this circuit (S1S6000)... (7 Replies)
Discussion started by: olle
7 Replies
5. Shell Programming and Scripting
Hi,
I develop simple animation ping script on Solaris Platform. It is like Cisco ping.
Examples and source code are below.
bash-3.00$ gokcell 152.155.180.8 30
Sending 30 Ping Packets to 152.155.180.8
!!!!!!!!!!!!!.!!!!!!!!!!!!!!!.
% 93.33 success... % 6.66 packet loss...... (1 Reply)
Discussion started by: gokcell
1 Replies
6. Shell Programming and Scripting
Hi
I am using perl to ping a list of nodes - with script below :
$p = Net::Ping->new("icmp");
if ($p->ping($host,1)){
print "$host is alive.\n";
}
else {
print "$host is unreacheable.\n";
}
$p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies
7. AIX
(5 Replies)
Discussion started by: Vishal_dba
5 Replies
8. Shell Programming and Scripting
Hello,
on Solaris ping command does not report failed packet as in i.e. Windows (Connection timeout)
Instead it reports the sequence of the sent packet:
64 bytes from 10.80.4.120: icmp_seq=11. time=36.0 ms
64 bytes from 10.80.4.120: icmp_seq=12. time=35.9 ms
64 bytes from 10.80.4.120:... (6 Replies)
Discussion started by: drbiloukos
6 Replies
9. Programming
help with bash script!
im am working on this script to make sure my server will stay online, so i made this script..
HOSTS="192.168.138.155"
COUNT=4
pingtest(){
for myhost in "$@"
do
ping -c "$COUNT" "$myhost" &&return 1
done
return 0
}
if pingtest $HOSTS
#100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies
PK(4) Kernel Interfaces Manual PK(4)
NAME
pk - packet driver
DESCRIPTION
The packet driver implements a full-duplex end-to-end flow control strategy for machine-to-machine communication. Packet driver protocol
is established by calling pkon(2) with a character device file descriptor and a desired packet size in bytes. The packet size must be a
power of 2, 32<=size<=4096. The file descriptor must represent an 8-bit data path. This is normally obtained by setting the device in
raw mode (see ioctl(2)).
The actual packet size, which may be smaller than the desired packet size, is arrived at by negotiation with the packet driver at the
remote end of the data link.
The packet driver maintains two data areas for incoming and outgoing packets. The output area is needed to implement retransmission on
errors, and arriving packets are queued in the input area. Data arriving for a file not open for reading is discarded. Initially the size
of both areas is set to two packets.
It is not necessary that reads and writes be multiples of the packet size although there is less system overhead if they are. Read opera-
tions return the maximum amount of data available from the input area up to the number of bytes specified in the system call. The buffer
sizes in write operations are not normally transmitted across the link. However, writes of zero length are treated specially and are
reflected at the remote end as a zero-length read. This facilitates marking the serial byte stream, usually for delimiting files.
When one side of a packet driver link is shut down by close(2)or pkoff (see pkon(2)), read(2) on the other side will return 0, and write on
the other side will raise a SIGPIPE signal.
SEE ALSO
pkon(2), pkopen(3)
local PK(4)