ipv6 support for Jolla infrastructure

Question

31

ipv6 support for Jolla infrastructure

asked 2014-02-05 20:01:00 +0300

Cmdr_Zod
5098 ●51 ●65 ●64

updated 2017-11-26 02:15:09 +0300

I recently got native IPv6 internet access and gave the Jolla a try in a IPv6 only test environment. The Jolla received an IP-Address, but the WLAN-Icon showed an Exclamation Mark, although I had connectivity (I could browse for example wikipedia). Unfortunately, the Jolla infrastructure is not ready for the future:

The Store was not available
together.jolla.com is not available
www.jolla.com is not available
harbour.jolla.com is not available
sailfishos.org is not available
shop.jolla.com is not available

I know it is not yet a large problem for the average user in middle Europe (first providers are rolling out native ipv6 with Carrier-grade NAT for IPv4), the shortage of IPv4 addresses is more evident in Asia and Africa, and Jolla announced it wants to enter the Chinese market.

When can we expect a fully IPv6 ready Jolla infrastructure?

Update 2016: More than two years have passed since my initial request, any news on this?

Update 2017: Another year has passed, more and more providers are putting their ipv4-users behind carrier grade NAT unless they protest or pay more, while IPv6 gets more adoption. And we still see no change from Jolla.

edit retag flag offensive close delete

Comments

1

Actually, this is an issue for some (like me), since I only have NAT64 (but no native IPv4 locally). The Jolla icon is greyed out all time time (I've never seen the exclamation mark. Maybe it was for older versions?).

The applications themselves DO work though, meaning that they work over native IPv6 (eg: there's not stupid programming errors where they assume IPv4 is available).

WhyNotHugo ( 2014-05-17 06:20:53 +0300 )edit

It's 2016 but I still don't have access to jolla.com :(

$ ping6 jolla.com
unknown host
$ dig -t AAAA jolla.com

; <<>> DiG 9.10.3-P4-Ubuntu <<>> -t AAAA jolla.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32867
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;jolla.com.         IN  AAAA

;; AUTHORITY SECTION:
jolla.com.      608 IN  SOA ns-615.awsdns-12.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 3600

;; Query time: 81 msec
;; SERVER: 193.180.164.2#53(193.180.164.2)
;; WHEN: Sat Aug 13 17:23:05 MSK 2016
;; MSG SIZE  rcvd: 119

Marzanna ( 2016-08-13 17:23:38 +0300 )edit

Jolla doesnt support ipv6 on their mobike phones either, from what i can see. When trying to use ipv6 for mobile data connection using SFOS 2.0.5.6 it fails to upload or download any data.

DarkTuring ( 2017-01-18 18:39:23 +0300 )edit

I used a Jolla One on an IPv6-only environment for years, so you might want to double check those results/network.

WhyNotHugo ( 2017-01-18 18:43:11 +0300 )edit

Actually, this is an issue for some (like me), since I only have NAT64 (but no native IPv4 locally). The Jolla icon is greyed out all time time (I've never seen the exclamation mark. Maybe it was for older versions?).
The applications themselves DO work though, meaning that they work over native IPv6 (eg: there's not stupid programming errors where they assume IPv4 is available).
WhyNotHugo ( 2014-05-17 06:20:53 +0300 )edit
It's 2016 but I still don't have access to jolla.com :(
$ ping6 jolla.com unknown host $ dig -t AAAA jolla.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> -t AAAA jolla.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32867 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;jolla.com. IN AAAA ;; AUTHORITY SECTION: jolla.com. 608 IN SOA ns-615.awsdns-12.net. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 3600 ;; Query time: 81 msec ;; SERVER: 193.180.164.2#53(193.180.164.2) ;; WHEN: Sat Aug 13 17:23:05 MSK 2016 ;; MSG SIZE rcvd: 119
Marzanna ( 2016-08-13 17:23:38 +0300 )edit
Jolla doesnt support ipv6 on their mobike phones either, from what i can see. When trying to use ipv6 for mobile data connection using SFOS 2.0.5.6 it fails to upload or download any data.
DarkTuring ( 2017-01-18 18:39:23 +0300 )edit
I used a Jolla One on an IPv6-only environment for years, so you might want to double check those results/network.
WhyNotHugo ( 2017-01-18 18:43:11 +0300 )edit

Answer 1

9

answered 2014-02-05 23:36:58 +0300

tigeli

9543 ●111 ●112 ●130

admin

First of all, the exclamation mark is only about to show the user that there might be a problem with the connection but it does not mean that every node is down on the Internet. Both ipv4.jolla.com and ipv6.jolla.com are used to check the connectivity but it's pretty much connectivity to Jolla infrastructure.

We do not yet have a public information to share about Jolla infrastructure being available through IPv6 but we are working on it. However it's not a high prio at the moment related to other things going on.

edit flag offensive delete publish link

Comments

1

Most of Finland is (hopefully) starting to use IPv6 on 2015-06-09 and it would be nice if Jolla infrastructure was ready before that time.

Mikaela ( 2015-01-25 10:44:38 +0300 )edit

2

IPv6 day came and went and now all customers of Elisa and DNA have native IPv6 on mobile, DNA also on physical connections and Sonera has 6rd, so importance of IPv6 would increase.

ARIN is also running out of IPv4.

Mikaela ( 2015-07-13 15:19:09 +0300 )edit

Answer 2

2

answered 2014-02-05 20:09:35 +0300

Sailor

8053 ●81 ●106 ●124

As far as I have seen Jolla is using ipv4.jolla.com to check if there is connectivity if it's pingable the exclamation mark is removed from the WLAN-Icon. There is also ipv6.jolla.com but it seems it's not used as indicator. I would also like to see a IPv6 ready environment. But first Dhcpv6 should be fixed on the phone itself in my opinion. https://together.jolla.com/question/11757/dhcpv6-rfc3315-support-on-jolla/

edit flag offensive delete publish link

Comments

1

DHCPv6 isn't necesary (though I agree it should be working), as you can have NDP for IP/DNS/router discovery.

WhyNotHugo ( 2014-05-17 06:19:24 +0300 )edit

2

Sure it is necessary because in enterprise envs it is often used.

Sailor ( 2014-05-17 14:15:09 +0300 )edit

1

Again, that just proves it's not necessary, merely importan. We have RA, which predates DHCPv6 to get IPs for now. Fixing what we already have comes before new features.

WhyNotHugo ( 2014-06-10 22:40:55 +0300 )edit

Answer 3

1

answered 2014-02-05 23:28:13 +0300

jr
421 ●6 ●13 ●15

One option is to edit /etc/connman/main.conf file and comment out the Ipv4StatusUrl and/or Ipv6StatusUrl lines. This way connman will use the default hosts ipv4.connman.net and/or ipv6.connman.net, those default hosts are working properly even for IPv6 when doing the connectivity check.

edit flag offensive delete publish link

Comments

1

ipv6.jolla.com is working too for ipv6.

tigeli ( 2014-02-05 23:38:48 +0300 )edit

ipv6 support for Jolla infrastructure

Comments

3 Answers

Comments

Comments

Comments

Question tools

Stats

Related questions

ipv6 support for Jolla infrastructure

Comments

3 Answers

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions