Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
generalized port/IP rewriting #623
I count 10 issues and pull requests relating to handling port and/or IP address rewriting and unblocking.
These are almost invariably about IPv4 NAT modifying or blocking IP/port tuples at one end or the other. I could be a wag and shout "IPv6, already!", but I've already been doing that for 5 years, and we still haven't gotten past IPv4.
The problem that I see is that most of these issues/PRs address some narrow part of the problem specific to the reporter's network, and thus aren't broadly useful enough for inclusion into Mosh. I'd like to suggest that we come up with some more-general scheme for managing this issue.
My thoughts on this are ill-formed so far, but I have two ideas that I want to float:
All of this applies to both mosh-client and mosh-server.
An observation: when I wrote the change for #572, I certainly felt that there were other similar PRs solving it differently, and it seemed to reduce to the lack of a server-side config file. The client-side config piggybacks on .ssh/config, but not completely. And my change was a small step to having server-side config within the ssh constraints as well.