SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #9358762
Ticket Status: User

PoP: nzwlg01 - Advanced Computer Solutions (ACSData) (Wellington)

New Tunnel has not come up - T122298
[nz] Shadow Hawkins on Saturday, 11 May 2013 04:53:42
Hi There, My new tunnel to nzwlg01 has not come up at all. Below is some diagnostics and configuration of my static tunnel. Thanks user@HOST> ping 2001:4428:200:12b::1 source 2001:4428:200:12b::2 PING6(56=40+8+8 bytes) 2001:4428:200:12b::2 --> 2001:4428:200:12b::1 ^C --- 2001:4428:200:12b::1 ping6 statistics --- 4 packets transmitted, 0 packets received, 100% packet loss frizianz@FRIZIANZ-WINDERMERE-FW01> ping 202.21.136.122 source 203.86.203.0 PING 202.21.136.122 (202.21.136.122): 56 data bytes 64 bytes from 202.21.136.122: icmp_seq=0 ttl=57 time=16.451 ms 64 bytes from 202.21.136.122: icmp_seq=1 ttl=57 time=14.979 ms 64 bytes from 202.21.136.122: icmp_seq=2 ttl=57 time=14.541 ms 64 bytes from 202.21.136.122: icmp_seq=3 ttl=57 time=14.292 ms ^C --- 202.21.136.122 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 14.292/15.066/16.451/0.837 ms user@HOST> traceroute 202.21.136.122 source 203.86.203.0 traceroute to 202.21.136.122 (202.21.136.122) from 203.86.203.0, 30 hops max, 40 byte packets 1 20.17.69.111.static.snap.net.nz (111.69.17.20) 11.582 ms 9.865 ms 9.726 ms 2 24.17.69.111.static.snap.net.nz (111.69.17.24) 64.320 ms 60.199 ms 9.224 ms 3 * * * 4 snap.wix.net.nz (202.7.1.240) 14.866 ms 14.472 ms 15.575 ms 5 acsdata.wix.net.nz (202.7.0.245) 15.151 ms 15.194 ms 15.179 ms 6 ge0-2-3050-901.v4wlg2.acsdata.co.nz (114.110.34.235) 15.811 ms 14.997 ms 14.948 ms 7 vlan104.deputy-dog.acsdata.co.nz (114.110.32.90) 15.688 ms 15.266 ms 14.664 ms 8 vlan104.deputy-dog.acsdata.co.nz (114.110.32.90) 15.227 ms !X 15.373 ms !X 15.197 ms !X user@HOST> show configuration interfaces ip-0/0/0 unit 2 | display set set interfaces ip-0/0/0 unit 2 description "Tunnel to ACSData - SixXS" set interfaces ip-0/0/0 unit 2 tunnel source 203.86.203.0 set interfaces ip-0/0/0 unit 2 tunnel destination 202.21.136.122 set interfaces ip-0/0/0 unit 2 family inet6 mtu 1280 set interfaces ip-0/0/0 unit 2 family inet6 address 2001:4428:200:12b::2/64 user@HOST>
New Tunnel has not come up - T122298
[ch] Jeroen Massar SixXS Staff on Saturday, 11 May 2013 06:16:28
As you can see in the Live Tunnel Status, the PoP has it configured, as such the PoP side is ready.
user@HOST> ping 2001:4428:200:12b::1 source 2001:4428:200:12b::2
user@HOST> traceroute 202.21.136.122 source 203.86.203.0
Why do you have to select the source?
8 vlan104.deputy-dog.acsdata.co.nz (114.110.32.90) 15.227 ms !X 15.373 ms !X 15.197 ms !X
That is interesting though, would almost mean that the final destination cannot be reached, which is odd, though could just be a firewall (I'll ask ACSData about that). From our side we also see a similar thing:
12 ADC-0003.asianetcom.net (202.147.41.206) 277.237 ms 274.790 ms 275.572 ms 13 ge0-0-801.v4wlg2.acsdata.co.nz (114.110.34.203) 287.769 ms 285.651 ms 285.366 ms 14 vlan104.deputy-dog.acsdata.co.nz (114.110.32.90) 284.607 ms 283.692 ms 284.939 ms 15 vlan104.deputy-dog.acsdata.co.nz (114.110.32.90) 284.662 ms !X 284.278 ms !X 283.513 ms !X
But IPv4 TCP/UDP is fully functional and a lot of other tunnels are marked as up, thus while odd I don't think this is a huge problem or the one causing your tunnel not to work. Outbound traceroute toward you:
traceroute to 203.86.203.0 (203.86.203.0), 30 hops max, 60 byte packets 1 deputy-dog.wlg.acsdata.co.nz (202.21.136.65) 0.189 ms 0.154 ms 0.133 ms 2 ge0-0-104.v4wlg2.acsdata.co.nz (114.110.32.89) 0.540 ms 0.587 ms 0.574 ms 3 ge0-0-801.v4wlg0.acsdata.co.nz (114.110.34.201) 0.925 ms 0.915 ms 0.898 ms 4 snap.wix.net.nz (202.7.1.240) 12.086 ms 12.079 ms 12.063 ms 5 * * * 6 24.17.69.111.static.snap.net.nz (111.69.17.24) 5.940 ms 5.938 ms 5.918 ms 7 25.17.69.111.static.snap.net.nz (111.69.17.25) 24.774 ms 24.465 ms 24.058 ms 8 * * * 9 * * *
Could it be that your endpoint is firewalled or routing packets back in the wrong way or so? Don't forget to check protocol 41...
user@HOST> show configuration interfaces ip-0/0/0 unit 2 | display set
While configuration is one thing, can you show the actual interface details and routing tables instead?
New Tunnel has not come up - T122298
[nz] Shadow Hawkins on Sunday, 12 May 2013 02:34:21
Here is the routing table as requested: user@HOST> show route table inet6 inet6.0: 10 destinations, 12 routes (10 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both ::/0 *[Static/5] 21:43:17 > to 2001:4428:200:12b::1 via ip-0/0/0.2 2001:4428:200:12b::/64 *[Direct/0] 21:43:17 > via ip-0/0/0.2 2001:4428:200:12b::2/128 *[Local/0] 21:43:17 Local via ip-0/0/0.2 2001:4428:200:812b::/64 *[Direct/0] 4d 06:38:06 > via vlan.100 2001:4428:200:812b::1/128 *[Local/0] 4d 06:38:23 Local via vlan.100 fe80::/64 *[Direct/0] 4d 06:38:06 > via vlan.100 [Direct/0] 4d 06:35:09 > via at-1/0/0.0 [Direct/0] 21:43:17 > via ip-0/0/0.2 fe80::42b4:f000:51:4740/128 *[Local/0] 4d 06:38:14 Local via ip-0/0/0.2 fe80::42b4:f00f:fc51:4740/128 *[Direct/0] 4d 06:38:44 > via lo0.0 fe80::42b4:f010:51:4740/128 *[Local/0] 4d 06:37:50 Local via at-1/0/0.0 fe80::42b4:f0ff:fe51:4748/128 *[Local/0] 4d 06:38:23 Local via vlan.100 user@HOST> Simply i need to specify the source as it is a security device so it needs a source so it can apply policies to it. Also for the fact that regardless of routing tables you should always be able to ping directly connected networks :) Here is the show interface of the tunnel. As you will see i'm not recieving any input packets. user@HOST> show interfaces ip-0/0/0.2 extensive Logical interface ip-0/0/0.2 (Index 93) (SNMP ifIndex 553) (Generation 164) Description: Tunnel to ACSData - SixXS Flags: Point-To-Point SNMP-Traps 0x0 IP-Header 202.21.136.122:203.86.203.0:4:df:64:00000000 Encapsulation: IPIP-NULL Traffic statistics: Input bytes : 0 Output bytes : 5992 Input packets: 0 Output packets: 78 Local statistics: Input bytes : 0 Output bytes : 5992 Input packets: 0 Output packets: 78 Transit statistics: Input bytes : 0 0 bps Output bytes : 0 0 bps Input packets: 0 0 pps Output packets: 0 0 pps Security: Zone: InternetCombined Allowed host-inbound traffic : ike ping snmp ssh traceroute Flow Statistics : Flow Input statistics : Self packets : 0 ICMP packets : 0 VPN packets : 0 Multicast packets : 0 Bytes permitted by policy : 0 Connections established : 0 Flow Output statistics: Multicast packets : 0 Bytes permitted by policy : 4144 Flow error statistics (Packets dropped due to): Address spoofing: 0 Authentication failed: 0 Incoming NAT errors: 0 Invalid zone received packet: 0 Multiple user authentications: 0 Multiple incoming NAT: 0 No parent for a gate: 0 No one interested in self packets: 0 No minor session: 0 No more sessions: 0 No NAT gate: 0 No route present: 0 No SA for incoming SPI: 0 No tunnel found: 0 No session for a gate: 0 No zone or NULL zone binding 0 Policy denied: 0 Security association not active: 0 TCP sequence number out of window: 0 Syn-attack protection: 0 User authentication errors: 0 Protocol inet6, MTU: 1280, Generation: 181, Route table: 0 Flags: User-MTU Addresses, Flags: Is-Preferred Is-Primary Destination: 2001:4428:200:12b::/64, Local: 2001:4428:200:12b::2 Generation: 199 Addresses, Flags: Is-Preferred Destination: fe80::/64, Local: fe80::42b4:f000:51:4740 Generation: 200 user@HOST>
New Tunnel has not come up - T122298
[ch] Jeroen Massar SixXS Staff on Sunday, 12 May 2013 08:25:55
Simply i need to specify the source as it is a security device so it needs a source so it can apply policies to it. Also for the fact that regardless of routing tables you should always be able to ping directly connected networks :)
A device that routes is a device that routes, it will be able to select the proper source IP. As you mention 'security device' though, please see my note about checking your firewall...

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker