On 27/07/2016 14:18, "Ben Pfaff" wrote:
>On Wed, Jul 27, 2016 at 01:51:00PM -0700, Jesse Gross wrote:
>> On Wed, Jul 27, 2016 at 1:40 PM, Daniele Di Proietto
>> wrote:
>> > On 27/07/2016 13:12, "Joe Stringer" wrote:
>> >
>> >>On 26 July 2016 at 17:58, Daniele Di Proietto
>> >>wrote:
>> >
On Wed, Jul 27, 2016 at 01:51:00PM -0700, Jesse Gross wrote:
> On Wed, Jul 27, 2016 at 1:40 PM, Daniele Di Proietto
> wrote:
> > On 27/07/2016 13:12, "Joe Stringer" wrote:
> >
> >>On 26 July 2016 at 17:58, Daniele Di Proietto
> >>wrote:
> >>> The userspace connection tracker doesn't support ALG
On Wed, Jul 27, 2016 at 1:40 PM, Daniele Di Proietto
wrote:
> On 27/07/2016 13:12, "Joe Stringer" wrote:
>
>>On 26 July 2016 at 17:58, Daniele Di Proietto wrote:
>>> The userspace connection tracker doesn't support ALGs, frag reassembly
>>> or NAT yet, so skip those tests.
>>>
>>> Also, connecti
On 27/07/2016 13:12, "Joe Stringer" wrote:
>On 26 July 2016 at 17:58, Daniele Di Proietto wrote:
>> The userspace connection tracker doesn't support ALGs, frag reassembly
>> or NAT yet, so skip those tests.
>>
>> Also, connection tracking state input from a local port is not possible
>> in
On 26 July 2016 at 17:58, Daniele Di Proietto wrote:
> The userspace connection tracker doesn't support ALGs, frag reassembly
> or NAT yet, so skip those tests.
>
> Also, connection tracking state input from a local port is not possible
> in userspace.
>
> The userspace datapath pads all frames wi
The userspace connection tracker doesn't support ALGs, frag reassembly
or NAT yet, so skip those tests.
Also, connection tracking state input from a local port is not possible
in userspace.
The userspace datapath pads all frames with 0, to make them at
least 64 bytes.
Finally, the userspace data
