On Mon, Jun 23, 2014 at 03:58:28PM -0700, Ben Pfaff wrote:
> On Mon, Jun 23, 2014 at 3:55 PM, Simon Horman wrote:
> > On Mon, Jun 23, 2014 at 02:50:20PM -0700, Ben Pfaff wrote:
> >> On Mon, Jun 16, 2014 at 10:09:38AM +0900, Simon Horman wrote:
> >> > In some cases an pop MPLS action changes a pack
On Mon, Jun 23, 2014 at 3:55 PM, Simon Horman wrote:
> On Mon, Jun 23, 2014 at 02:50:20PM -0700, Ben Pfaff wrote:
>> On Mon, Jun 16, 2014 at 10:09:38AM +0900, Simon Horman wrote:
>> > In some cases an pop MPLS action changes a packet to be a non-mpls packet.
>> > In this case subsequent any L3+ ac
On Mon, Jun 23, 2014 at 02:50:20PM -0700, Ben Pfaff wrote:
> On Mon, Jun 16, 2014 at 10:09:38AM +0900, Simon Horman wrote:
> > In some cases an pop MPLS action changes a packet to be a non-mpls packet.
> > In this case subsequent any L3+ actions require access to portions
> > of the packet which we
On Mon, Jun 16, 2014 at 10:09:38AM +0900, Simon Horman wrote:
> In some cases an pop MPLS action changes a packet to be a non-mpls packet.
> In this case subsequent any L3+ actions require access to portions
> of the packet which were not decoded as they were opaque when the
> packet was MPLS. Allo
In some cases an pop MPLS action changes a packet to be a non-mpls packet.
In this case subsequent any L3+ actions require access to portions
of the packet which were not decoded as they were opaque when the
packet was MPLS. Allow such actions to be translated by
first recirculating the packet.
Co
