Notices


Reply
Thread Tools
Posts: 599 | Thanked: 717 times | Joined on Mar 2011 @ Nantes, France
#1
Hi,
I've activated the developer mode on my Jolla. It works on wifi (not so good because the wifi is pretty unstable, but it works).

I'm trying to use the dev mode through USB. The GUI tells me the address is 192.168.2.15 (as was on my N9), but:
- I can't ping this address (linux computer)
- I can't ssh "Connection refused"

I wonder if I have also to specify a password specifically for the USB Dev Mode connection?

Last edited by romu; 2014-11-20 at 11:24.
 
Community Council | Posts: 4,343 | Thanked: 10,722 times | Joined on May 2012 @ Southerrn Finland
#2
open terminal and check if the RNDIS interface really has the IP address assigned:

[nemo@Jolla ~]$
[nemo@Jolla ~]$ /sbin/ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2475 errors:0 dropped:0 overruns:0 frame:0
TX packets:2475 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:235064 (229.5 KiB) TX bytes:235064 (229.5 KiB)

rndis0 Link encap:Ethernet HWaddr 7E:25:BD:3E:7A:7C
inet addr:192.168.2.15 Bcast:192.168.2.255 Mask:255.255.255.0

inet6 addr: fe80::7c25:bdff:fe3e:7a7c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:222 errors:0 dropped:0 overruns:0 frame:0
TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34001 (33.2 KiB) TX bytes:24450 (23.8 KiB)

wlan0 Link encap:Ethernet HWaddr 50:56:A8:01:00:CD
inet addr:10.251.117.190 Bcast:10.251.119.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25087 errors:0 dropped:78 overruns:0 frame:0
TX packets:24637 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:20656500 (19.6 MiB) TX bytes:3626340 (3.4 MiB)

[nemo@Jolla ~]$
 

The Following User Says Thank You to juiceme For This Useful Post:
Posts: 84 | Thanked: 79 times | Joined on Dec 2013
#3
And do the same on the linux machine, if there's not interface with a 192.168.2.x IP it still won't work, even if it's correct on the Jolla.
 

The Following User Says Thank You to evk For This Useful Post:
anidel's Avatar
Posts: 1,740 | Thanked: 1,223 times | Joined on Jul 2006 @ Twickenham, UK
#4
I think, I might be wrong, that there's no DHCPd listening. So once you connect the Jolla to the PC, you've got to manually setup the IP for the PC's ethernet.
 

The Following User Says Thank You to anidel For This Useful Post:
Posts: 599 | Thanked: 717 times | Joined on Mar 2011 @ Nantes, France
#5
Thanks guy, it was correct on the Jolla and not on the PC. I just fixed an IP address to the USB link and it works.

Great thanks !
 
Community Council | Posts: 4,343 | Thanked: 10,722 times | Joined on May 2012 @ Southerrn Finland
#6
Originally Posted by anidel View Post
I think, I might be wrong, that there's no DHCPd listening. So once you connect the Jolla to the PC, you've got to manually setup the IP for the PC's ethernet.
Well, you're wrong there

[nemo@Jolla ~]$ ps aux | grep dhc
root 9657 0.0 0.0 1800 496 ? Ss 12:32 0:00 /usr/sbin/udhcpd -f
nemo 10488 1.0 0.1 5656 844 pts/0 S+ 13:26 0:00 grep dhc
[nemo@Jolla ~]$
 
Posts: 599 | Thanked: 717 times | Joined on Mar 2011 @ Nantes, France
#7
So, if @anidel was wrong, there's a bug in Jolla as my PC got a 192.168.1.x address, not unable to communicate with 192.168.2.x.
 
Posts: 46 | Thanked: 285 times | Joined on Dec 2005
#8
Originally Posted by romu View Post
So, if @anidel was wrong, there's a bug in Jolla as my PC got a 192.168.1.x address, not unable to communicate with 192.168.2.x.
I would say something is wrong on your pc end as the Jolla hands out a correct dhcp address for me.

#sudo dhclient -d usb0
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/usb0/ca:0b:76:64:90:8c
Sending on LPF/usb0/ca:0b:76:64:90:8c
Sending on Socket/fallback
DHCPREQUEST of 192.168.3.8 on usb0 to 255.255.255.255 port 67 (xid=0x5a290e3c)
DHCPNAK from 192.168.2.15 (xid=0x5a290e3c)
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 3 (xid=0x7a117a84)
DHCPREQUEST of 192.168.2.9 on usb0 to 255.255.255.255 port 67 (xid=0x7a117a84)
DHCPOFFER of 192.168.2.9 from 192.168.2.15
DHCPACK of 192.168.2.9 from 192.168.2.15
bound to 192.168.2.9 -- renewal in 428058 seconds.

Disconnect, change the ip in the developer mode UI. Reconnect:

$ sudo dhclient -d usb0
Internet Systems Consortium DHCP Client 4.2.4
Copyright 2004-2012 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/usb0/be:55:8a:9c:d0:51
Sending on LPF/usb0/be:55:8a:9c:d0:51
Sending on Socket/fallback
DHCPREQUEST of 192.168.2.9 on usb0 to 255.255.255.255 port 67 (xid=0x21b2b815)
DHCPNAK from 192.168.3.18 (xid=0x21b2b815)
DHCPDISCOVER on usb0 to 255.255.255.255 port 67 interval 3 (xid=0x39b67e63)
DHCPREQUEST of 192.168.3.8 on usb0 to 255.255.255.255 port 67 (xid=0x39b67e63)
DHCPOFFER of 192.168.3.8 from 192.168.3.18
DHCPACK of 192.168.3.8 from 192.168.3.18
bound to 192.168.3.8 -- renewal in 364451 seconds.
 

The Following 3 Users Say Thank You to Philippe For This Useful Post:
Posts: 599 | Thanked: 717 times | Joined on Mar 2011 @ Nantes, France
#9
That's a possibility.
 
Reply

Tags
developer

Thread Tools

 
Forum Jump


All times are GMT. The time now is 20:49.