On 2/2/17 8:21 PM, Eric W. Biederman wrote:
>
> My brain is mostly elswhere right now so I don't have an implementation
> on how it should be implemented. However Linux fundamentally gets used
> interesting ways, and if we don't implement the option as per mpls exit
> now someone will come along
Robert Shearman writes:
> On 31/01/17 00:17, Eric W. Biederman wrote:
>> Robert Shearman writes:
>>
>>> It is sometimes desirable to present an MPLS transport network as a
>>> single hop to traffic transiting it because it prevents confusion when
>>> diagnosing failures. An example of where conf
On 31/01/17 01:09, David Ahern wrote:
On 1/30/17 1:36 PM, Robert Shearman wrote:
@@ -243,24 +245,29 @@ static bool mpls_egress(struct mpls_route *rt, struct
sk_buff *skb,
payload_type = ip_hdr(skb)->version;
switch (payload_type) {
- case MPT_IPV4: {
-
On 31/01/17 00:41, David Ahern wrote:
On 1/30/17 1:36 PM, Robert Shearman wrote:
It is sometimes desirable to present an MPLS transport network as a
single hop to traffic transiting it because it prevents confusion when
diagnosing failures. An example of where confusion can be generated is
when
On 31/01/17 00:17, Eric W. Biederman wrote:
Robert Shearman writes:
It is sometimes desirable to present an MPLS transport network as a
single hop to traffic transiting it because it prevents confusion when
diagnosing failures. An example of where confusion can be generated is
when addresses u
On 1/30/17 1:36 PM, Robert Shearman wrote:
> @@ -243,24 +245,29 @@ static bool mpls_egress(struct mpls_route *rt, struct
> sk_buff *skb,
> payload_type = ip_hdr(skb)->version;
>
> switch (payload_type) {
> - case MPT_IPV4: {
> - struct iphdr *hdr4 = ip_hdr(skb
On 1/30/17 1:36 PM, Robert Shearman wrote:
> It is sometimes desirable to present an MPLS transport network as a
> single hop to traffic transiting it because it prevents confusion when
> diagnosing failures. An example of where confusion can be generated is
> when addresses used in the provider ne
Robert Shearman writes:
> It is sometimes desirable to present an MPLS transport network as a
> single hop to traffic transiting it because it prevents confusion when
> diagnosing failures. An example of where confusion can be generated is
> when addresses used in the provider network overlap wit
It is sometimes desirable to present an MPLS transport network as a
single hop to traffic transiting it because it prevents confusion when
diagnosing failures. An example of where confusion can be generated is
when addresses used in the provider network overlap with addresses in
the overlay network
