Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  


Welcome to Hurricane Electric's forums!

Author Topic: Configuring BGP for IPv6 tunnel on a SonicWall NSA 3600 - Route not advertised?  (Read 3893 times)


  • Newbie
  • *
  • Posts: 1

I am trying to configure an IPv6 tunnel to tunnelbroker using BGP, since I have an assigned IPv6 address space. I have BGP configured on the SonicWall NSA 3600 using the command-line interface (CLI) and have created the following configuration (this is largely based on the SonicWall knowledgebase instructions here: plus information from their CLI manual regarding IPv6 and BGP here:

Code: [Select]
router bgp 54729
 neighbor 2001:470:1f0c:1f::1 remote-as 6939

 address-family ipv6
 network 2620:fc:8000::/48
 redistribute connected
 neighbor 2001:470:1f0c:1f::1 activate

BGP seems to be running correctly, and my router is communicating with the HE router via the IPv6 tunnel. However, HE tech support tells me that no advertised routes were received from my router:

Code: [Select]
No routes are received from  Neighbor 2001:470:1f0c:1f::2
ipv6 prefix-list as54729-tunnel-filter: 1 entries
     seq 3932 permit 2620:fc:8000::/48

I have searched via the SonicWall knowledge-base, these forums, and Google, but was unable to find any reference to what is amiss in my configuration. There is tons of more complicated examples using multi-homed configurations, but mine is single-homed, single-ISP (tunnel), but for a simple configuration like mine, the above config should be theoretically sufficient.

So, as far as I can tell, the configuration statement
Code: [Select]
network 2620:fc:8000::/48 in my configuration should advertise the network to the neighbor.

Anybody have any idea what is missing? I'm sorry, but while I'm quite knowledgable about IPv6, I'm not as familiar with BGP....



  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1745

As I mentioned in your trouble ticket, don't forget to install a pull-up route for your /48 either with a null route of the range, or configuring an IP out of it in an interface or loopback device.