Ticket ID: SIXXS #5950094 Ticket Status: User PoP: fihel01 - DNA Oy (Helsinki)
IPv6 broken
Shadow Hawkins on Tuesday, 22 November 2011 22:08:45
Hi,
A second time reporting a ticket, here we go:
It seems that my connection to my PoP is somewhat broken. For example when I try to connect to any other IPv6 server, the connection times out.
The problem occured some two months back, but I really didn't have the time to look into it until now. My PoP is up and running according to the PoP-page.
AICCU stop and AICCU start didn't resolve the problem, neither did the reboot of my server.
NIC handle: MLO3-SIXXS
Tunnel Information for T23766
Tunnel NameMy First Tunnel
PoP Namefihel01PoP
LocationHelsinki, Finland Finland
PoP IPv462.78.96.38
TIC Server tic.sixxs.net (default in AICCU)
Your LocationHelsinki, Finland Finland
Your IPv4AYIYA, currently unknown
IPv6 Prefix2001:14b8:100:282::1/64
PoP IPv62001:14b8:100:282::1
Your IPv62001:14b8:100:282::2
Created2009-10-28 16:31:05 CET
StateAYIYA (automatically enabled on the fly)
Oh and about my setup: I'm sure everything is set-up just fine, since everything was okay for a long time before this unfortunate breakage. If it helps, I'm running an Ubuntu server (lucid) where AICCU resides.
Everything works just fine before this in aiccu test:
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:14b8:100:282::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 successful then this could be both
### a firewalling and a routing/interface problem
PING 2001:14b8:100:282::1(2001:14b8:100:282::1) 56 data bytes
--- 2001:14b8:100:282::1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2014ms
######
###### [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), 30 hops max, 80 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
...
###### ACCU Quick Connectivity Test (done)
Here's what "iptables -nvL ; ip6tables -nvL ip -4 route ; ip -6 route ;ifconfig" gives:
Chain INPUT (policy ACCEPT 5792K packets, 3212M bytes)
pkts bytes target prot opt in out source destination
4888K 3050M fail2ban-ssh tcp -- * * 0.0.0.0/0 0.0.0.0/0 multiport dports 22
0 0 fail2ban-vsftpd tcp -- * * 0.0.0.0/0 0.0.0.0/0 multiport dports 21,20,990,989
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 3416K packets, 2027M bytes)
pkts bytes target prot opt in out source destination
Chain fail2ban-ssh (1 references)
pkts bytes target prot opt in out source destination
4886K 3050M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0
Chain fail2ban-vsftpd (1 references)
pkts bytes target prot opt in out source destination
0 0 RETURN all -- * * 0.0.0.0/0 0.0.0.0/0
ip6tables v1.4.4: option `-4' requires an argument
Try `ip6tables -h' or 'ip6tables --help' for more information.
2001:14b8:100:282::/64 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev br0 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:14b8:100:282::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 0
br0 Link encap:Ethernet HWaddr 00:09:6b:9d:65:2c
inet addr:192.168.100.200 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::209:6bff:fe9d:652c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8798174 errors:0 dropped:0 overruns:0 frame:0
TX packets:4486732 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3724964598 (3.7 GB) TX bytes:2136317458 (2.1 GB)
eth0 Link encap:Ethernet HWaddr 00:09:6b:9d:65:2c
inet6 addr: fe80::209:6bff:fe9d:652c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8798247 errors:0 dropped:0 overruns:0 frame:0
TX packets:4486745 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3851164152 (3.8 GB) TX bytes:2136319636 (2.1 GB)
eth1 Link encap:Ethernet HWaddr 00:0e:2e:3b:8b:aa
UP BROADCAST PROMISC MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1420 errors:0 dropped:0 overruns:0 frame:0
TX packets:1420 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:128026 (128.0 KB) TX bytes:128026 (128.0 KB)
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: 2001:14b8:100:282::2/64 Scope:Global
inet6 addr: fe80::14b8:100:282: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:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:48 (48.0 B)
And here's a tcpdump:
00:05:54.253268 IP (tos 0x0, ttl 63, id 51528, offset 0, flags [DF], proto
UDP (17), length 176) hoasnet-fe2edd00-135.dhcp.inet.fi.34819 >
fihel01.sixxs.net.5072: UDP, length 148
00:05:55.252758 IP (tos 0x0, ttl 63, id 51529, offset 0, flags [DF], proto
UDP (17), length 176) hoasnet-fe2edd00-135.dhcp.inet.fi.34819 >
fihel01.sixxs.net.5072: UDP, length 148
00:05:56.252758 IP (tos 0x0, ttl 63, id 51530, offset 0, flags [DF], proto
UDP (17), length 176) hoasnet-fe2edd00-135.dhcp.inet.fi.34819 >
fihel01.sixxs.net.5072: UDP, length 148
00:05:57.252724 IP (tos 0x0, ttl 63, id 51531, offset 0, flags [DF], proto
UDP (17), length 176) hoasnet-fe2edd00-135.dhcp.inet.fi.34819 >
fihel01.sixxs.net.5072: UDP, length 148
00:05:58.252723 IP (tos 0x0, ttl 63, id 51532, offset 0, flags [DF], proto
UDP (17), length 176) hoasnet-fe2edd00-135.dhcp.inet.fi.34819 >
fihel01.sixxs.net.5072: UDP, length 148
State change: user
Jeroen Massar on Tuesday, 22 November 2011 23:36:06
The state of this ticket has been changed to user
IPv6 broken
Shadow Hawkins on Wednesday, 23 November 2011 16:44:47
I changed the tunnel type from AYIYA to Heartbeat and now it is working. Any idea why the pop was not responding to the UDP packets but works with proto 41?
IPv6 broken
Jeroen Massar on Wednesday, 23 November 2011 17:50:59
Swapping between proto-41 and AYIYA can sometimes yield strange results with the v3 PoPs, this is what may have happened.
But when I pinged your tunnel due to your request above, it worked and it was AYIYA, thus then it worked just fine.
Posting is only allowed when you are logged in. |