-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
antrea CNI not setting default gateway correctly #46
Comments
working cluster from another env on vsphere, we can see that Get-NetRoute has a
the ipconfig output
the network adapter 13... is the one that is correct
|
xref antrea-io/antrea#2344 antrea
calico
|
@wenyingd can you suggest us a fix here ? Would like to keep using antrea as the default CNI if possible. But Virtualbox wants to make 2 NICs and my initial experiments to use public_network seem to fail. |
@Keith-Mange, @daschott, @sbangari, the above topic was brought up by @jayunit100 during the SIG Windows meeting today. Can I let you look into it, please? |
as one workaround, ive attempted to use |
Reproducing the issue:
|
You can follow these steps to test antrea patch: antrea-io/antrea#2344
BTW, I always compile antrea-agent.exe on Windows host successfully, didn't try it on other kinds of OSs. |
ok thanks @wenyingd , will test it out - do you have a binary we can use ? |
potentially fixed by #90 ... will try to close this once its automated with the right NIC input |
Having this issue when provisioning Antrea steps on master
Rerunning solved the issue, still investigating if related with last 1.3 release change |
Testing the new version on: |
Hi, the error occurs if you install the upstream OVS driver on Windows host for the first time. It is because the upstream OVS driver is not signed, and Windows doesn't trust the publisher. To resolve it, you need to enable testsigning mode on the Windows host in advance, and it should be safe to use a console for the installation at the first time, because Windows might give a popup window to ask if the user trusts the vendor or not. The user should confirm the installation. |
@wenyingd thanks. will try these steps |
Bcdedit.exe -set TESTSIGNING ON
Restart-Computer -Force |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Antrea CNI works be using the
node-ip
address to find a device, and then tries to use that specific Device to pick agateway
. That default gateway is theuplink
for OVS.However, it looks like it wants that device to have a
destinationPrefix
of 0.0.0.0/0 , as a way to find the default gateway by then extracting the NextHop value.So the question is... can we hardcode that NextHop value in cases like, this repos, where the node ip doesnt come up w/ a device that is directly connected to a default gateway?
update this is fixed now:) antrea-io/antrea@da17b5d
The text was updated successfully, but these errors were encountered: