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
VM contains several default routes #2280
Comments
Off topic
user-v2:
This is a test between the virtual machine and the host using iperf3 |
@AkihiroSuda |
SGTM, but the plan may change depending on the performance and stability |
Atleast with vzNAT i noticed that few cases of guest -> host network calls failing. This i noticed during very initial development of vz driver. Maybe we can test and provide a option to override as per need basis |
Same thing for me. In my case problem related to VPN. By default nat is disabled between the vpn and bridge interface. I applied nat rules using
This is unexpected behavior for me. VzNat in this case seems unnecessary. Only for connect the VM at a own address? |
Description
I'm testing vzNat and noticed strange behavior. After startup, the VM contains several default routes. So network connections are balancing between slirp and vnNat.
Lima Version:
v0.21.0
Template:
experimental/vz
.Steps:
limactl start --name test --debug template://experimental/vz
limactl shell test ip r
. Output:Actual output:
Expected output (without first route):
This comes from cloud-init, but I haven't found an option to disable this in network-config
The text was updated successfully, but these errors were encountered: