Originally Posted by ejjoman

Can you ping your computer from your recovery shell? Can you try to ping the IP of some public service, like the Google DNS (8.8.8.8)?

Originally Posted by Kabouik

No, I get "permission denied" when trying to ping an IP, and unknown host when pinging a url. This is from chroot, but ping works better when ran out of chroot (just going into Recovery shell and using ping immediately without the mount points and the chroot), I mean I don't get permission issues, but there is still no internet access.

Here is an output of what I get when trying to follow the guide on TJC:

Code:

/ # mkdir /mnt/rootfs
 
/ # mount /dev/mapper/sailfish-root /mnt/rootfs
 
/ # chroot /mnt/rootfs
 
bash-3.2# mount /proc
 
bash-3.2# mount /sys
 
bash-3.2# mount /dev/pts
 
bash-3.2# echo "nameserver 8.8.8.8" >> /etc/resolv.conf
 
bash-3.2# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.42.66.64     *               255.255.255.248 U     0      0        0 rndis0
192.168.2.0     *               255.255.255.0   U     0      0        0 rndis0
 
bash-3.2# route add default gw 10.42.66.67
 
bash-3.2# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         10.42.66.67     0.0.0.0         UG    0      0        0 rndis0
10.42.66.64     *               255.255.255.248 U     0      0        0 rndis0
192.168.2.0     *               255.255.255.0   U     0      0        0 rndis0
 
bash-3.2# su
 
[root@(none) /]# ip -4 addr
3: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    inet 10.42.66.66/29 brd 10.42.66.255 scope global rndis0
       valid_lft forever preferred_lft forever
    inet 192.168.2.15/24 brd 192.168.2.255 scope global rndis0:0
       valid_lft forever preferred_lft forever
 
[root@(none) /]# ip route
default via 10.42.66.67 dev rndis0 
10.42.66.64/29 dev rndis0  proto kernel  scope link  src 10.42.66.66 
192.168.2.0/24 dev rndis0  proto kernel  scope link  src 192.168.2.15
 
[root@(none) /]# tracepath -n 8.8.8.8
 1:  send failed
     Resume: pmtu 65535
 
[root@(none) /]# ping -c 5 google.com
ping: unknown host google.com

[root@(none) /]# exit
exit

bash-3.2# ifconfig
rndis0    Link encap:Ethernet  HWaddr B6:23:76:8C:DC:63  
          inet addr:10.42.66.66  Bcast:10.42.66.255  Mask:255.255.255.248
          inet6 addr: fe80::b423:76ff:fe8c:dc63/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1188 errors:0 dropped:0 overruns:0 frame:0
          TX packets:505 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:91017 (88.8 KiB)  TX bytes:60383 (58.9 KiB)

rndis0:0  Link encap:Ethernet  HWaddr B6:23:76:8C:DC:63  
          inet addr:192.168.2.15  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

The computer can ping the Jolla C at 10.42.66.66, and I have run this from it and it returned no error:

Code:

sudo sysctl net.ipv4.ip_forward=1 
sudo iptables -t nat -A POSTROUTING -o wlp2s0 -j MASQUERADE

But somehow, something is still perventing it to share internet to the Jolla C, or the Jolla C to pick up.

[Edit] Finally reset to factory state, I love my original Jolla and I largely prefer it over my Jolla C for its form factor actually, but there is an Androdi application that requires 4.4.4 that I need to run and I can't on the Jolla due to its older version of Aliendalvik.

Originally Posted by nieldk

Is wlp2s0 your internet device on your computer?
Not wlan0?

Originally Posted by deutch1976

Is it already possible, after a phone flash, to update directly to 2.1.1 or do we still have to update one by one? Thanks

Originally Posted by elastic

Sailfish 1.x hat a quite simple and intuitive user interface compared to 2.x - already forgot that ...