|
Ubuntu Server (10.10) - 2.6.35.22 - Cannot ping the pop
![[us]](/s/countries/us.gif) Carmen Sandiego on Wednesday, 10 November 2010 22:04:56
I've been looking around the net and the tickets, usually I can self-help on these kind of things but I'm at the end of my tether (and IPv6 is very new to me).
I'm using aiccu to connect to my IPv6 tunnel, it appears to connect fine, the tunnel adapter "sixxs" is created and has the correct information but I cannot ping the SixXS IPv6 IP (also tried Google's IPv6 IP).
Anyone know what I'm doing wrong here, all the tutorials I've found online it just "works".
/var/log/syslog
Nov 10 14:43:39 server01 aiccu[26160]: sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)"
Nov 10 14:43:39 server01 aiccu[26160]: sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-linux Linux/2.6.35-22-server"
Nov 10 14:43:39 server01 aiccu[26160]: sock_getline() : "200 Client Identity accepted"
Nov 10 14:43:39 server01 aiccu[26160]: sock_printf() : "get unixtime"
Nov 10 14:43:39 server01 aiccu[26160]: sock_getline() : "200 1289421819"
Nov 10 14:43:39 server01 aiccu[26160]: sock_printf() : "starttls"
Nov 10 14:43:40 server01 aiccu[26160]: sock_getline() : "400 This service is not SSL enabled (yet)"
Nov 10 14:43:40 server01 aiccu[26160]: TIC Server does not support TLS but TLS is not required, continuing
Nov 10 14:43:40 server01 aiccu[26160]: sock_printf() : "username ****-*****"
Nov 10 14:43:40 server01 aiccu[26160]: sock_getline() : "200 ****-***** choose your authentication challenge please"
Nov 10 14:43:40 server01 aiccu[26160]: sock_printf() : "challenge md5"
Nov 10 14:43:40 server01 aiccu[26160]: sock_getline() : "200 ********************************"
Nov 10 14:43:40 server01 aiccu[26160]: sock_printf() : "authenticate md5 ********************************"
Nov 10 14:43:40 server01 aiccu[26160]: sock_getline() : "200 Successfully logged in using md5 as ****-***** (Mike ******)"
Nov 10 14:43:40 server01 aiccu[26160]: sock_printf() : "tunnel list"
Nov 10 14:43:40 server01 aiccu[26160]: sock_getline() : "201 Listing tunnels"
Nov 10 14:43:40 server01 aiccu[26160]: sock_getline() : "T4***5 2604:****:***:**::2 heartbeat uschi03"
Nov 10 14:43:40 server01 aiccu[26160]: sock_getline() : "202 <tunnel_id> <ipv6_endpoint> <ipv4_endpoint> <pop_name>"
Nov 10 14:43:40 server01 aiccu[26160]: sock_printf() : "tunnel show T4***5"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "201 Showing tunnel information for T4***5"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "TunnelId: T4***5"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "Type: 6in4-heartbeat"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "IPv6 Endpoint: 2604:****:**:**::2"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "IPv6 POP: 2604:****:**:**::1"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "IPv6 PrefixLength: 64"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "Tunnel MTU: 1280"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "Tunnel Name: My First Tunnel"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "POP Id: uschi03"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "IPv4 Endpoint: heartbeat"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "IPv4 POP: 38.229.76.3"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "UserState: enabled"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "AdminState: enabled"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "Password: ***********************"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "Heartbeat_Interval: 60"
Nov 10 14:43:41 server01 aiccu[26160]: sock_getline() : "202 Done"
Nov 10 14:43:41 server01 aiccu[26160]: Successfully retrieved tunnel information for ******
Nov 10 14:43:41 server01 aiccu[26160]: sock_printf() : "QUIT Forsaken"
Nov 10 14:43:41 server01 aiccu[26165]: AICCU running as PID 26165
Nov 10 14:43:41 server01 kernel: [1739878.645669] sixxs: Disabled Privacy Extensions
Nov 10 14:43:41 server01 aiccu[26165]: heartbeat_socket() - IPv4 : 192.168.1.10
Nov 10 14:43:41 server01 aiccu[26165]: [HB] HEARTBEAT TUNNEL 2604:****:***:**::2 sender 12******21 ***********************
#sudo ip -6 route
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
default via 2604:****:***:**::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
#ifconfig
eth0 Link encap:Ethernet HWaddr 00:**:**:**:**:0a
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::218:f3ff:fea6:420a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2297054 errors:0 dropped:0 overruns:0 frame:0
TX packets:1940224 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2306829361 (2.3 GB) TX bytes:1345487240 (1.3 GB)
Interrupt:23 Base address:0xa000
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:4645 errors:0 dropped:0 overruns:0 frame:0
TX packets:4645 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1564450 (1.5 MB) TX bytes:1564450 (1.5 MB)
sixxs Link encap:IPv6-in-IPv4
inet6 addr: fe80::****:1/64 Scope:Link
inet6 addr: fe80::****:10a/64 Scope:Link
inet6 addr: 2604:****:***:**::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1280 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
#ping6 2604:****:***:**::1
PING 2604:****:***:**::1(2604:****:***:**::1) 56 data bytes
^C
--- 2604:****:***:**::1 ping statistics ---
22 packets transmitted, 0 received, 100% packet loss, time 21005ms
#sudo tcpdump -i sixxs -vv -n
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: listening on sixxs, link-type RAW (Raw IP), capture size 65535 bytes
14:46:57.016456 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 9
14:46:58.016415 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 10
14:46:59.016427 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 11
14:47:00.016443 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 12
14:47:01.016420 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 13
14:47:02.016465 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 14
14:47:03.016407 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 15
14:47:04.016412 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 16
14:47:05.016407 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 64) 2604:****:***:**::2 > 2604:****:***:**::1: [icmp6 sum ok] ICMP6, echo request, length 64, seq 17
^C
9 packets captured
9 packets received by filter
0 packets dropped by kernel
Ubuntu Server (10.10) - 2.6.35.22 - Cannot ping the pop
Why are you trying to blank out all the useful address bits?
#sudo ip -6 route fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295 default via 2604:****:***:**::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
It seems you do not have any routes for the interface itself, that is quite odd.
eth0 Link encap:Ethernet HWaddr 00:**:**:**:**:0a inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
You have a RFC1918 address, thus unless you properly configure your NAT box protocol-41 tunnels (thus the static and heartbeat ones) won't work.
Simple solution: use AYIYA, which indeed, just works (unless you don't have tun/tap support on your host or you have a very restrictive firewall somewhere)
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
That interface never saw a single bit of traffic, not surprising that it does not work.
Also, how do your firewall rules, both IPv4 and IPv6 look like
#sudo tcpdump -i sixxs -vv -n
You really want to look at the underlying IPv4 interface.
Also when there is a '#' in your prompt it generally indicates you are root already, thus no need to sudo.
Ubuntu Server (10.10) - 2.6.35.22 - Cannot ping the pop
Carmen Sandiego on Wednesday, 10 November 2010 22:49:07
****'s .. Paranoia! :-) The "#", yer I'm not really root, I just take the bash prompt out and replace it with a "#", again, Paranoia! :-)
Well, I don't pretend to understand what's going on here (yet), but I can't argue with the results:
#traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2001:4860:b007::69) from 2604:****:***:**::2, 30 hops max, 24 byte packets
1 gw-50.chi-03.us.sixxs.net (2604:****:***:**::1) 12.753 ms 12.227 ms 13.006 ms
2 2620:0:6b0:a::1 (2620:0:6b0:a::1) 12.525 ms 14.701 ms 12.094 ms
3 2607:f4e8:2:1::1 (2607:f4e8:2:1::1) 12.7 ms 12.94 ms 22.009 ms
4 2607:f4e8:1:2b::1 (2607:f4e8:1:2b::1) 16.779 ms 14.344 ms 15.92 ms
5 10gigabitethernet4-1.core1.chi1.he.net (2001:504:0:4::6939:1) 14.998 ms 19.173 ms 14.613 ms
6 2001:470:0:bf::2 (2001:470:0:bf::2) 14.255 ms 14.032 ms 13.965 ms
7 2001:4860::1:0:3f7 (2001:4860::1:0:3f7) 24.34 ms 15.446 ms 14.698 ms
8 2001:4860::1:0:1d1 (2001:4860::1:0:1d1) 25.062 ms 25.421 ms 25.822 ms
9 2001:4860::38 (2001:4860::38) 25.821 ms 26.345 ms 25.322 ms
10 2001:4860:0:1::d (2001:4860:0:1::d) 38.398 ms 26.659 ms 36.079 ms
11 iy-in-x69.1e100.net (2001:4860:b007::69) 26.166 ms 25.943 ms 25.827 ms
Hurray! Thank you very much, it's appreciated (and quick too!)
Ubuntu Server (10.10) - 2.6.35.22 - Cannot ping the pop
Well, I don't pretend to understand what's going on here (yet), but I can't argue with the results:
AYIYA (IPv6 inside UDP in IPv4) and that is something your NAT box understands, while before you had a heartbeat tunnel, which uses protocol 41 (thus IPv6 directly inside IPv4) which is something that your NAT box obviously did not like at all...
1 gw-50.chi-03.us.sixxs.net (2604:****:***:**::1) 12.753 ms 12.227 ms 13.006 ms
You do realize that hostnames resolve to IP addresses.... ?
Ubuntu Server (10.10) - 2.6.35.22 - Cannot ping the pop
Carmen Sandiego on Thursday, 11 November 2010 01:11:15
Whoops, it was bound to happen!
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 10 November 2010 22:25:56
Posting is only allowed when you are