Arch Linux

89c51

Member

Registered: 2012-06-05

Posts: 741

Mosh (remote terminal) questions.

I use mosh on my local network. (between desk and laptop)

i get the message below quite often.

mosh vvvv@testland.local
/usr/bin/mosh: Could not resolve hostname testland.local
ssh_exchange_identification: Connection closed by remote host
/usr/bin/mosh: Did not find remote IP address (is SSH ProxyCommand disabled?).

I found this > https://github.com/keithw/mosh/issues/311 but i cant relate to anything mentioned in it.

Also if i put an ethernet wire to the laptop and shut the wifi the connection is lost.  If i turn the wifi back on it connects again to the mosh server. Is it supposed to work this way or i mis configured something.

Thanks in advance.

Last edited by 89c51 (2014-11-14 17:05:00)

MoonSwan

Member

From: Great White North

Registered: 2008-01-23

Posts: 881

Re: Mosh (remote terminal) questions.

Have you tried leaving the wifi off and booting the laptop with only the wire present?  Does your test work if you use an IP address instead of a host name?  Got anything exotic running like that other poster's stderr?

89c51

Member

Registered: 2012-06-05

Posts: 741

Re: Mosh (remote terminal) questions.

I tried a few things and it seems that after restarting avahi-daemon.service it connected. But it can be random. I tested with IP instead of hostname and seemed to behave better.

Need to do more testing.And no i don't have anything exotic.

Also to rephrase the  second question: Is only the client allowed to change IP in order to maintain a connection or can the server change IP also and mosh will keep working.

MoonSwan

Member

From: Great White North

Registered: 2008-01-23

Posts: 881

Re: Mosh (remote terminal) questions.

I'm afraid I can't answer your last question because I'm not that knowledgeable about Mosh.  Maybe you could look at mosh's website and find something?

89c51

Member

Registered: 2012-06-05

Posts: 741

Re: Mosh (remote terminal) questions.

Thanks anyway.

The connection thing seems to be random. Today it failed all the ways (ethernet wifi ip hostname etc). After a reboot it somehow connected after a few tries. 

Could it be HW related (router or laptop)?

Last edited by 89c51 (2014-11-17 10:03:14)

MoonSwan

Member

From: Great White North

Registered: 2008-01-23

Posts: 881

Re: Mosh (remote terminal) questions.

Yes, it very well could!  Try changing the cables first (that's the easiest thing to do) and if things don't improve change another piece of hardware one at a time to see if you can isolate the issue.  E.G. A spare router at this point would be also a good thing to try changing and/or the network card.

89c51

Member

Registered: 2012-06-05

Posts: 741

Re: Mosh (remote terminal) questions.

Error: org.freedesktop.Avahi.TimeoutError: Timeout reached

This is an error i get and from reading around it says that is due to firewall (which i don't have) and broken multicast network driver on the card.

Laptop HW:

01:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller

So it's most likely a combination of the broadcom chip or/and avahi or sshd acting weird.

Last edited by 89c51 (2014-11-17 20:14:17)

MoonSwan

Member

From: Great White North

Registered: 2008-01-23

Posts: 881

Re: Mosh (remote terminal) questions.

Does the chip work in other situations?  For example, can you browse the web with it and do other mundane things?  Have you tried a different LAN cable?  Swap the router out for another (if you can)?  Is there another drive you can use then try that too.Did you read about the Broadcom's quirks and foibles on the wiki at all?  If not, I'd suggest you look there if the hardware isn't the issue.

89c51

Member

Registered: 2012-06-05

Posts: 741

Re: Mosh (remote terminal) questions.

The internet works fine (afai can tell) on that machine. Its just the remote connection/avahi stuff that is dodgy. And sadly i don't have another router to test.

Last edited by 89c51 (2014-11-18 13:11:32)

MoonSwan

Member

From: Great White North

Registered: 2008-01-23

Posts: 881

Re: Mosh (remote terminal) questions.

So only the wifi connection is being a pain?  If you've tested the hardware that you can swap out then the only other possibility I can come up with is a mis-configured router or wifi setup.  You could go to the networking page on the wiki and work through a manual setup of your wifi connection.  Following that might point you to where the presumed mis-configuration lays.

89c51

Member

Registered: 2012-06-05

Posts: 741

Re: Mosh (remote terminal) questions.

It sometimes misbehaved with ethernet also. So it might be something software related. I need to test more. Thanks for the answers.