canonical / canonical/multipass
Useless IPs reported on instances
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9.2k
- Forks
- 829
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 45
Description
#1951 is back.
In multipass list and multipass info we list all the IPs we find on instances. The problem is they may not be reachable outside of the instance (e.g. bridges for containers, guest networks). It's confusing today that you see an IP that you can not reach.
PS C:\Users\natha> multipass list
Name State IPv4 Image
docker-vm Running 172.17.0.1 Ubuntu 20.04 LTS
PS C:\Users\natha> ssh -v 172.17.0.1
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Connecting to 172.17.0.1 [172.17.0.1] port 22.
debug1: connect to address 172.17.0.1 port 22: Connection timed out
ssh: connect to host 172.17.0.1 port 22: Connection timed out
I see two options out of this:
- only display IPs for interfaces Multipass created (based on their MAC)
- show interface names as well (to help identify usable networks)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the entry points for multipass list and multipass info, and reproduce the reported unreachable address from the issue. Trace how instance IPs are collected and determine whether the intended behavior is to filter them or show interface names. Done means the command output no longer presents confusing unreachable addresses, with the chosen behavior covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100