Hi Jafar, The limitation is not caused by "VRF", it is caused by lacking of right design/implementation.
Now with our additional implementation, you can configured as many as same IP in the Same namespace. (As I said earlier, VRF is designed to have same IP addresses cross VRF table within ONE Name space, that has been this way ever since VRF as a concept being introduced) For example: Interface Et0.10 ip vrf red ip address 1.1.1.1/24 ospf enable interface Eth0.11 ip vrf blue ip address 1.1.1.1/24 isis enable Interface Eth1.100 Ip vrf white Ip address 1.1.1.1/24 Also you can see, within one namespace, you can now use Single OSPF/ISIS instance to support dynamic routing with VRF aware Using same ip address within same namespace OSPF/ISIS will create a routing table and build adjacency using The VRF domain configured on the logical interface. This way, the VRF work with namespace seamlessly to meet two separate Requirements: 1) namespace to create virtual router/switch Within each namespace, you can enable BGP/OSPF/ISIS 2) using VRF to build multi-table for each namespace. Just ONE OSPF/ISIS/BGP instance can support MPLS/L3VPN, or IGP/VRF. Thanks, Andrew ============== again, please ignore my attached disclaimer, it is not intentional ==================== -----Original Message----- From: Jafar Al-Gharaibeh [mailto:[email protected]] Sent: Thursday, May 21, 2015 7:17 AM To: Andrew Qu Cc: [email protected] Subject: Re: [quagga-dev 12365] Re: VRF and Multiple-Instance OSPF On 5/20/2015 11:34 PM, Andrew Qu wrote: > Overall, VRF was initially designed to support duplicate IP address > in each VRF table, do You have a case to support the statement about VRF > limitation there? I think the most obvious limitation is that "in general" you can't use the same IP address on multiple interfaces within the same network namespace. --Jafar ************* Email Confidentiality Notice ******************** The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you! _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
