Re: Implementing VRFs in linux kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 13, 2010 at 5:47 PM, Sambath Kumar Balasubramanian
<sambath_kumar_b@xxxxxxxxx> wrote:
> Thanks for your input. I did start looking into network namespaces. The
> documentation I
>
> could find for it is very limited and based on the limited documentation, it
> seems from a
>
> user space perspective, the set of processes have to be bound to a namespace
> which
>
> does notseems to be a scalable solution. Also it is not clear to me how a socket
> can bind
> to a namespace. I have not had a chance to dig deeper into the kernel code to do
> more
>
> investigation, but I am planning to do it. But at the first look, namespace
> seems to be not
>
> well suited for applications like VRFs and it seems to be more of a system
> virtualization
> solution.
>
>
>
>
> ----- Original Message ----
> From: Peter Chacko <peterchacko35@xxxxxxxxx>
> To: Stephen Hemminger <shemminger@xxxxxxxxxx>
> Cc: Sambath Kumar Balasubramanian <sambath_kumar_b@xxxxxxxxx>;
> linux-net@xxxxxxxxxxxxxxx
> Sent: Sun, September 12, 2010 7:33:53 AM
> Subject: Re: Implementing VRFs in linux kernel
>
> Network-name spaces are good for VRF ? Another question is is there
> any active, Linux  MPLS VPN project ?
>
> would appreciate your thoughts.
>
> On Sun, Sep 12, 2010 at 9:57 AM, Stephen Hemminger
> <shemminger@xxxxxxxxxx> wrote:
>> On Sat, 11 Sep 2010 20:03:29 -0700 (PDT)
>> Sambath Kumar Balasubramanian <sambath_kumar_b@xxxxxxxxx> wrote:
>>
>>> Hi,
>>>
>>>   Is there an implementation for VRFs (virtual routing and forwarding) in the
>>> linux
>>>
>>> kernel. Currently the linux kernel supports multiple routing table  but this
>>> needs
>>>
>>> to be enhanced with abilities for applications to bind a socket to a routing
>>> table,
>>>
>>> support for multiple neighbor tables and inherent support for duplicate IP
>>> addresses
>>>
>>> across different VRFs.
>>>
>>> Is there any linux project that will provide the above mentioned support? If
>>> there
>>> were to be work done in this area, will it acceptable in the mainline kernel?
>>>
>>> Thanks,
>>> Sambath
>>
>> Have you considered network namespaces?
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-net" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Take a look at "man unshare" and "man clone"'s CLONE_NEWNET how a
socket binds to a namespace.


thanks,
yao
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux