Client not working on Bash on Windows #781

Closed
spkujis opened this Issue Jul 29, 2016 · 20 comments

Comments

Projects
None yet
9 participants
@spkujis

spkujis commented Jul 29, 2016

When I try to use mosh as client with Bash on Windows, I get the following error:
Network exception: setsockopt: Invalid argument

I am not a developer and I know Bash on Windows is still in heavy development, but could this be something that can/needs be fixed in mosh?

Versions:
mosh 1.2.5 compiled from .tar.gz on this system (default repositories have 1.2.4a-1ubuntu1)
Windows 10 Insider Preview 14393

If you don't have access to Bash on Windows, I will gladly try to help, if you decide to look into this.

@Doridian

This comment has been minimized.

Show comment
Hide comment
@Doridian

Doridian Aug 2, 2016

I am having a similar problem on Bash for Windows (or Linux Subsystem for Windows):

All I get on a successful connection is this:

user@PC:~$ mosh user@host


[mosh is exiting.]

Doridian commented Aug 2, 2016

I am having a similar problem on Bash for Windows (or Linux Subsystem for Windows):

All I get on a successful connection is this:

user@PC:~$ mosh user@host


[mosh is exiting.]
@glensc

This comment has been minimized.

Show comment
Hide comment
@glensc

glensc Aug 2, 2016

check if other tools like tmux work:
https://blogs.msdn.microsoft.com/commandline/2016/06/08/tmux-support-arrives-for-bash-on-ubuntu-on-windows/

as i read PTY support is not complete there, but probably there are updates on that....

glensc commented Aug 2, 2016

check if other tools like tmux work:
https://blogs.msdn.microsoft.com/commandline/2016/06/08/tmux-support-arrives-for-bash-on-ubuntu-on-windows/

as i read PTY support is not complete there, but probably there are updates on that....

@Doridian

This comment has been minimized.

Show comment
Hide comment
@Doridian

Doridian Aug 2, 2016

tmux runs fine, screen just exits without an error like mosh

Doridian commented Aug 2, 2016

tmux runs fine, screen just exits without an error like mosh

@cgull

This comment has been minimized.

Show comment
Hide comment
@cgull

cgull Aug 2, 2016

Member

I thought I answered this days ago, but I'm wrong.

Mosh almost works in Windows Subsystem for Linux. Its pty support is now fine for Mosh. At this point, only one thing is keeping Mosh from working-- a missing socket option for path MTU discovery causes Mosh to exit. My position is that if Microsoft is offering Linux binary compatibility, this is their problem to fix. However, the fix would be easy, and we have discussed changing how we do MTU discovery anyway.

I have a branch with the necessary changes (and some extras), https://github.com/cgull/mosh/tree/wsl-workarounds-14361.

Member

cgull commented Aug 2, 2016

I thought I answered this days ago, but I'm wrong.

Mosh almost works in Windows Subsystem for Linux. Its pty support is now fine for Mosh. At this point, only one thing is keeping Mosh from working-- a missing socket option for path MTU discovery causes Mosh to exit. My position is that if Microsoft is offering Linux binary compatibility, this is their problem to fix. However, the fix would be easy, and we have discussed changing how we do MTU discovery anyway.

I have a branch with the necessary changes (and some extras), https://github.com/cgull/mosh/tree/wsl-workarounds-14361.

@Doridian

This comment has been minimized.

Show comment
Hide comment
@Doridian

Doridian Aug 2, 2016

@cgull Beautiful, I merged your branch with the latest of master (no significant changes, but if I build a nightly, might as well be latest) and now mosh works. Thanks :)

Doridian commented Aug 2, 2016

@cgull Beautiful, I merged your branch with the latest of master (no significant changes, but if I build a nightly, might as well be latest) and now mosh works. Thanks :)

@cgull

This comment has been minimized.

Show comment
Hide comment
@cgull

cgull Aug 3, 2016

Member

I forgot to mention, I've reported this and it's in their queue: Microsoft/WSL#170

Member

cgull commented Aug 3, 2016

I forgot to mention, I've reported this and it's in their queue: Microsoft/WSL#170

@kaepora

This comment has been minimized.

Show comment
Hide comment
@kaepora

kaepora Aug 17, 2016

I am also having this problem.

kaepora commented Aug 17, 2016

I am also having this problem.

@keithw keithw referenced this issue in rpwoodbu/mosh-chrome Aug 20, 2016

Closed

Chrome App Migration? #127

@cgull

This comment has been minimized.

Show comment
Hide comment
@cgull

cgull Oct 13, 2016

Member

The Microsoft people have heard your votes :)
Microsoft/WSL#170 (comment)

Member

cgull commented Oct 13, 2016

The Microsoft people have heard your votes :)
Microsoft/WSL#170 (comment)

@deadalnix

This comment has been minimized.

Show comment
Hide comment
@deadalnix

deadalnix Jan 3, 2017

While microsoft is getting its shit together, what are the workaround options ?

While microsoft is getting its shit together, what are the workaround options ?

@cgull

This comment has been minimized.

Show comment
Hide comment
@cgull

cgull Jan 5, 2017

Member

Compiling the above-mentioned branch from source, or using Mosh under Cygwin or Msys2 are all usable workarounds.

Member

cgull commented Jan 5, 2017

Compiling the above-mentioned branch from source, or using Mosh under Cygwin or Msys2 are all usable workarounds.

@deadalnix

This comment has been minimized.

Show comment
Hide comment

Thanks.

@metasoarous

This comment has been minimized.

Show comment
Hide comment
@metasoarous

metasoarous Jan 13, 2017

For the record, there's also this issue: Microsoft/WSL#1140

For the record, there's also this issue: Microsoft/WSL#1140

@cgull

This comment has been minimized.

Show comment
Hide comment
@cgull

cgull Mar 26, 2017

Member

Windows Insider build 15002 and later support Mosh, and in all likelihood that means it goes into the Windows Creator update as well.

Member

cgull commented Mar 26, 2017

Windows Insider build 15002 and later support Mosh, and in all likelihood that means it goes into the Windows Creator update as well.

@cgull cgull closed this Mar 26, 2017

@deadalnix

This comment has been minimized.

Show comment
Hide comment
@deadalnix

deadalnix Mar 28, 2017

I can confirm it is fixed using insider builds.

I can confirm it is fixed using insider builds.

@huyinjie

This comment has been minimized.

Show comment
Hide comment
@huyinjie

huyinjie Mar 29, 2017

@cgull I am waiting Creator Update,hoping it won't Disappoint me.

@cgull I am waiting Creator Update,hoping it won't Disappoint me.

@hossbeast

This comment has been minimized.

Show comment
Hide comment
@hossbeast

hossbeast Jun 6, 2017

Just got the Windows Creator Update, and the first thing I did was boot up bash and try mosh.

Failure on the client with this error:
mosh: Nothing received from server on UDP port 60001.

Client
todd@hossbeast:~$ mosh --version
mosh 1.2.4a

Server (Ubuntu 16.04.1)
0 % mosh --version
mosh 1.2.5 [build mosh 1.2.5]

Just got the Windows Creator Update, and the first thing I did was boot up bash and try mosh.

Failure on the client with this error:
mosh: Nothing received from server on UDP port 60001.

Client
todd@hossbeast:~$ mosh --version
mosh 1.2.4a

Server (Ubuntu 16.04.1)
0 % mosh --version
mosh 1.2.5 [build mosh 1.2.5]

@hossbeast

This comment has been minimized.

Show comment
Hide comment
@hossbeast

hossbeast Jun 6, 2017

I built from source and updated both sides to mosh-1.3.0, and continue to receive the same error.

I built from source and updated both sides to mosh-1.3.0, and continue to receive the same error.

@cgull

This comment has been minimized.

Show comment
Hide comment
@cgull

cgull Jun 7, 2017

Member

@hossbeast, mosh works fine for me on the Windows Creator 1703 build. The message you're getting is likely due to network connectivity issues, not issues with Windows itself. Windows firewall/AV software can be difficult in this area. Please try the troubleshooting tips in the FAQ at https://mosh.org.

Member

cgull commented Jun 7, 2017

@hossbeast, mosh works fine for me on the Windows Creator 1703 build. The message you're getting is likely due to network connectivity issues, not issues with Windows itself. Windows firewall/AV software can be difficult in this area. Please try the troubleshooting tips in the FAQ at https://mosh.org.

@hossbeast

This comment has been minimized.

Show comment
Hide comment
@hossbeast

hossbeast Jun 7, 2017

@cgull thanks, I assumed from my reading of this thread there was some Windows fix I needed, and jumped to conclusions. I fixed the firewall issue, and it now appears to be working.

@cgull thanks, I assumed from my reading of this thread there was some Windows fix I needed, and jumped to conclusions. I fixed the firewall issue, and it now appears to be working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment