Rich

Thanks for replying. Interesting that this might not be my problem after all.... As I am running on Kubernetes and the `weave-tc` daemonset already has privileged access with host networking...