|
Ticket ID: SIXXS #983075 Ticket Status: User PoP: nlede01 - BIT BV (Ede)
T14835 is not working.
![[cz]](/s/countries/cz.gif) Shadow Hawkins on Monday, 23 February 2009 18:56:02
Hello,
on my FreeBSD box I have dynamic AYIYA tunnel. Number of this tunnel is T14835.
The problem is that I cannot ping the remote endpoint of this tunnel and I cannot reach the rest of IPv6 internet.
I tried to use another tunnel on another PoP and it worked perfect.
Information about T14835.
PoP name: nlede01
Prefix: 2001:7b8:2ff:1d5::1/64.
(And, the counters on details page stopped at 23:15)
Regards, Jan
T14835 is not working.
Please actually read the "Reporting Problems" section on the Contact page and provide the requested details.
State change: user
The state of this ticket has been changed to user
sixxs-aiccu test
Shadow Hawkins on Tuesday, 24 February 2009 00:26:38
[root@postak /home/honza]# sixxs-aiccu test
route: writing to routing socket: File exists
add net default: gateway 2001:7b8:2ff:1d5::1: route already in table
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.100)
### This should return so called 'echo replies'
### If it doesn't then check your firewall settings
### Your local endpoint should always be pingable
### It could also indicate problems with your IPv4 stack
PING 192.168.1.100 (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: icmp_seq=0 ttl=64 time=0.097 ms
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=0.132 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.131 ms
--- 192.168.1.100 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.097/0.120/0.132/0.016 ms
######
Did this work? [Y/n]
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (193.109.122.244)
### These pings should reach the PoP and come back to you
### In case there are problems along the route between your
### host and the PoP this could not return replies
### Check your firewall settings if problems occur
PING 193.109.122.244 (193.109.122.244): 56 data bytes
64 bytes from 193.109.122.244: icmp_seq=0 ttl=47 time=63.857 ms
64 bytes from 193.109.122.244: icmp_seq=1 ttl=47 time=39.969 ms
64 bytes from 193.109.122.244: icmp_seq=2 ttl=46 time=44.869 ms
--- 193.109.122.244 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 39.969/49.565/63.857/10.302 ms
######
Did this work? [Y/n]
####### [3/8] Traceroute to the PoP (193.109.122.244) over IPv4
### This traceroute should reach the PoP
### In case this traceroute fails then you have no connectivity
### to the PoP and this is most probably the problem
traceroute to 193.109.122.244 (193.109.122.244), 64 hops max, 40 byte packets
1 stokurev (192.168.1.1) 0.525 ms 0.504 ms 0.473 ms
^C
######
Did this work? [Y/n]
###### [4/8] Checking if we can ping IPv6 localhost (::1)
### This confirms if your IPv6 is working
### If ::1 doesn't reply then something is wrong with your IPv6 stack
PING6(56=40+8+8 bytes) ::1 --> ::1
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=0 hlim=64 dst=::1%2 time=0.862 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1%2 time=0.349 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1%2 time=0.344 ms
--- ::1 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.344/0.518/0.862/0.243 ms
######
Did this work? [Y/n]
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:7b8:2ff:1d5::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING6(56=40+8+8 bytes) 2001:7b8:2ff:1d5::2 --> 2001:7b8:2ff:1d5::2
16 bytes from 2001:7b8:2ff:1d5::2: Echo Request
16 bytes from 2001:7b8:2ff:1d5::2, icmp_seq=0 hlim=64 dst=2001:7b8:2ff:1d5::2%3 time=0.992 ms
16 bytes from 2001:7b8:2ff:1d5::2: Echo Request
16 bytes from 2001:7b8:2ff:1d5::2, icmp_seq=1 hlim=64 dst=2001:7b8:2ff:1d5::2%3 time=0.376 ms
16 bytes from 2001:7b8:2ff:1d5::2: Echo Request
16 bytes from 2001:7b8:2ff:1d5::2, icmp_seq=2 hlim=64 dst=2001:7b8:2ff:1d5::2%3 time=0.325 ms
--- 2001:7b8:2ff:1d5::2 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.325/0.564/0.992/0.303 ms
######
Did this work? [Y/n]
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:7b8:2ff:1d5::1)
### This confirms the reachability of the other side of the tunnel
### If it doesn't reply then check your interface and routing tables
### Don't forget to check your firewall of course
### If the previous test was succesful then this could be both
### a firewalling and a routing/interface problem
PING6(56=40+8+8 bytes) 2001:7b8:2ff:1d5::2 --> 2001:7b8:2ff:1d5::1
--- 2001:7b8:2ff:1d5::1 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
######
Did this work? [Y/n]
###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net)
### This confirms that you can reach the central machine of SixXS
### If that one is reachable you should be able to reach most IPv6 destinations
### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection
### If your browser supports IPv6 and uses it of course.
traceroute6 to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:7b8:2ff:1d5::2, 64 hops max, 12 byte packets
^C
######
Did this work? [Y/n]
###### [8/8] Traceroute6 to (www.kame.net)
### This confirms that you can reach a Japanese IPv6 destination
### If that one is reachable you should be able to reach most IPv6 destinations
### You should also check http://www.kame.net which should display
### a animated kame (turtle), of course only when your browser supports and uses IPv6
traceroute6 to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:7b8:2ff:1d5::2, 64 hops max, 12 byte packets
^C
######
Did this work? [Y/n]
###### ACCU Quick Connectivity Test (done)
### Either the above all works and gives no problems
### or it shows you where what goes wrong
### Check the SixXS FAQ (http://www.sixxs.net/faq/
### for more information and possible solutions or hints
### Don't forget to check the Forums (http://www.sixxs.net/forum/)
### for a helping hand.
### Passing the output of 'aiccu autotest >aiccu.log' is a good idea.
*** press a key to continue ***
[root@postak /home/honza]#
My ISP drops ICMP packets that traceroute command generates
sixxs-aiccu test
The fact that you get errors already at the top should explain you that something is wrongly setup there already.
AICCU does not fix misconfigured setups. That would be a near impossible thing to do correctly. Check your routing tables, check your interfaces and clean it up. See the "Reporting Problems" checklist section on the contact page for more details.
sixxs-aiccu test
Shadow Hawkins on Tuesday, 24 February 2009 09:36:49
No effect after deletion this default route.
When I started the tunnel, this routes appears.
Result of route monitor command:
[root@postak /home/honza]# route monitor
got message of size 96 on Tue Feb 24 09:33:28 2009
RTM_IFINFO: iface status change: len 96, if# 3, link: unknown, flags:<UP,PTP,MULTICAST>
got message of size 136 on Tue Feb 24 09:33:28 2009
RTM_NEWADDR: address being added to iface: len 136, metric 0, flags:<CLONING>
sockaddrs: <NETMASK,IFP,IFA,BRD>
ffff:ffff:ffff:ffff:: tun0 fe80::2b0:d0ff:fed4:aa8c%tun0 default
got message of size 176 on Tue Feb 24 09:33:28 2009
RTM_ADD: Add Route: len 176, pid: 0, seq 0, errno 0, flags:<UP,HOST,LLINFO,LOCAL>
locks: inits:
sockaddrs: <DST,GATEWAY>
fe80::2b0:d0ff:fed4:aa8c%tun0
got message of size 100 on Tue Feb 24 09:33:28 2009
RTM_NEWMADDR: new multicast group membership on iface: len 100,
sockaddrs: <IFP,IFA>
tun0 ff02::1:ffd4:aa8c%tun0
got message of size 100 on Tue Feb 24 09:33:28 2009
RTM_NEWMADDR: new multicast group membership on iface: len 100,
sockaddrs: <IFP,IFA>
tun0 ff02::1%tun0
got message of size 100 on Tue Feb 24 09:33:28 2009
RTM_NEWMADDR: new multicast group membership on iface: len 100,
sockaddrs: <IFP,IFA>
tun0 ff02::2:fff3:71b9%tun0
got message of size 100 on Tue Feb 24 09:33:28 2009
RTM_NEWMADDR: new multicast group membership on iface: len 100,
sockaddrs: <IFP,IFA>
tun0 ff01:3::1
got message of size 96 on Tue Feb 24 09:33:28 2009
RTM_IFINFO: iface status change: len 96, if# 3, link: unknown, flags:<UP,PTP,RUNNING,MULTICAST>
got message of size 136 on Tue Feb 24 09:33:28 2009
RTM_NEWADDR: address being added to iface: len 136, metric 0, flags:<CLONING>
sockaddrs: <NETMASK,IFP,IFA,BRD>
(0) 0 0 0 ffff ffff ffff ffff 0 0 0 0 0 0 tun0 fe80::4b8:2ff:1d5:2%tun0 default
got message of size 176 on Tue Feb 24 09:33:28 2009
RTM_ADD: Add Route: len 176, pid: 0, seq 0, errno 0, flags:<UP,HOST,LLINFO,LOCAL>
locks: inits:
sockaddrs: <DST,GATEWAY>
fe80::4b8:2ff:1d5:2%tun0
got message of size 100 on Tue Feb 24 09:33:28 2009
RTM_NEWMADDR: new multicast group membership on iface: len 100,
sockaddrs: <IFP,IFA>
tun0 ff02::1:ffd5:2%tun0
got message of size 160 on Tue Feb 24 09:33:28 2009
RTM_NEWADDR: address being added to iface: len 160, metric 0, flags:<UP>
sockaddrs: <NETMASK,IFP,IFA,BRD>
(0) 0 0 0 ffff ffff ffff ffff ffff ffff ffff ffff 0 0 tun0 cl-470.ede-01.nl.sixxs.net gw-470.ede-01.nl.sixxs.net
got message of size 176 on Tue Feb 24 09:33:28 2009
RTM_ADD: Add Route: len 176, pid: 0, seq 0, errno 0, flags:<UP,HOST,LLINFO,LOCAL>
locks: inits:
sockaddrs: <DST,GATEWAY>
cl-470.ede-01.nl.sixxs.net
got message of size 100 on Tue Feb 24 09:33:28 2009
RTM_NEWMADDR: new multicast group membership on iface: len 100,
sockaddrs: <IFP,IFA>
tun0 ff02::1:ff00:2%tun0
got message of size 152 on Tue Feb 24 09:33:28 2009
RTM_ADD: Add Route: len 152, pid: 2103, seq 1, errno 17, flags:<UP,GATEWAY,STATIC>
locks: inits:
sockaddrs: <DST,GATEWAY,NETMASK>
:: gw-470.ede-01.nl.sixxs.net ::
But nothing happens.
Result of tcpdump (ping6 -c 5 www.ripe.net):
[root@postak /home/honza]# tcpdump -i tun0 -s 1500
tcpdump: WARNING: tun0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tun0, link-type NULL (BSD loopback), capture size 1500 bytes
09:35:23.244991 IP6 cl-470.ede-01.nl.sixxs.net > aquila.ripe.net: ICMP6, echo request, seq 0, length 16
09:35:24.245537 IP6 cl-470.ede-01.nl.sixxs.net > aquila.ripe.net: ICMP6, echo request, seq 1, length 16
09:35:25.245398 IP6 cl-470.ede-01.nl.sixxs.net > aquila.ripe.net: ICMP6, echo request, seq 2, length 16
09:35:26.245286 IP6 cl-470.ede-01.nl.sixxs.net > aquila.ripe.net: ICMP6, echo request, seq 3, length 16
09:35:27.245150 IP6 cl-470.ede-01.nl.sixxs.net > aquila.ripe.net: ICMP6, echo request, seq 4, length 16
09:35:28.243946 IP6 cl-470.ede-01.nl.sixxs.net > gw-470.ede-01.nl.sixxs.net: ICMP6, neighbor solicitation, who has gw-470.ede-01.nl.sixxs.net, length 24
09:35:29.243820 IP6 cl-470.ede-01.nl.sixxs.net > gw-470.ede-01.nl.sixxs.net: ICMP6, neighbor solicitation, who has gw-470.ede-01.nl.sixxs.net, length 24
09:35:30.243698 IP6 cl-470.ede-01.nl.sixxs.net > gw-470.ede-01.nl.sixxs.net: ICMP6, neighbor solicitation, who has gw-470.ede-01.nl.sixxs.net, length 24
sixxs-aiccu test
Shadow Hawkins on Tuesday, 24 February 2009 19:00:08
What is very interesting that when I use another tunnel it works perfect.
T14835 is not working.
Shadow Hawkins on Tuesday, 24 February 2009 00:30:43
[root@postak /home/honza]# pkg_info | grep sixxs
sixxs-aiccu-20070115 SixXS IPv6 TIC+ tunnel broker heartbeat client
[root@postak /home/honza]# ifconfig
xl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=9<RXCSUM,VLAN_MTU>
ether 00:b0:d0:d4:aa:8c
inet6 fe80::2b0:d0ff:fed4:aa8c%xl0 prefixlen 64 scopeid 0x1
inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255
inet6 2001:7b8:3e2::1 prefixlen 64
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff000000
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
inet6 fe80::2b0:d0ff:fed4:aa8c%tun0 prefixlen 64 scopeid 0x3
inet6 fe80::4b8:2ff:1d5:2%tun0 prefixlen 64 scopeid 0x3
inet6 2001:7b8:2ff:1d5::2 --> 2001:7b8:2ff:1d5::1 prefixlen 128
Opened by PID 5080
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:bd:01:5f:00:00
inet6 fe80::2bd:1ff:fe5f:0%tap0 prefixlen 64 scopeid 0x4
inet 172.30.0.1 netmask 0xffffff00 broadcast 172.30.0.255
Opened by PID 887
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 36:fc:e2:88:1d:f6
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 4 priority 128 path cost 2000000
member: xl0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
ifmaxaddr 0 port 1 priority 128 path cost 200000
[root@postak /home/honza]# netstat -r
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default stokurev UGS 0 162873 xl0
localhost localhost UH 0 1601 lo0
172.30.0.0 link#4 UC 0 0 tap0
vpn-002 00:ff:6e:19:57:60 UHLW 1 7644 tap0 668
172.30.0.255 ff:ff:ff:ff:ff:ff UHLWb 1 115 tap0
192.168.1.0 link#1 UC 0 0 xl0
stokurev 00:1c:10:9a:38:3b UHLW 2 353 xl0 1193
postak 00:b0:d0:d4:aa:8c UHLW 1 30 lo0
192.168.1.255 ff:ff:ff:ff:ff:ff UHLWb 1 104 xl0
Internet6:
Destination Gateway Flags Netif Expire
:: localhost UGRS lo0 =>
default gw-470.ede-01.nl.s UGS tun0
localhost localhost UHL lo0
::ffff:0.0.0.0 localhost UGRS lo0
gw-470.ede-01.nl.s link#3 UHL tun0
cl-470.ede-01.nl.s link#3 UHL lo0
2001:7b8:3e2:: link#1 UC xl0
2001:7b8:3e2::1 00:b0:d0:d4:aa:8c UHL lo0
fe80:: localhost UGRS lo0
fe80::%xl0 link#1 UC xl0
fe80::2b0:d0ff:fed 00:b0:d0:d4:aa:8c UHL lo0
fe80::30d8:fb46:2a 00:1f:3a:1b:55:74 UHLW xl0
fe80::%lo0 fe80::1%lo0 U lo0
fe80::1%lo0 link#2 UHL lo0
fe80::2b0:d0ff:fed link#3 UHL lo0
fe80::4b8:2ff:1d5: link#3 UHL lo0
fe80::%tap0 link#4 UC tap0
fe80::2bd:1ff:fe5f 00:bd:01:5f:00:00 UHL lo0
ff01:1:: link#1 UC xl0
ff01:2:: localhost UC lo0
ff01:3:: link#3 UC tun0
ff01:4:: link#4 UC tap0
ff02:: localhost UGRS lo0
ff02::%xl0 link#1 UC xl0
ff02::%lo0 localhost UC lo0
ff02::%tun0 link#3 UC tun0
ff02::%tap0 link#4 UC tap0
[root@postak /home/honza]# uname -a
FreeBSD postak.betik.cz 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #8: Mon Feb 23 17:44:33 CET 2009 honza@postak.betik.cz:/usr/obj/usr/src/sys/EAN-CODE i386
[root@postak /home/honza]#
T14835 is not working.
Shadow Hawkins on Tuesday, 24 February 2009 00:32:51
I dont use any IPv6 firewall.
My internet connection is over cable modem.
T14835 is not working.
Shadow Hawkins on Wednesday, 25 February 2009 02:46:44
Some hints?
I tried to use this tunnel on my laptop and IT IS NOT FUNCTIONAL. With another tunnel it works perfect.
T14835 is not working.
Shadow Hawkins on Wednesday, 25 February 2009 02:50:03
Tag [/code] is not closed
|
![[ch]](/s/countries/ch.gif)
on Monday, 23 February 2009 20:20:28
Posting is only allowed when you are