Hi everyone ... I just wanted to thank you all for the really great advice. I was able to successfully perform NAT64/NAPT mappings to multiple customers in different namespaces, even with conflicting IPv4 address spaces, using the "recipe" outlined below.
For our purposes I dressed it up with a configuration file that accepts a list of customer names along with the name of the interface each customer appears on and their IPv4 configuration. If there is any interest, let me know and I will post the script to the list. Once again, many thanks. -- Art From: Stefan Brudny <[email protected]> Sent: Wednesday, December 16, 2020 10:34 To: Art Cancro <[email protected]> Cc: Alberto Leiva <[email protected]>; [email protected] <[email protected]> Subject: Re: [Jool-list] JOOL in a multitenant service provider environment [EXTERNAL] [...] If you still neet to nat64, then recipe is to Create namespace and link them to monitoring tool using ipv6. Link and route the customers networks into name spaces (gre, vlans, vpns) Setup nat64 in name spaces. Optional: expose services to customer networks using some ha ky technique, i used dnat but this could be proxy, another tunnel etc. _______________________________________________ Jool-list mailing list [email protected] https://mail-lists.nic.mx/listas/listinfo/jool-list
