You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
In certain types of deployment (e.g. CNI) weave will not be in charge of creating bridge devices and container network interfaces. An analysis of weave must be performed to identify specific problems and document them as issues for resolution.
awh
changed the title
Work with existing bridges and container network interfaces
Determine bridge and container network interface requirements
Sep 14, 2015
I think when this was filed the thinking was that we could piggy-back on the CNI 'bridge' plugin. Since then we have implemented our own Weave Net CNI plugin which does create and set up veths.
We tell people to use this after calling weave launch, which will create the bridge, so that part of the premise also bears re-considering.
In certain types of deployment (e.g. CNI) weave will not be in charge of creating bridge devices and container network interfaces. An analysis of weave must be performed to identify specific problems and document them as issues for resolution.
ethtool tx off
on guest interfaces #1255 - Don't rely on disabling TSOThe text was updated successfully, but these errors were encountered: