Bug 10089

Summary: ping6: socket: Invalid argument
Product: [Retired] Red Hat Linux Reporter: Brock Organ <borgan>
Component: iputilsAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: dr, jboynton
Target Milestone: ---   
Target Release: ---   
Hardware: sparc   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-07-12 15:47:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Brock Organ 2000-03-09 15:07:26 UTC
the ping6 command returns an error for valid command lines:


[root@ultra1 iputils-20000121]# ping6 -I eth0 hank
ping6: socket: Invalid argument
[root@ultra1 iputils-20000121]# ping6 -I eth0
ping6: socket: Invalid argument
[root@ultra1 iputils-20000121]#

from /usr/doc/iputils-20000121/README:
* ping/ping6

Usage: ping [ as usually ]

	Changed options: -I <device name> may be used to set output interface.

	New options:
	-T [ping only]:  send timestamp IP option.
		-T tsonly	--- only timesamps
	        -T tsandaddr	--- timestamps & addresses
		-T tsprespec host1 [host2 [host3 [host 4]]]
				--- timestamp prespecified hops

	-P <traffic class> [ping6 only] sets traffic class bits.
	-F <flow label> [ping6 only] sets flow label. -F 0 generates
	    random label.
	-w TIMEOUT  exit after this time. If no replies received, exit
	            with error code.

	- it understands icmp error messages and reacts to them correctly.
	- it checks icmp checksum and reacts to corrupted packets correctly.
	- it correctly pings linux loopback.

Comment 1 Anonymous 2000-04-14 18:04:59 UTC
This also happens with ipx_configure and ipx_interface directly
after an upgrade from 6.1 to 6.2


Comment 2 Pekka Savola 2000-07-12 15:47:49 UTC
Issue with ping6 and both ipx issues (->ipxutils, really) have been
fixed in the latest rawhide.