mobile-shell / mobile-shell/mosh
Allow binding mosh traffic to a specific interface.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 14.5k
- Forks
- 865
- PR merge metrics
- No merged PRs in 30d
Description
I have a situation where my laptop is connected to both a wifi and ethernet network, with the ethernet as the primary interface.
My problem is that (for some unknown reason) I can't connect to mosh over the ethernet network, but I can over the wifi network. I'd like to be able to specify that mosh send its traffic over the wifi interface. The SSH side of things can (hopefully) be handled by using the -b flag and the --ssh mosh command (not ideal, but I can live with it).
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by identifying the mosh traffic path and how a specific interface could be selected, while considering the separate SSH connection. Done means mosh traffic can be bound to the requested interface without requiring SSH to use the same binding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100