Instance network routing issues.

[olandodeflexy]

Describe the bug
Network routing issues multipass version: multipass 1.15.0+mac multipassd 1.15.0+mac

To Reproduce
How, and what happened?

1. multipass shell instance1
shell failed: ssh connection failed: 'Failed to connect: No route to host'
   multipassd.log

The issue started after I updated to 1.15.0
I followed Network routing problems to remove and add the route again.
I removed multipass and reinstalled it.

I am aware of 2070 and [2973(https://github.com//issues/2973) but none of the suggestions helped to resolve my issue.
I can run multipass list/ls without any issues.

Logs
Please provide logs from the daemon, see accessing logs on where to find them on your platform.
multipassd.log

Additional info

• MackBook Pro M3: Sequoia 15.2

• multipass version: multipass 1.15.0+mac multipassd 1.15.0+mac

• multipass info:
  Name: new1
  State: Running
  Snapshots: 0
  IPv4: 192.168.64.2
  Release: Ubuntu 24.04.1 LTS
  Image hash: 6e1f90d3e81b (Ubuntu 24.04 LTS)
  CPU(s): 1
  Load: 0.00 0.00 0.00
  Disk usage: 2.2GiB out of 4.8GiB
  Memory usage: 235.5MiB out of 953.0MiB
  Mounts: --

• multipass get local.driver: qemu

Additional context
A ping to the instances IP returns
ping 192.168.64.2
PING 192.168.64.2 (192.168.64.2): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 0
ping: sendto: No route to host
Request timeout for icmp_seq 1
ping: sendto: No route to host
Request timeout for icmp_seq 2
ping: sendto: No route to host
Request timeout for icmp_seq 3
^C
--- 192.168.64.2 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

[ricab]

Hi @olandodeflexy, sorry you are experiencing this. It appears to be the same issue as #3766. Please reopen otherwise. Some people report rebooting helped.

[ricab]

Duplicate of #3766

[Chobicus]

I have the exact same setup as @olandodeflexy . Rebooting does not help. What does work is

sudo multipass shell  -vvvv

but it is not optimal.

[olandodeflexy]

Sadly I am still having this issue.

[ricab]

Could you please try this solution? It appears to be fixing it for others.

[lucj]

Thanks @ricab! I got the problem after upgrading to 1.15.0 this morning, and your suggestion fixed the thing :)