testing ipv6 tools
Maybe I'm missing some important pieces, but is there someone who can
get this to work ?
[EMAIL PROTECTED]:/home/ik5pvx # ping6 fe80::250:4ff:fe38:a630
connect: Invalid argument
the address is the site-wide one automatically assigned to the eth0 of
another computer on the lan.
here's a strace of the command above:
[EMAIL PROTECTED]:/home/ik5pvx # strace ping6 fe80::250:4ff:fe38:a630
execve("/bin/ping6", ["ping6", "fe80::250:4ff:fe38:a630"], [/* 39 vars */]) = 0
uname({sys="Linux", node="penny", ...}) = 0
brk(0) = 0x806da98
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x40017000
open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(0x3, 0xbfffebfc)= 0
old_mmap(NULL, 57790, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40018000
close(3)= 0
open("/lib/i686/libresolv.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340(\0"..., 1024) =
1024
fstat64(0x3, 0xbfffec44)= 0
old_mmap(NULL, 70628, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40027000
mprotect(0x40035000, 13284, PROT_NONE) = 0
old_mmap(0x40035000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0xd000) = 0x40035000
old_mmap(0x40036000, 9188, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40036000
close(3)= 0
open("/lib/i686/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0l\313\1"..., 1024) =
1024
fstat64(0x3, 0xbfffec34)= 0
old_mmap(NULL, 1179140, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40039000
mprotect(0x4014e000, 44548, PROT_NONE) = 0
old_mmap(0x4014e000, 28672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x114000) = 0x4014e000
old_mmap(0x40155000, 15876, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40155000
close(3)= 0
open("/lib/i686/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0l\313\1"..., 1024) =
1024
fstat64(0x3, 0xbfffebc4)= 0
close(3)= 0
munmap(0x40018000, 57790) = 0
getpid()= 10950
socket(PF_INET6, SOCK_RAW, 58) = 3
SYS_199(0x401542c4, 0, 0x40154f20, 0x40151630, 0x2) = 0
msgget(IPC_PRIVATE, 0) = 0
socket(PF_INET6, SOCK_DGRAM, 0) = 4
connect(4, {sin_family=AF_INET6, sin6_port=htons(1025), inet_pton(AF_INET6,
"fe80::250:4ff:fe38:a630", &sin6_addr), sin6_flowinfo=htonl(0)}}, 24) = -1
EINVAL (Invalid argument)
write(2, "connect: Invalid argument\n", 26connect: Invalid argument
) = 26
_exit(2) = ?
[EMAIL PROTECTED]:/home/ik5pvx #
--
---
Pierfrancesco Caci | ik5pvx | mailto:[EMAIL PROTECTED] -
http://gusp.dyndns.org
Firenze - Italia | Office for the Complication of Otherwise Simple Affairs
Linux penny 2.4.0 #1 Sat Jan 6 14:27:38 CET 2001 i686 unknown
Re: An alarming trend (no it's not flaimbait.)
:-> "ahzz-debate" == ahzz-debate <[EMAIL PROTECTED]> writes: [...] > I see an increasing trend of two critical problems in the way > debian operates. #1 package age. Let me talk about this one > first. There has been a relatively (year or two) explosion in > the package count. As this package count has gone up, packages > that I have used for years and that used to work well have > falen into a sad state or disrepair. I'll use CDRToaster as an > example here. [...] > However, that leaves a problem. I've been told by several > developers that "it's an upstream problem. send them a patch > and when they include it we will update". Wel, that argument > doesn't work in increasingly common cases like this. At this > point, it is now (IMHO) the debian packagers problem. If they > are unwilling or unable to fix it, then the package should be > marked as "BAD" or "dead-upstream" as a warning to the user > that they should pick a different utility like this one to > use. [...] > It is my opinion that if you are putting your name to > somethign that you are providing for download, you are > implying that you have accepted responsibility for the quality > of the software. > If this is not the case, then debian needs to stop labeling > itself as a "distro" in the users eyes, and clearly label > itself as a system of packaging volunteers that have NO > responsibility for software bugs at all, and ONLY responsible > and track bugs that come from being packaged. [...] > Ok, enough of this for tonight. I will now let you all discuss > this amongst yourselves since I am not a developer. Should the > situation arise that a: I have more free time, and b: that > debian either accepts responsibility for packages, or > alternativly modifies it's public image to one of being a > packager only and keeps up with upstream stuff, then at that > point i'd be interested in joining the team to make debian > better. [...] > I would appreciate a CC: to [EMAIL PROTECTED] for > any emails sent back tot he list directly. For I am not on the > debian-devel mailing list.:) [...] Nice bait I'll bite, but if you want to read it you'll have to subscribe... It's not fair to throw the rock and hide the hand 1) learn how to properly format a mail message (i.e. fold at 75th column) 2) learn how to package a deb and adopt whichever package you think you're better at maintaining than the original maintainer 3) if the package is dead upstream, fork it and maintain it yourself. Most free software licences allow it. Have a nice (redhat|mandrake|windowsXP) day Pf -- --- Pierfrancesco Caci | ik5pvx | mailto:[EMAIL PROTECTED] - http://gusp.dyndns.org Firenze - Italia | Office for the Complication of Otherwise Simple Affairs Linux penny 2.4.16 #1 Fri Nov 30 22:12:51 CET 2001 i686 unknown
