Why would you add the complexity of BGP over GRE? I guess you could if you wanted to but the 2 protocols have extremely different uses. Use BGP to connect with one or more network service providers where you then bring your own address space. Use GRE to build tunnels into those networks. once BGP peered to the internet cloud, let the cloud do the routing and delivery between networks for you. Obviously if you have a direct point to point route between these networks (over radio) that may be preferable, but then again if you have such a link then maybe it's a good idea for those networks to peer based upon a common agreed upon roting policy.
Eric AF6EP
On Thu, Apr 24, 2014 at 4:24 PM, Don Fanning don@00100100.net wrote:
(Please trim inclusions from previous messages) _______________________________________________ I'm of the opinion that it should be kept the simplest possible and let people deal with their own networks. Give the people the basics needed to create a connection and get the routes. Then if they want to block people, they can add a static route dropping them or a firewall rule.
I feel BGP over GRE or DMVPN is overkill as beyond the extra functionality of GRE being able to do multicast and other kinds of traffic, there is no added value to what we already have with IPIP and RIP44d/encap. Within 44net, it's a different story - go RIP/OSPF and IPSec for all I care. But setting up tunnels should be kept simplistic.