Hi Thomas,

The issue was related to an outdated slirp4netns which did not recognize the option '--netns-type'.

A quick update solved the issue.

Thanks

On Mon, Apr 6, 2020 at 11:35 AM Thomas Monjalon <thomas@monjalon.net> wrote:

06/04/2020 17:27, Brandon Lo:
> We have looked into this issue and resolved it.

What is the resolution?

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824