On Tue, 12 Jul 2016 07:22:14 +0300 Alex Levit <alexl.glo...@gmail.com> wrote:
> I have done it in the past using network namespaces (simulating VRF). > It worked well with OpenNHRP/Quagga This requires public IP per segregated network. But is probably the only way to do it at the moment. > On Tue, Jul 12, 2016 at 6:14 AM, <pbar...@netprotec.com> wrote: > > > I have been very satisfied with the OpenNHRP/Quagga implementation > > on Alpine Linux. Thank you so much for a very useful product. > > > > I was wondering if there was an option to segregate multiple > > customers all on the same HUB node? Customer ONE has 5 Spokes and > > Customer TWO has 6 Spokes. They can connect among themselves, but > > Customer ONE will never connect to Customer TWO? Like mentioned above network namespace (or containers which basically does the same thing). There has been work on the kernel and quagga for implementing VRFs, but it's still under development and not in usable state. It would also require new code in quagga/nhrp module for being VRF aware, and to support different IPsec profiles per dmvpn network. /Timo ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ opennhrp-devel mailing list opennhrp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opennhrp-devel
