Unable to ping VM from host with vzNAT network #3094
Unanswered
jrajahalme
asked this question in
Q&A
Replies: 2 comments
-
eth0 (192.168.5.15) is not pingable, but lima0 should be pingable $ lima ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 52:55:55:9b:04:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.5.15/24 metric 200 brd 192.168.5.255 scope global dynamic eth0
valid_lft 3580sec preferred_lft 3580sec
inet6 fe80::5055:55ff:fe9b:450/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
3: lima0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 52:55:55:99:a0:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.64.5/24 metric 100 brd 192.168.64.255 scope global dynamic lima0
valid_lft 3580sec preferred_lft 3580sec
inet6 fd21:a20d:ee48:a4d5:5055:55ff:fe99:a0bf/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 2591999sec preferred_lft 604799sec
inet6 fe80::5055:55ff:fe99:a0bf/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
$ ping 192.168.64.5
PING 192.168.64.5 (192.168.64.5): 56 data bytes
64 bytes from 192.168.64.5: icmp_seq=0 ttl=64 time=0.579 ms
^C
--- 192.168.64.5 ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.579/0.579/0.579/0.000 ms |
Beta Was this translation helpful? Give feedback.
0 replies
-
No IPv4 address on
Any hints on why this may be the case? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
limactl version 1.0.3
macOS 14.7.2 / Macbook Pro M3
According to the docs (https://lima-vm.io/docs/config/network/) vzNAT network should be able to "Connect to the VM IP from Host". I have a Ubuntu 22.04 VM running with the vz driver and vzNAT network.
In the VM, the only IP address that looks like it could be routable (locally) is on
eth0
(no IPv4 address onlima0
):On the host:
So there is no network device on 192.168.5 in the host.
Beta Was this translation helpful? Give feedback.
All reactions