|
config aiccu to use IPv4 Endpoint eth0:1 virtual interface?
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Thursday, 21 October 2010 10:23:45
Can aiccu use eth0:1? If yes, do I have to edit aiccu.conf to reflect this?
I think that I've set up my tunnel but I can't ping6 the remote. I think the problem is that my IPv4 Endpoint is on a virtual interface eth0:1
alexx
p.s. some of my information
(I'm on CentOS 5.5; ip6tables -F while testing; no NAT; eth1 is part of a Link Local IPv6 connection used for syncing with a sister machine, (direct cable connection - that works fine) but eth1 should be separate from eth0 in this case)
/etc/init.d/aiccu start
Tunnel Information for T43649:
POP Id : frmrs01
IPv6 Local : 2a01:240:fe00:123::2/64
IPv6 Remote : 2a01:240:fe00:123::1/64
Tunnel Type : 6in4-static
Adminstate : enabled
Userstate : enabled
[ OK ]
[root@ns0 log]# ping6 -I sixxs 2a01:240:fe00:123::2
PING 2a01:240:fe00:123::2(2a01:240:fe00:123::2) 56 data bytes
64 bytes from 2a01:240:fe00:123::2: icmp_seq=0 ttl=64 time=0.051 ms
64 bytes from 2a01:240:fe00:123::2: icmp_seq=1 ttl=64 time=0.045 ms
--- 2a01:240:fe00:123::2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.045/0.048/0.051/0.003 ms, pipe 2
[root@ns0 log]# ping6 -I sixxs 2a01:240:fe00:123::1
PING 2a01:240:fe00:123::1(2a01:240:fe00:123::1) 56 data bytes
--- 2a01:240:fe00:123::1 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 4999ms
config aiccu to use IPv4 Endpoint eth0:1 virtual interface?
Shadow Hawkins on Thursday, 21 October 2010 11:13:35
Looks like aiccu isn't the problem.
screen 1
[root@ns0 log]# ping6 2a01:240:fe00:123::1
--- 2a01:240:fe00:123::1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms
[root@sam ~]# ping6 ipv6.google.com
PING ipv6.google.com(2a00:1450:8002::68) 56 data bytes
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5000ms
screen 2
[root@ns0 log]# tcpdump -ni eth0:1 'proto 41'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0:1, link-type EN10MB (Ethernet), capture size 96 bytes
09:06:05.033964 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a00:1450:8002::68: ICMP6, echo request, seq 0, length 64
09:06:06.034704 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a00:1450:8002::68: ICMP6, echo request, seq 1, length 64
09:06:07.034599 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a00:1450:8002::68: ICMP6, echo request, seq 2, length 64
09:06:08.034482 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a00:1450:8002::68: ICMP6, echo request, seq 3, length 64
09:06:09.034303 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a00:1450:8002::68: ICMP6, echo request, seq 4, length 64
09:07:39.331584 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, seq 0, length 64
09:07:40.331747 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, seq 1, length 64
09:07:41.331657 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, seq 2, length 64
09:07:42.331568 IP 193.0.234.247 > 78.153.240.201: IP6 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, seq 3, length 64
so if aiccu is working (
# aiccu version
AICCU 2007.01.15-console-linux by Jeroen Massar
)
then why do I get OK and dead
# /etc/init.d/aiccu start
Succesfully retrieved tunnel information for T43649
sock_printf() : "QUIT Better Off Dead"
Tunnel Information for T43649:
POP Id : frmrs01
IPv6 Local : 2a01:240:fe00:123::2/64
IPv6 Remote : 2a01:240:fe00:123::1/64
Tunnel Type : 6in4-static
Adminstate : enabled
Userstate : enabled
RTNETLINK answers: File exists
RTNETLINK answers: File exists
[ OK ]
[root@sam ~]# /etc/init.d/aiccu status
aiccu dead but subsys locked
config aiccu to use IPv4 Endpoint eth0:1 virtual interface?
aiccu dead but subsys locked
That is because aiccu stops running when it has configured a static tunnel, as in that case it is not a daemon as there is nothing left to do.
config aiccu to use IPv4 Endpoint eth0:1 virtual interface?
Shadow Hawkins on Thursday, 21 October 2010 11:50:14
de packets they go out
they no come back...
root@ns0:~# tcpdump -vv -ni eth0:1 net 193.0.234.247
tcpdump: listening on eth0:1, link-type EN10MB (Ethernet), capture size 96 bytes
09:38:02.446136 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: IPv6 (41), length: 124) 193.0.234.247 > 78.153.240.201: IP6 (hlim 64, next-header: ICMPv6 (58), length: 64) 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, length 64, seq 179
09:38:03.445941 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: IPv6 (41), length: 124) 193.0.234.247 > 78.153.240.201: IP6 (hlim 64, next-header: ICMPv6 (58), length: 64) 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, length 64, seq 180
09:38:04.445898 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: IPv6 (41), length: 124) 193.0.234.247 > 78.153.240.201: IP6 (hlim 64, next-header: ICMPv6 (58), length: 64) 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, length 64, seq 181
09:38:05.446683 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: IPv6 (41), length: 124) 193.0.234.247 > 78.153.240.201: IP6 (hlim 64, next-header: ICMPv6 (58), length: 64) 2a01:240:fe00:123::2 > 2a01:240:fe00:123::1: ICMP6, echo request, length 64, seq 182
My laptop has a working teredo tunnel and testing from that end I get:
me@laptop:~$ traceroute6 2a01:240:fe00:123::1
traceroute to 2a01:240:fe00:123::1 (2a01:240:fe00:123::1) from 2001:0:53aa:64c:1c22:2b27:a61d:8aeb, 30 hops max, 16 byte packets
1 2001:470:0:195::2 (2001:470:0:195::2) 251.528 ms 25.674 ms 26.922 ms
2 gige-g2-5.core1.par1.he.net (2001:470:0:195::1) 71.401 ms 22.933 ms 29.93 ms
3 jaguar.ipv6.panap.fr (2001:860:0:6:0:3:781:1) 75.968 ms 27.882 ms 28.324 ms
4 sixxs.cust.ipv6.jaguar-network.net (2a01:240:200:1::2) 100.797 ms 35.547 ms 54.813 ms
5 gw-292.mrs-01.fr.sixxs.net (2a01:240:fe00:123::1) 41.667 ms 40.134 ms 41.066 ms
which is a good start.. but
me@laptop:~$ traceroute6 2a01:240:fe00:123::1
1 * * *
2 * 2001:0:53aa:64c:1c22:2b27:a61d:8aeb (2001:0:53aa:64c:1c22:2b27:a61d:8aeb) 7.081 ms !H 0.125 ms !H
so I try a looking glass:
Tracing the route to cl-292.mrs-01.fr.sixxs.net (2A01:240:FE00:123::2)
1 if-3-0.mcore4.MTT-Montreal.ipv6.as6453.net (2001:5A0:300:200::1) 228 msec 32 msec 8 msec
2 if-11-1-0.1869.core1.PV1-Paris.ipv6.as6453.net (2001:5A0:300:200::12) 96 msec 92 msec 96 msec
3 2001:5A0::22 104 msec 108 msec 104 msec
4 sixxs.cust.ipv6.jaguar-network.net (2A01:240:200:1::2) 120 msec 116 msec 120 msec
5 frmrs01.sixxs.net (2A01:240:202::2) 116 msec 120 msec 120 msec
6 * * *
Tracing the route to gw-292.mrs-01.fr.sixxs.net (2A01:240:FE00:123::1)
1 if-3-0.mcore4.MTT-Montreal.ipv6.as6453.net (2001:5A0:300:200::1) 276 msec 112 msec 292 msec
2 if-14-0-0.1870.core1.PV1-Paris.ipv6.as6453.net (2001:5A0:300:200::16) 108 msec 108 msec 92 msec
3 2001:5A0::22 140 msec 104 msec 184 msec
4 sixxs.cust.ipv6.jaguar-network.net (2A01:240:200:1::2) 140 msec 168 msec 116 msec
5 gw-292.mrs-01.fr.sixxs.net (2A01:240:FE00:123::1) 144 msec 120 msec 116 msec
so 2A01:240:200:1::2 -> 2A01:240:FE00:123::1 (ok fine CDN works for my GW)
but 2A01:240:200:1::2 -> 2A01:240:202::2 -> dev lo (for 2a01:240:fe00:123::2)
is this a router problem?
config aiccu to use IPv4 Endpoint eth0:1 virtual interface?
root@ns0:~# tcpdump -vv -ni eth0:1 net 193.0.234.247
You are missing out on every other packet on that interface, including ICMPs from every hop on the path between your host and the PoP.
You also will want to check any firewalls on that path.
config aiccu to use IPv4 Endpoint eth0:1 virtual interface?
As you have a static tunnel, you don't have to use AICCU, better to use the system's tunnel configuration options, which most likely have a 'local IPv4' option (just like AICCU actually). Then you can configure everything to your hearts content.
config aiccu to use IPv4 Endpoint eth0:1 virtual interface?
Shadow Hawkins on Thursday, 13 January 2011 12:31:01
Very useful information. Thank you. I've finally managed to get my tunnel up. Turned out that my ISP was filtering ipv6-icmp, (and as soon as my ISK gets back out of the red I'm going to change the PoP Location to one closer.)
Thanks again Massar, and thank you Sixxs
|
![[ch]](/s/countries/ch.gif)
on Friday, 22 October 2010 09:39:41
Posting is only allowed when you are