Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NAT confuses shoop #24

Open
hukka opened this issue Aug 9, 2016 · 2 comments
Open

NAT confuses shoop #24

hukka opened this issue Aug 9, 2016 · 2 comments

Comments

@hukka
Copy link

hukka commented Aug 9, 2016

  • opening UDT connection...[E] errrrrrrr connecting to 192.168.1.4:60500 - UdtError { err_code: 1001, err_msg: "Connection setup failure: connection time out." }

which makes sense, as the client is not inside the LAN. But it should make the UDT connection to the same ip as the original ssh did.

@mcginty
Copy link
Owner

mcginty commented Aug 9, 2016

Hmm, I guess that means we can't trust the SSH_CONNECTION env variable? I think that's how mosh does it though, I wonder what's different about your situation.

@hukka
Copy link
Author

hukka commented Aug 10, 2016

Indeed, when connecting from NATed client to NATed server, the SSH_CONNECTION shows the client's external IP on the server, but the internal IP for the server itself. mosh works fine, but I don't know how it decides the IPs to send the UDP packets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants