• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

my BGP tunnel is dead for some reason

Started by drookie, June 02, 2014, 01:39:49 AM

Previous topic - Next topic

drookie

Hi.

I'm using a number of tunnels to HE, now I need to fix my BGPv6 connectivity and I've set up a BGP tunnel. But for some reason it's dead - the peer doesn't answer neither to icmp6 neighbor solicitation messages:

Here's tcpdump capture on an outer interface:

14:38:34.975299 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2.10900 > 2001:470:11:3::1.179: tcp 0
14:38:37.975208 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2.10900 > 2001:470:11:3::1.179: tcp 0
14:38:39.975213 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2 > 2001:470:11:3::1: ICMP6, neighbor solicitation, who has 2001:470:11:3::1, length 24
14:38:40.975209 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2 > 2001:470:11:3::1: ICMP6, neighbor solicitation, who has 2001:470:11:3::1, length 24
14:38:41.175201 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2.10900 > 2001:470:11:3::1.179: tcp 0
14:38:41.975200 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2 > 2001:470:11:3::1: ICMP6, neighbor solicitation, who has 2001:470:11:3::1, length 24
14:38:44.375208 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2.10900 > 2001:470:11:3::1.179: tcp 0
14:38:47.575200 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2.10900 > 2001:470:11:3::1.179: tcp 0
14:38:49.375261 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2 > 2001:470:11:3::1: ICMP6, neighbor solicitation, who has 2001:470:11:3::1, length 24
14:38:50.375260 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2 > 2001:470:11:3::1: ICMP6, neighbor solicitation, who has 2001:470:11:3::1, length 24
14:38:50.775197 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2.10900 > 2001:470:11:3::1.179: tcp 0
14:38:51.375202 IP 89.250.210.69 > 216.66.84.50: IP6 2001:470:11:3::2 > 2001:470:11:3::1: ICMP6, neighbor solicitation, who has 2001:470:11:3::1, length 24

broquea

You are supposed to be emailing ipv6@he.net to bring this to their attention. Now go open a trouble ticket.