debian tunnel problem
Carmen Sandiego on Friday, 16 January 2004 17:51:05
i have configured my ipv6 tunnel and when i will ping any ipv6 ip it returns the following error "ping: bind icmp socket: Invalid argument"
anyone now what that means? i also can't traceroute an ipv6 ip it returns
"traceroute: bind sending socket: Invalid argument" ;(
debian tunnel problem
Shadow Hawkins on Monday, 19 January 2004 07:55:17
Are you sure you have ipv6 support on the machine? Either compyled in the kernel, or as a module?
And is the module loaded?
debian tunnel problem
Carmen Sandiego on Monday, 19 January 2004 10:14:06
Did you try ping6 instead of ping?
debian tunnel problem
Shadow Hawkins on Monday, 19 January 2004 13:21:10
Which kernel version are you using? If you are running an older kernel, try upgrading to the latest one - 2.4.24 from www.kernel.org.
debian tunnel problem
Carmen Sandiego on Monday, 19 January 2004 16:29:16
yes i have ipv6 support on my machine and i also used ping6 and not ping
i can ping6 the endpoint of my tunnel but no other adresses out there
i use kernel 2.4.20
debian tunnel problem
Jeroen Massar on Monday, 19 January 2004 16:49:12
You might want to show actual output and not "it doesn't work" without any output or what you are trying to do.
debian tunnel problem
Carmen Sandiego on Monday, 19 January 2004 19:52:45
okay sorry
if i try to ping an ipv6 adress i get the following output:
6bone.net > 3ffe:b00:c18:1::10
www.ipv6-net.org > 2001:618:1401::4
if i try to ping 6bone:
taf-clan:~# ping6 -c3 3ffe:b00:c18:1::10
ping: bind icmp socket: Invalid argument
and ipv6-net.org
taf-clan:~# ping6 -c3 2001:618:1401::4
ping: bind icmp socket: Invalid argument
but if i ping my ipv6 endpoint at xx i geht the normal ping output:
taf-clan:~# ping6 -c3 2001:6f8:900:fc::1
PING 2001:6f8:900:fc::1(2001:6f8:900:fc::1) from 2001:6f8:900:fc::2 : 56 data bytes
64 bytes from 2001:6f8:900:fc::1: icmp_seq=1 ttl=64 time=8.72 ms
64 bytes from 2001:6f8:900:fc::1: icmp_seq=2 ttl=64 time=8.50 ms
64 bytes from 2001:6f8:900:fc::1: icmp_seq=3 ttl=64 time=8.66 ms
--- 2001:6f8:900:fc::1 ping statistics ---
3 packets transmitted, 3 received, 0% loss, time 2023ms
rtt min/avg/max/mdev = 8.500/8.630/8.727/0.122 ms
so i can only reach my tunnel endpoint nothing else out there my sixx interfaces looks:
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:6f8:900:fc::2/64 Scope:Global
inet6 addr: fe80::d9a0:ab70/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:629 errors:0 dropped:0 overruns:0 frame:0
TX packets:624 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:61056 (59.6 KiB) TX bytes:73888 (72.1 KiB)
if anyone knows how to get this tunnel work right please help me thanks
debian tunnel problem
Jeroen Massar on Monday, 19 January 2004 20:31:29
And how does your full routing table look like? What kernel? What ... What ... ? Aka be more specific. You could for instance do a 'strace ping6 ...' for checking what exactly is going wrong and another point would be to check your firewall rules etc.
debian tunnel problem
Carmen Sandiego on Monday, 19 January 2004 20:43:58
ok..
the firewall is disabled at the moment so that shoud be no problem
the kernel on the machine is 2.4.21-2-686
my routing table:
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 23 36 lo
::/3 2001:6f8:900:fc::1 UG 1024 0 0 sixxs
2001:6f8:900:fc::2/128 :: U 0 749 21 lo
2001:6f8:900:fc::/64 :: UA 256 613 1173 sixxs
fe80::d9a0:ab70/128 :: U 0 0 0 lo
fe80::240:63ff:fec2:dd5e/128 :: U 0 224 224 lo
fe80::/64 :: UA 256 0 0 eth0
fe80::/64 :: UA 256 0 0 sixxs
ff00::/8 :: UA 256 0 0 eth0
ff00::/8 :: UA 256 0 0 sixxs
::/0 :: UDA 256 0 0 eth0
i tried this 'strace ping6' it returns:
taf-clan:~# strace ping6 3ffe:b00:c18:1::10
execve("/bin/ping6", ["ping6", "3ffe:b00:c18:1::10"], [/* 15 vars */]) = 0
uname({sys="Linux", node="taf-clan.org", ...}) = 0
brk(0) = 0x807087c
open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=11791, ...}) = 0
old_mmap(NULL, 11791, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40012000
close(3) = 0
open("/lib/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((\0\000"..., 1024) = 1024
fstat64(3, {st_mode=S_IFREG|0644, st_size=56652, ...}) = 0
old_mmap(NULL, 65412, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40015000
mprotect(0x40022000, 12164, PROT_NONE) = 0
old_mmap(0x40022000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xd000) = 0x40022000
old_mmap(0x40023000, 8068, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40023000
close(3) = 0
open("/lib/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\0\275Z\1"..., 1024) = 1024
fstat64(3, {st_mode=S_IFREG|0755, st_size=1103880, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40025000
old_mmap(NULL, 1113636, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40026000
mprotect(0x4012e000, 32292, PROT_NONE) = 0
old_mmap(0x4012e000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x107000) = 0x4012e000
old_mmap(0x40134000, 7716, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40134000
close(3) = 0
munmap(0x40012000, 11791) = 0
socket(PF_INET6, SOCK_RAW, 58) = 3
getuid32() = 0
setuid32(0) = 0
socket(PF_INET6, SOCK_DGRAM, 0) = 4
connect(4, {sin_family=AF_INET6, sin6_port=htons(1025), inet_pton(AF_INET6, "3ffe:b00:c18:1::10", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
getsockname(4, {sin_family=AF_INET6, sin6_port=htons(32791), inet_pton(AF_INET6, "fe80::240:63ff:fec2:dd5e", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
close(4) = 0
bind(3, {sin_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "fe80::240:63ff:fec2:dd5e", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINVAL (Invalid argument)
dup(2) = 4
fcntl64(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
brk(0) = 0x807087c
brk(0x807187c) = 0x807187c
brk(0) = 0x807187c
brk(0x8072000) = 0x8072000
fstat64(4, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 12), ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40012000
_llseek(4, 0, 0xbffff890, SEEK_CUR) = -1 ESPIPE (Illegal seek)
write(4, "ping: bind icmp socket: Invalid "..., 41ping: bind icmp socket: Invalid argument
) = 41
close(4) = 0
munmap(0x40012000, 4096) = 0
semget(2, 1075001216, 0) = -1 ENOSYS (Function not implemented)
_exit(2) = ?
but i don't now where the error is in this output to many data for me
debian tunnel problem
Jeroen Massar on Monday, 19 January 2004 20:52:20 the kernel on the machine is 2.4.21-2-686
2.4.24 has very nice new IPv6 features and a lot of bug fixes including kernel sploit fixes ;)
my routing table: Kernel IPv6 routing table Destination Next Hop Flags Metric Ref Use Iface ::1/128 :: U 0 23 36 lo ::/3 2001:6f8:900:fc::1 UG 1024 0 0 sixxs
::/3 ??? a semi-default-route that matches when the first three bits are 0... hmmm let me see, that would currently match nothing that is allocated ? :)
<SNIP>
::/0 :: UDA 256 0 0 eth0
And a default route over eth0, there is where your packets are trying to travel.
Remove it and the odd ::/3 and put the default over the tunnel.
<SNIP>
bind(3, {sin_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6, "fe80::240:63ff:fec2:dd5e", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINVAL (Invalid argument)
This simply means that it was trying to use eth0, but failed because it can't bind a linklocal address because then one would need to supply a linkspec.
semget(2, 1075001216, 0) = -1 ENOSYS (Function not implemented)
Upgrade your kernel and especially userland to relieve yourself from this one.
debian tunnel problem
Carmen Sandiego on Tuesday, 20 January 2004 13:49:11
ah nice
i removed that ::/0 route through eth0 and added a new one via the sixxs interface now it works fine
thanks a lot
Posting is only allowed when you are logged in. |