|
Ticket ID: SIXXS #690401 Ticket Status: User PoP: ittrn01 - ITgate (Torino)
Strange routing problem using AICCU
![[it]](/s/countries/it.gif) Shadow Hawkins on Monday, 17 March 2008 13:41:38
I have read and followed the "Reporting Problems" section on the Contact page and
am providing the following details for this report based on the list of items
stated there:
My name is Marco Nenciarini, my NIC handle MANE1-RIPE (email to mnencia@prato.linux.it),
and I'm having trouble with AYIYA tunnel T10465 to ittrn01 .
It worked without problems for about a year then about two month ago it stopped
to work. (I'm on linux 2.6.24.3 with latest aiccu from debian unstable)
Now my connection goes up (AICCU says that everything is ok) and I can see
outcoming packets using a sniffer both on sixxs and eth0 interface but I get no
incoming packets at all (after initial handshake of course), no matter what
host I'm pinging.
When I try to ping my host (or the other tunnel end) from another static tunnel
I own (T9409 to ittrn01) the result is a "No route to host" response from
2001:1418:100:176::1
Tnx in advance
Marco Nenciarini
Problem using AICCU from my laptop
Shadow Hawkins on Tuesday, 18 August 2009 15:27:46
After a year from last issue the tunnel has stopped to work another time about
a week ago.
As stated in firts message of the ticket my name is Marco Nenciarini, my NIC
handle MANE1-RIPE (email to mnencia@prato.linux.it) and I'm having trouble with
AYIYA tunnel T10465 to ittrn01.
there are my diagnostic values:
# ip -6 route show
2001:1418:100:1b6::/64 dev sixxs proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 0
fe80::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev sixxs proto kernel metric 256 mtu 1480 advmss 1420 hoplimit 0
default via 2001:1418:100:1b6::1 dev sixxs metric 1024 mtu 1480 advmss 1420 hoplimit 0
# ifconfig sixxs
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2001:1418:100:1b6::2/64 Scope:Global
inet6 addr: fe80::1418:100:1b6:2/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:464 (464.0 B)
No iptables or ip6tables are present
I'm on linux 2.6.30-1-686 with latest aiccu from debian unstable
My connection goes up (AICCU says that everything is ok) and I can see
outcoming packets using a sniffer both on sixxs and wlan0 interface but I get
no incoming packets at all (after initial handshake of course), no matter what
host I'm pinging.
I tried
2001:1418:100:1b6::1 (my gateway)
2001:838:1:1:210:dcff:fe20:7c7c (noc.sixxs.net)
2001:1418:1d7:1::1 (lorien.prato.linux.it another tunnel i own)
2001:200:0:8002:203:47ff:fea5:3085 (www.kame.net)
without success.
Thanks in Andvance for your help
Problem using AICCU from my laptop
If you send AYIYA packets it will work, but the last one was received:
Last Beat : 2009-08-18 17:05:17 (43772 seconds ago)
And indeed, when there are no AYIYA heartbeats, there is no tunnel.
Please read the contact page and the FAQ.
Problem using AICCU from my laptop
Shadow Hawkins on Wednesday, 19 August 2009 12:08:54
Sorry, but I don't understand the meaning of your response.
I have a laptop with AICCU installed.
The last packet you see is from it, and when it was sent the tunnel was not
working (as i stated in previous post).
The AYIYA tunnel was working for years, and I haven't changed anything in
configuration nor in relevant part of the system.
I've read all the FAQs and Contact page.
Diagnostic values:
NIC-HANDLE: MANE1-RIPE
Distribution: Debian Sid
AICCU version: 20070115-9
uname -a: Linux manwe 2.6.30-1-686 #1 SMP Sat Aug 15 19:11:58 UTC 2009 i686 GNU/Linux
AICCU configuration:
password XXXXXX
tunnel_id T10465
username MANE1-RIPE
protocol tic
server tic.sixxs.net
ipv6_interface sixxs
verbose true
daemonize true
automatic true
requiretls false
Tunnel Information for T10465:
POP Id : ittrn01
IPv6 Local : 2001:1418:100:1b6::2/64
IPv6 Remote : 2001:1418:100:1b6::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.108)
### 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.108 (192.168.1.108) 56(84) bytes of data.
64 bytes from 192.168.1.108: icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from 192.168.1.108: icmp_seq=2 ttl=64 time=0.041 ms
64 bytes from 192.168.1.108: icmp_seq=3 ttl=64 time=0.040 ms
--- 192.168.1.108 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.033/0.038/0.041/0.003 ms
######
####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (213.254.12.34)
### 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 213.254.12.34 (213.254.12.34) 56(84) bytes of data.
64 bytes from 213.254.12.34: icmp_seq=1 ttl=55 time=34.1 ms
64 bytes from 213.254.12.34: icmp_seq=2 ttl=55 time=33.0 ms
64 bytes from 213.254.12.34: icmp_seq=3 ttl=55 time=34.4 ms
--- 213.254.12.34 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 33.076/33.893/34.421/0.623 ms
######
####### [3/8] Traceroute to the PoP (213.254.12.34) 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 213.254.12.34 (213.254.12.34), 30 hops max, 60 byte packets
1 . (192.168.1.1) 2.360 ms 2.585 ms 3.660 ms
2 static-213-205-24-65.clienti.tiscali.it (213.205.24.65) 32.898 ms 34.899 ms 35.373 ms
3 static-213-205-28-50.clienti.tiscali.it (213.205.28.50) 36.712 ms 37.162 ms 37.668 ms
4 static-213-205-56-105.clienti.tiscali.it (213.205.56.105) 57.704 ms 58.146 ms 58.645 ms
5 static-213-205-25-137.clienti.tiscali.it (213.205.25.137) 40.731 ms 42.464 ms 42.915 ms
6 so-7-1-0.mil19.ip4.tinet.net (89.149.186.145) 53.598 ms 30.312 ms so-6-0-0.mil19.ip4.tinet.net (89.149.186.98) 32.148 ms
7 sl-bb20-mil.sprintlink.net (213.200.68.182) 31.585 ms 32.276 ms 31.303 ms
8 sl-gw10-mil-14-0-0.sprintlink.net (217.147.128.37) 32.797 ms 33.169 ms 35.182 ms
9 217.147.129.54 (217.147.129.54) 35.688 ms 36.444 ms 36.980 ms
10 if-0-3.scrappy-monster.core.trn.itgate.net (213.254.31.245) 42.492 ms 44.643 ms 45.119 ms
11 if-0-0.charleston.CBQ.TRN.itgate.net (213.254.0.13) 46.389 ms 47.497 ms 48.025 ms
12 frejus.ITgate.net (213.254.12.34) 48.568 ms 50.060 ms 50.343 ms
######
###### [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
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.040 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.059 ms
64 bytes from ::1: icmp_seq=3 ttl=64 time=0.060 ms
--- ::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.040/0.053/0.060/0.009 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1418:100:1b6::2)
### This confirms that your tunnel is configured
### If it doesn't reply then check your interface and routing tables
PING 2001:1418:100:1b6::2(2001:1418:100:1b6::2) 56 data bytes
64 bytes from 2001:1418:100:1b6::2: icmp_seq=1 ttl=64 time=0.044 ms
64 bytes from 2001:1418:100:1b6::2: icmp_seq=2 ttl=64 time=0.059 ms
64 bytes from 2001:1418:100:1b6::2: icmp_seq=3 ttl=64 time=0.064 ms
--- 2001:1418:100:1b6::2 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.044/0.055/0.064/0.012 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:1b6::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
PING 2001:1418:100:1b6::1(2001:1418:100:1b6::1) 56 data bytes
--- 2001:1418:100:1b6::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms
######
###### [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.
traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:1418:100:1b6::2, 30 hops max, 16 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
29 * * *
30 * * *
######
###### [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
traceroute to www.kame.net (2001:200:0:8002:203:47ff:fea5:3085) from 2001:1418:100:1b6::2, 30 hops max, 16 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
######
###### 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.
$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:1b:24:34:7c:bf brd ff:ff:ff:ff:ff:ff
3: wmaster0: <UP,LOWER_UP> mtu 0 qdisc pfifo_fast state UNKNOWN qlen 1000
link/ieee802.11 00:19:d2:ad:fa:0d brd 00:00:00:00:00:00
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 00:19:d2:ad:fa:0d brd ff:ff:ff:ff:ff:ff
inet 192.168.1.108/24 brd 192.168.1.255 scope global wlan0
inet6 fe80::219:d2ff:fead:fa0d/64 scope link
valid_lft forever preferred_lft forever
5: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
6: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
link/sit 0.0.0.0 brd 0.0.0.0
9: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 32:f0:ef:87:b8:0d brd ff:ff:ff:ff:ff:ff
14: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500
link/[65534]
inet6 2001:1418:100:1b6::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::1418:100:1b6:2/64 scope link
valid_lft forever preferred_lft forever
$ ip route show
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.108
default via 192.168.1.1 dev wlan0
$ ip -6 route show
2001:1418:100:1b6::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev wlan0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
default via 2001:1418:100:1b6::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0
There is no firewall installed (no iptables nor ip6tables loaded)
My clock is synchronized with NTP:
$ ntpq -c peers -n
remote refid st t when poll reach delay offset jitter
==============================================================================
+212.45.144.59 193.204.114.232 2 u 175 256 377 29.630 0.580 0.631
*212.45.144.16 193.204.114.232 2 u 151 256 377 29.850 0.258 0.708
+83.149.158.210 193.204.114.231 2 u 179 256 377 46.380 3.509 1.036
current date is: Wed Aug 19 12:02:27 CEST 2009
Traceroute to me from: http://www.berkom.blazing.de/tools/traceroute.cgi
1 2a01:30:1000::1 1.647 ms 1.287 ms 1.207 ms
2 2001:440:eeee:ff41::1 37.443 ms 36.335 ms 37.976 ms
3 2001:440:eeee:fffd::2 66.097 ms 67.849 ms 70.011 ms
4 2001:1418:1:200::9 83.901 ms 70.676 ms 70.594 ms
5 2001:1418:1:101::d 71.597 ms 74.090 ms 70.276 ms
6 2001:1418:10:2::2 71.664 ms !H 70.904 ms !H 70.319 ms !H
I've included all information I can found.
I hope you can figure out where is the problem.
Problem using AICCU from my laptop
Shadow Hawkins on Wednesday, 19 August 2009 12:27:27
I forgot to attach the following tcpdump output (tunnel up, no ping running)
$ sudo tcpdump -n -s0 -vv -i wlan0 host 213.254.12.34
tcpdump: listening on wlan0, link-type EN10MB (Ethernet), capture size 65535 bytes
12:18:29.473485 IP (tos 0x0, ttl 64, id 56723, offset 0, flags [DF], proto UDP (17), length 72)
192.168.1.108.48142 > 213.254.12.34.5072: [udp sum ok] UDP, length 44
12:19:29.473845 IP (tos 0x0, ttl 64, id 56724, offset 0, flags [DF], proto UDP (17), length 72)
192.168.1.108.48142 > 213.254.12.34.5072: [udp sum ok] UDP, length 44
12:20:29.474189 IP (tos 0x0, ttl 64, id 56725, offset 0, flags [DF], proto UDP (17), length 72)
192.168.1.108.48142 > 213.254.12.34.5072: [udp sum ok] UDP, length 44
12:21:29.474380 IP (tos 0x0, ttl 64, id 56726, offset 0, flags [DF], proto UDP (17), length 72)
192.168.1.108.48142 > 213.254.12.34.5072: [udp sum ok] UDP, length 44
12:22:29.474680 IP (tos 0x0, ttl 64, id 56727, offset 0, flags [DF], proto UDP (17), length 72)
192.168.1.108.48142 > 213.254.12.34.5072: [udp sum ok] UDP, length 44
State change: user
The state of this ticket has been changed to user
Strange routing problem using AICCU
Please actually read the "Reporting Problems" section on the Contact page.
Most likely your routing tables locally are wrong. Check the list, use it, and reply back with all the details, otherwise we can't help.
Strange routing problem using AICCU
Shadow Hawkins on Monday, 17 March 2008 14:47:32
I have read and followed the "Reporting Problems" section on the Contact page and
am providing the following details for this report based on the list of items
stated there:
This is my IPv6 routing table. I don't see anything wrong on it.
# ip -6 route show
2001:1418:100:1b6::/64 dev sixxs metric 256 expires 21331502sec mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev wlan0 metric 256 expires 21328965sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev sixxs metric 256 expires 21331502sec mtu 1280 advmss 1220 hoplimit 4294967295
default via 2001:1418:100:1b6::1 dev sixxs metric 1024 expires 21331502sec mtu 1280 advmss 1220 hoplimit 4294967295
Moreover I stated that AICCU/AYIYA packets are coming out from my machine (I can
see it both on machine external interface using wireshark and on gateway using
tcpdump) but no one comes back.
This is my sixxs interface from ifconfig
# ifconfig sixxs
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2001:1418:100:1b6::2/64 Scope:Global
inet6 addr: fe80::1418:100:1b6:2/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1675 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:174032 (169.9 KiB)
No ip6tables are present and these are the ip6 related modules loaded.
sit 10660 0
tunnel4 3688 1 sit
ipv6 240772 36 sit
I hope these information are enough
Thanks in advance
Strange routing problem using AICCU
Latency to your IPv4 endpoint (79.26.134.170) seems very high:
64 bytes from 79.26.134.170: icmp_seq=2 ttl=55 time=597 ms
PoP side of the tunnel is up:
64 bytes from 2001:1418:100:1b6::1: icmp_seq=1 ttl=51 time=26.3 ms
Client side seems to respond now too (but didn't a few moments ago...):
64 bytes from 2001:1418:100:1b6::2: icmp_seq=1 ttl=50 time=91.6 ms
And now very high latency again:
64 bytes from 2001:1418:100:1b6::2: icmp_seq=1 ttl=50 time=681 ms
64 bytes from 2001:1418:100:1b6::2: icmp_seq=2 ttl=50 time=719 ms
64 bytes from 2001:1418:100:1b6::2: icmp_seq=3 ttl=50 time=608 ms
64 bytes from 2001:1418:100:1b6::2: icmp_seq=4 ttl=50 time=643 ms
Seems something in the middle has an issue at least:
1. if-1-12.charleston.CBQ.TRN.ITgate.net 0.0% 14 0.5 0.6 0.3 1.9 0.5
2. if-0-1.scooby-monster.core.TRN.itgate.net 0.0% 14 1.1 11.8 0.3 157.5 41.9
3. telecom-pub1.topix.it 0.0% 14 0.7 0.8 0.7 1.3 0.2
4. r-to70-r-to88.opb.interbusiness.it 0.0% 13 18.7 18.8 18.7 18.9 0.1
5. crs-mi001-r-to70.opb.interbusiness.it 50.0% 13 18.9 19.1 18.6 19.9 0.5
6. 151.99.98.162 69.2% 13 20.8 20.8 20.5 21.4 0.4
7. r-fi62-crs-rm001.opb.interbusiness.it 0.0% 13 18.4 19.6 18.4 33.0 4.0
8. 80.19.134.64 0.0% 13 17.5 17.5 17.4 17.6 0.0
9. host14-2-static.45-88-b.business.telecomitalia.it 0.0% 13 18.6 18.5 18.4 18.7 0.1
10. host170-134-dynamic.26-79-r.retail.telecomitalia.it 0.0% 13 560.1 570.3 499.3 694.0 49.2
Though the high latency is on the last hop...
Strange routing problem using AICCU
Shadow Hawkins on Monday, 17 March 2008 15:22:23
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Sorry for the high latency, I was downloading some pieces of software from eclipse site.
At the moment my tunnel seem to be back to life.
I can see the dancing kame again :P
Thanks for the support
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 19 August 2009 08:15:35
Posting is only allowed when you are