[RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-01 Thread Robert Shearman
In order to be able to function as a Label Edge Router in an MPLS network, it is necessary to be able to take IP packets and impose an MPLS encap and forward them out. The traditional approach of setting up an interface for each "tunnel" endpoint doesn't scale for the common MPLS use-cases where ea

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-01 Thread Thomas Graf
On 06/01/15 at 05:46pm, Robert Shearman wrote: > In order to be able to function as a Label Edge Router in an MPLS > network, it is necessary to be able to take IP packets and impose an > MPLS encap and forward them out. The traditional approach of setting > up an interface for each "tunnel" endpoi

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Robert Shearman
On 02/06/15 01:06, Thomas Graf wrote: On 06/01/15 at 05:46pm, Robert Shearman wrote: In order to be able to function as a Label Edge Router in an MPLS network, it is necessary to be able to take IP packets and impose an MPLS encap and forward them out. The traditional approach of setting up an i

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread roopa
On 6/1/15, 9:46 AM, Robert Shearman wrote: In order to be able to function as a Label Edge Router in an MPLS network, it is necessary to be able to take IP packets and impose an MPLS encap and forward them out. The traditional approach of setting up an interface for each "tunnel" endpoint doesn't

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Eric W. Biederman
Robert Shearman writes: > In order to be able to function as a Label Edge Router in an MPLS > network, it is necessary to be able to take IP packets and impose an > MPLS encap and forward them out. The traditional approach of setting > up an interface for each "tunnel" endpoint doesn't scale for

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Eric W. Biederman
roopa writes: > On 6/1/15, 9:46 AM, Robert Shearman wrote: >> In order to be able to function as a Label Edge Router in an MPLS >> network, it is necessary to be able to take IP packets and impose an >> MPLS encap and forward them out. The traditional approach of setting >> up an interface for ea

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread roopa
On 6/2/15, 11:30 AM, Eric W. Biederman wrote: roopa writes: On 6/1/15, 9:46 AM, Robert Shearman wrote: In order to be able to function as a Label Edge Router in an MPLS network, it is necessary to be able to take IP packets and impose an MPLS encap and forward them out. The traditional approa

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Robert Shearman
On 02/06/15 19:11, Eric W. Biederman wrote: Robert Shearman writes: In order to be able to function as a Label Edge Router in an MPLS network, it is necessary to be able to take IP packets and impose an MPLS encap and forward them out. The traditional approach of setting up an interface for ea

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Eric W. Biederman
Robert Shearman writes: > On 02/06/15 19:11, Eric W. Biederman wrote: >> Robert Shearman writes: >> >>> In order to be able to function as a Label Edge Router in an MPLS >>> network, it is necessary to be able to take IP packets and impose an >>> MPLS encap and forward them out. The traditional

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Thomas Graf
On 06/02/15 at 02:28pm, Robert Shearman wrote: > Nesting attributes inside the RTA_ENCAP blob should be supported by the > patch series today. Something like this: Sure. I'm not seeing such a construct for the MPLS case yet. I'm happy to rebase my patches on top of your nexthop implementation. It

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Robert Shearman
On 02/06/15 22:10, Eric W. Biederman wrote: Robert Shearman writes: On 02/06/15 19:11, Eric W. Biederman wrote: Robert Shearman writes: In order to be able to function as a Label Edge Router in an MPLS network, it is necessary to be able to take IP packets and impose an MPLS encap and forw

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-02 Thread Eric W. Biederman
Robert Shearman writes: > On 02/06/15 22:10, Eric W. Biederman wrote: >> Robert Shearman writes: >> >>> On 02/06/15 19:11, Eric W. Biederman wrote: Robert Shearman writes: > In order to be able to function as a Label Edge Router in an MPLS > network, it is necessary to be able

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-03 Thread Robert Shearman
On 02/06/15 22:43, Thomas Graf wrote: On 06/02/15 at 02:28pm, Robert Shearman wrote: Nesting attributes inside the RTA_ENCAP blob should be supported by the patch series today. Something like this: Sure. I'm not seeing such a construct for the MPLS case yet. Right, that is something that sho

Re: [RFC net-next 0/3] IP imposition of per-nh MPLS encap

2015-06-04 Thread Nicolas Dichtel
Le 03/06/2015 00:58, Eric W. Biederman a écrit : [snip] On the drawing board is getting cross namespace routes so with a little luck I will only need loopback devices in most of my network namespaces when the dust settles. +1 I've start to look at this, but I didn't have enough time right now.