|
Ticket ID: SIXXS #1319259 Ticket Status: User PoP: ittrn01 - ITgate (Torino)
Tunnel T24687 not working properly
![[it]](/s/countries/it.gif) Shadow Hawkins on Tuesday, 05 January 2010 10:56:12
The static tunnel T24687 is not working properly.
The tunnel interface goes up and it sets up correctly but I cannot ping6 the other side of the tunnel.
The version of aiccu I use is the one available in OpenBSD 4.6 (20070115), on a similar machine the tunnel T24344 (ayiya) it's workin well.
Ask if you need more informations.
-------------------------------------------------------------------------------
sock_getline() : "200 SixXS TIC Service on noc.sixxs.net ready (http://www.sixxs.net)"
sock_printf() : "client TIC/draft-00 AICCU/2007.01.15-console-openbsd OpenBSD/4.6"
sock_getline() : "200 Client Identity accepted"
sock_printf() : "get unixtime"
sock_getline() : "200 1262684246"
sock_printf() : "username GBT3-SIXXS"
sock_getline() : "200 Choose your authentication challenge please"
sock_printf() : "challenge md5"
sock_getline() : "200 af3b77cc29530e1257fea9659e01dd85"
sock_printf() : "authenticate md5 6006cd96a6b1f153ecb47ccd8fc8a2cd"
sock_getline() : "200 Succesfully logged in using md5 as GBT3-SIXXS (Giovanni Bechis) from 2001:7b8:3:4f:202:b3ff:fe46:bec"
sock_printf() : "tunnel show T24687"
sock_getline() : "201 Showing tunnel information for T24687"
sock_getline() : "TunnelId: T24687"
sock_getline() : "Type: 6in4-static"
sock_getline() : "IPv6 Endpoint: 2001:1418:100:31f::2"
sock_getline() : "IPv6 POP: 2001:1418:100:31f::1"
sock_getline() : "IPv6 PrefixLength: 64"
sock_getline() : "Tunnel MTU: 1280"
sock_getline() : "Tunnel Name: www.snb.it"
sock_getline() : "POP Id: ittrn01"
sock_getline() : "IPv4 Endpoint: 62.149.229.129"
sock_getline() : "IPv4 POP: 213.254.12.34"
sock_getline() : "UserState: enabled"
sock_getline() : "AdminState: enabled"
sock_getline() : "202 Done"
Succesfully retrieved tunnel information for T24687
sock_printf() : "QUIT Under the weeping moon"
add net default: gateway 2001:1418:100:31f::1
Tunnel Information for T24687:
POP Id : ittrn01
IPv6 Local : 2001:1418:100:31f::2/64
IPv6 Remote : 2001:1418:100:31f::1/64
Tunnel Type : 6in4-static
Adminstate : enabled
Userstate : enabled
-------------------------------------------------------------------------------
add net default: gateway 2001:1418:100:31f::1
#######
####### AICCU Quick Connectivity Test
#######
####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (62.149.229.129)
### 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 62.149.229.129 (62.149.229.129): 56 data bytes
64 bytes from 62.149.229.129: icmp_seq=0 ttl=255 time=0.066 ms
64 bytes from 62.149.229.129: icmp_seq=1 ttl=255 time=0.035 ms
64 bytes from 62.149.229.129: icmp_seq=2 ttl=255 time=0.041 ms
--- 62.149.229.129 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.035/0.047/0.066/0.014 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 data bytes
64 bytes from 213.254.12.34: icmp_seq=0 ttl=55 time=16.087 ms
64 bytes from 213.254.12.34: icmp_seq=1 ttl=55 time=11.153 ms
64 bytes from 213.254.12.34: icmp_seq=2 ttl=55 time=11.231 ms
--- 213.254.12.34 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 11.153/12.823/16.087/2.311 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), 64 hops max, 40 byte packets
1 host2-224-149-62.serverdedicati.aruba.it (62.149.224.2) 0.562 ms 0.597 ms 1.6 ms
2 12416PT.aruba.it (62.149.190.4) 0.575 ms 0.382 ms 0.423 ms
3 12416P1.aruba.it (62.149.190.3) 0.721 ms 0.573 ms 0.571 ms
4 itgate.mix-it.net (217.29.66.65) 7.304 ms 7.205 ms 7.152 ms
5 if-0-1.tango.core.MIL2.itgate.net (212.110.33.3) 27.191 ms 11.223 ms 10.954 ms
6 if-0-3.scrappy-monster.core.TRN.itgate.net (213.254.31.245) 11.103 ms 10.934 ms 11.248 ms
7 if-0-0.charleston.CBQ.TRN.itgate.net (213.254.0.13) 10.813 ms 10.802 ms 10.808 ms
8 frejus.ITgate.net (213.254.12.34) 11.396 ms 11.256 ms 11.246 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
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%3 time=0.098 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=1 hlim=64 dst=::1%3 time=0.091 ms
16 bytes from ::1: Echo Request
16 bytes from ::1, icmp_seq=2 hlim=64 dst=::1%3 time=0.094 ms
--- ::1 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.091/0.094/0.098/0.003 ms
######
###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:1418:100:31f::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:1418:100:31f::2 --> 2001:1418:100:31f::2
16 bytes from 2001:1418:100:31f::2: Echo Request
16 bytes from 2001:1418:100:31f::2, icmp_seq=0 hlim=64 dst=2001:1418:100:31f::2%3 time=0.096 ms
16 bytes from 2001:1418:100:31f::2: Echo Request
16 bytes from 2001:1418:100:31f::2, icmp_seq=1 hlim=64 dst=2001:1418:100:31f::2%3 time=0.097 ms
16 bytes from 2001:1418:100:31f::2: Echo Request
16 bytes from 2001:1418:100:31f::2, icmp_seq=2 hlim=64 dst=2001:1418:100:31f::2%3 time=0.1 ms
--- 2001:1418:100:31f::2 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.096/0.098/0.100/0.002 ms
######
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:1418:100:31f::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
--- 2001:1418:100:31f::1 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
######
State change: user
The state of this ticket has been changed to user
Tunnel T24687 not working properly
Please read that big orange box which points to the contact page where there is big list of items that you might want to provide (interfaces,routes,firewall rules etc).
Note also that for a static tunnel you don't even need to use AICCU and OpenBSD provides a standard method of configuring static tunnels, again, see the FAQ.
Tunnel T24687 not working properly
Shadow Hawkins on Tuesday, 05 January 2010 12:17:57
I changed my config and i setup the tunnel without Aiccu.
Here there are some configs:
$ ifconfig bge0
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:08:02:f7:c0:55
priority: 0
groups: egress
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 62.149.229.129 netmask 0xffffe000 broadcast 62.149.255.255
$ ifconfig gif0
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
priority: 0
groups: gif egress
physical address inet 62.149.229.129 --> 213.254.12.34
inet6 fe80::208:2ff:fef7:c055%gif0 -> prefixlen 64 scopeid 0x5
inet6 2001:1418:100:31f::2 -> 2001:1418:100:31f::1 prefixlen 128
# route -n show
Routing tables
Internet:
Destination Gateway Flags Refs Use Mtu Prio Iface
default 62.149.224.1 UGS 37 1083 - 8 bge0
62.149.224/19 link#1 UC 1 0 - 4 bge0
62.149.224.1 00:00:0c:07:ac:01 UHLc 1 0 - 4 bge0
110.169.41.118 62.149.224.1 UGHD 0 4472 - L 56 bge0
127/8 127.0.0.1 UGRS 0 0 33200 8 lo0
127.0.0.1 127.0.0.1 UH 12 341 33200 4 lo0
202.133.54.180 62.149.224.1 UGHD 0 3431 - L 56 bge0
224/4 127.0.0.1 URS 0 0 33200 8 lo0
Internet6:
Destination Gateway Flags Refs Use Mtu Prio Iface
::/104 ::1 UGRS 0 4 - 8 lo0
::/96 ::1 UGRS 0 0 - 8 lo0
default ::1 UGS 0 36 - 8 gif0
::1 ::1 UH 15 11076 33200 4 lo0
::127.0.0.0/104 ::1 UGRS 0 0 - 8 lo0
::224.0.0.0/100 ::1 UGRS 0 0 - 8 lo0
::255.0.0.0/104 ::1 UGRS 0 0 - 8 lo0
::ffff:0.0.0.0/96 ::1 UGRS 0 3 - 8 lo0
2001:1418:100:31f::1 2001:1418:100:31f::2 UH 0 2 - 4 gif0
2001:1418:100:31f::2 link#5 UHL 0 0 - 4 lo0
2002::/24 ::1 UGRS 0 0 - 8 lo0
2002:7f00::/24 ::1 UGRS 0 0 - 8 lo0
2002:e000::/20 ::1 UGRS 0 0 - 8 lo0
2002:ff00::/24 ::1 UGRS 0 0 - 8 lo0
fe80::/10 ::1 UGRS 9 2 - 8 lo0
fe80::%lo0/64 fe80::1%lo0 U 0 0 - 4 lo0
fe80::1%lo0 link#3 UHL 0 0 - 4 lo0
fe80::%gif0/64 link#5 UC 0 0 - 4 gif0
fe80::208:2ff:fef7:c055%gif0 link#5 UHL 0 0 - 4 lo0
fec0::/10 ::1 UGRS 0 0 - 8 lo0
ff01::/16 ::1 UGRS 0 0 - 8 lo0
ff01::%bge0/32 link#1 UC 0 0 - 4 bge0
ff01::%lo0/32 ::1 UC 0 0 - 4 lo0
ff01::%gif0/32 link#5 UC 0 0 - 4 gif0
ff02::/16 ::1 UGRS 8 0 - 8 lo0
ff02::%lo0/32 ::1 UC 0 0 - 4 lo0
ff02::%gif0/32 link#5 UC 0 0 - 4 gif0
# cat /etc/hostname.gif0
tunnel 62.149.229.129 213.254.12.34
inet6 2001:1418:100:31f::2 128
dest 2001:1418:100:31f::1
!/sbin/route add -inet6 default ::1
!/sbin/route change -inet6 default -ifp gif0
My firewall log all blocked packets and I do not see any related log, while pinging the endpoint tcpdump show this:
# tcpdump -netttv -i gif0
tcpdump: listening on gif0, link-type NULL
Jan 05 12:15:35.219302 2001:1418:100:31f::2 > 2001:1418:100:31f::1: icmp6: echo request (len 16, hlim 64)
Jan 05 12:15:36.227945 2001:1418:100:31f::2 > 2001:1418:100:31f::1: icmp6: echo request (len 16, hlim 64)
Tunnel T24687 not working properly
# tcpdump -netttv -i gif0
That is the tunnel interface, please actually read the reporting problems list, it states what to look for. No proto-41 or ICMP packets for that are being returned from your host, looks like a misconfig or overzealous firewalling somewhere, nothing we can resolve.
Tunnel T24687 not working properly
Shadow Hawkins on Tuesday, 05 January 2010 13:39:19
I switched my tunnel to ayiya and now it works fine.
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 05 January 2010 11:54:06
Posting is only allowed when you are