Hi Len
>VRF needs more than just namespaces, but certainly different vrf instances can >have the same IP addresses >in which does not get along well with just using multiple routing tables in my >experience. Namespaces do allow the >use of the same IP addresses in different instances, which can be used with >other stuff to give VRF support. >Now if you are willing to not allow reuse of IP addresses in different VRFs, >then OK you can do it without namespaces. >I don't think that is an acceptable limitation though. Why you said VRF needs more than namespace? To me namespace is not needed at all if I just want to support VRF. Namespace is only needed when I want to support logical router/switch. The code we are done and the design spec I send out does not require namespace at all. We Just co-exist with namespace in linux. 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? Thanks, Andrew ==== sorry folks, before I got our IT to fix this issue, my mail will automatically ==== ==== attached the legal disclaimer, please ignore it for now ======= ************* 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
