Re: [44net] Updated BGP design (was 44Net Digest, Vol 3, Issue 20)

Hi, I would appreciate any advice from this thread from someone that actually managed to introduce local BGP peering of a subnet and to set up whatever it takes not to disconnect this subnet from the rest of the 44 network. I am coordinating the Swedish delegation 44.140.0.0/16. Last year we made a complete restart of this network since it was totally dead after a very active pioneer period. I was unfortunately not part of that period and lack experience from the tunnelled version of the network. We now have an agreement both with ARDC and SUNET (the Swedish University Network) to provide Internet transit for this space locally via SUNET. SUNET is connected to Nordunet, which is connected to the European academic backbone GÉANT, which is connected all over the world. SUNET accepts announcements of subnets down to /24. This makes it possible for us to spread SUNET/se.amprnet gateways at SUNET points of presence all over the country. We are in the process of connecting amateur clubs to such gateways that will serve their individual members. We are also adding ipv6 support into this arrangement. Is it correctly understood from this thread that we should set up a fat tunnel in se.ampr between SUNET and 44.0.0.1? and route to 44.0.0.0/8 through it? There has been talk about both gre and ipip-tunnels. In cases where we still have to tunnel in 44.140/16 (hopefully temporarily) we are using gre-tunnels since they also support ipv6. But I guess we can use either for this particular tunnel. Anything else to think about to get it working? Bjorn/sa0bxi