Remote connection - signing in via SSH not working since update to 1.1.6.27

asked 2015-06-09 02:49:00 +0300

11677 ●187 ●289 ●324

updated 2015-06-20 23:30:12 +0300

As the title suggests; I can no longer sign in to my Jolla via SSH (over USB). Nothing has changed in puTTY and to double check, I made a fresh profile in puTTY, reconnected the cable, selected Developer Mode in the pop-up but still could not connect. No errors given on the PC, developer mode in use banner shows on phone but no 'log-in' prompt in puTTY terminal.

I disabled developer mode, rebooted and enabled developer mode once again, checked the option to allow signing in remotely and set my usual password. The USB IP address is (has been for many months) 192.168.3.15 (as my N900 already occupies 192.168.2.15)

Basically, nothing has changed on my PC, so it appears that the problem is on the phone, but I can't find it.

How-to - As per the comment from @wanderer given below, removal of the simlink file udhcpd.conffrom /etc seems to be enough.

To remove the file mentioned above, open terminal;

devel-su
rm /etc/udhcpd.conf
confirm with enter "After that connect your jolla via USB to your PC, it works again" - wanderer

edit retag flag offensive close delete

Comments

2

It works for me with 1.1.6.27 without having to change anything. Just wanted to point that out.

Yo ( 2015-06-09 15:02:58 +0300 )edit

1

Very strange. I had to ssh into my Jolla again today and it did not work. Removing udhcp.conf and dis-/enabling remote access cured it. Strange.

Yo ( 2015-07-13 23:28:35 +0300 )edit

3

answered 2015-06-09 11:46:01 +0300

Philippe De Swert
7698 ●74 ●88 ●91

updated 2015-06-09 11:49:41 +0300

Seems somehow the link migration fixes for usb-moded did not all make this update :( Anyway remove the symlink and it will be recreated normally again and things will work again.

Creating it by hand might create issues later on (although I think it would be removed anyway by the usb-moded logic)

To connect to do so make sure you set the ip on the pc side manually and check the ip on the jolla side.

edit flag offensive delete publish link

Comments

Thank you @Philippe De Swert - I removed udhcpd.conf as per another post about tethering. I can now SSH into my Jolla via USB, excellent!, file manipulation/editing is so much easier using SSH/puTTY.

Regards,

Spam Hunter ( 2015-06-09 14:19:58 +0300 )edit

Thanks! Had the same problem and after deleting the file it started working again.

yoktobit ( 2015-06-10 00:27:57 +0300 )edit

3

Well, these instructions are a bit cryptic, here is a more detailed instruction for not-so-techies :):

Open fingerterm
devel-su
rm /etc/udhcpd.conf
confirm with enter

After that connect your jolla via USB to your PC, it works again.

wanderer ( 2015-06-15 16:32:42 +0300 )edit

2

Can someone at jolla please explain how 1.1.6.27 shipped even though the issue with DHCP was reported? I can understand the the "silence sound" indicator is not considered a big deal but all forms of tethering/connecting to the phone?????

Seems to me a 1.1.6.28 that fixed the DHCP issue once and for all is what should have shipped to the non-beta tester customers...

Keeper-of-the-Keys ( 2015-06-21 00:12:23 +0300 )edit

@Keeper-of-the-Keys: Again normal WIFI tethering is not affected since it does not use udhcpcd. Also it does not affect MTP. That it somehow magically fixed the issue for you is co-incidence. Also I have no idea if the issue was reported and more importantly it only occurs in some corner cases.

Philippe De Swert ( 2015-06-21 10:37:13 +0300 )edit

0

answered 2015-06-09 08:33:34 +0300

TMavica

5514 ●89 ●132 ●124

http://twitter.com/TMavic...

create a "udhcpd.conf" in /tmp/ then put those inside: start 192.168.2.1 end 192.168.2.10 interface rndis0 option subnet 255.255.255.0

then systemctl restart udhcpd.service systemctl daemon-reload

Go developer mode, disable and renable agin set your new password

edit flag offensive delete publish link

Comments

@TMavica - the simple removal of the udhcpd.conf file seems to be enough to remedy the problem, no need to create that file, seems it is not required at all, at least in my case.

Spam Hunter ( 2015-06-09 14:21:17 +0300 )edit

No, creating /tmp/udhcpd.conf is not required and perhaps not even a good idea. Just delete /etc/udhcpd.conf. This symlink is created new afterwards, when you establish develeper mode connection, linking correctly to the new locaton /run/usb-moded/udhcpd.conf.

wanderer ( 2015-06-15 16:39:36 +0300 )edit

Remote connection - signing in via SSH not working since update to 1.1.6.27

Comments

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Remote connection - signing in via SSH not working since update to 1.1.6.27

Comments

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions