Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 4 days, 4 hrs ago - more...
|
2016-09-27
, 12:20
|
|
Posts: 188 |
Thanked: 223 times |
Joined on Apr 2013
@ Poland
|
#222
|
supl.nokia.com is dead, just like nokia itself. Change the value to:
But I still can't figure out what is it all about? Mine n900 got fix under a minute everytime, with no cellular data, only gps, even when I only stick it through the window.
With google supl it's doing the same, mostly under 5 seconds.
But yes, my previous n900 had problems with fixing, no matter if cellular data was enabled. It got partially broken stick on motherboard and broken antena (After hitting the ground really hard).
Last edited by Ridd92; 2016-09-27 at 12:31.
Code:
supl.google.com
With google supl it's doing the same, mostly under 5 seconds.
But yes, my previous n900 had problems with fixing, no matter if cellular data was enabled. It got partially broken stick on motherboard and broken antena (After hitting the ground really hard).
Last edited by Ridd92; 2016-09-27 at 12:31.
|
|
2016-09-27
, 12:38
|
|
Community Council |
Posts: 683 |
Thanked: 1,227 times |
Joined on Sep 2010
@ Mbabane
|
#223
|
dead? afaik it is NOT dead and still resolves to a valid address. On the other hand, I seem to remember N900 had problems with supl.google.com after the certificate problem was fixed for supl.nokia.com ... anyway, stopped using supl.google after supl.nokia started working again
as for the quick fixes on yours ... likely the result of ACWP and other variables (ephemeris data?). Take that N900 a long distance away, and not have a working SIM card ... and you'll probably be waiting for a fix for a long time too.
@gianko - supl.nokia.com still gives me near-instant fixes. i am on CSSU-T however, although I believe the certificate fix was incorporated in Stable as well
as for the quick fixes on yours ... likely the result of ACWP and other variables (ephemeris data?). Take that N900 a long distance away, and not have a working SIM card ... and you'll probably be waiting for a fix for a long time too.
@gianko - supl.nokia.com still gives me near-instant fixes. i am on CSSU-T however, although I believe the certificate fix was incorporated in Stable as well
|
|
2016-09-27
, 13:04
|
|
Posts: 188 |
Thanked: 223 times |
Joined on Apr 2013
@ Poland
|
#224
|
Originally Posted by sicelo
Ok, not dead, but I'm not sure about the functionality of supl.nokia. Just tested, with cellular data fix takes about a minute, like with no gsm at all. After switching to supl.google got fix in few second in slightly different position.
dead? afaik it is NOT dead and still resolves to a valid address. On the other hand, I seem to remember N900 had problems with supl.google.com after the certificate problem was fixed for supl.nokia.com ... anyway, stopped using supl.google after supl.nokia started working again
Originally Posted by sicelo
If I got fix when staying in one spot, then I can turn off the gsm and will have it fixed, even traveling 100km (Checked few days ago) with proper directions and so.
as for the quick fixes on yours ... likely the result of ACWP and other variables (ephemeris data?). Take that N900 a long distance away, and not have a working SIM card ... and you'll probably be waiting for a fix for a long time too
Originally Posted by sicelo
I'm on CSSU Stable, there is no problems with supl.google.com on this platform
supl.nokia.com still gives me near-instant fixes. i am on CSSU-T however, although I believe the certificate fix was incorporated in Stable as well
I'm not sure how it is all working, but it seems that slightly different configuration works differently on many devices. For now(and for me at least), if everything is fine with hardware there is only few if non problems at all
| The Following User Says Thank You to Ridd92 For This Useful Post: | ||
|
|
2016-09-27
, 13:14
|
|
Community Council |
Posts: 683 |
Thanked: 1,227 times |
Joined on Sep 2010
@ Mbabane
|
#225
|
very strange indeed. i also tried supl.google a few minutes ago, and because the gps data was mostly valid, the location was correct but 'coarse accuracy' - it didn't lock in 3 minutes. changed it back to 'supl.nokia' and as always, lock was done in less than 20s...
must be that your "it seems that slightly different configuration works differently on many devices" comment is correct, which actually sucks, haha
EDIT: have to add i did these tests indoors
must be that your "it seems that slightly different configuration works differently on many devices" comment is correct, which actually sucks, haha
EDIT: have to add i did these tests indoors
|
|
2016-09-27
, 17:07
|
|
Posts: 445 |
Thanked: 367 times |
Joined on Nov 2010
@ Italy
|
#226
|
Originally Posted by Ulle
According to this post the cert for Nokia is expired. I have no indoor fix with only wifi and A-gps. Tried both Google and Nokia supl but no fix. Btw if I ping supl.google.com I have replies but if I ping supl.nokia.com I got 100% packet lost but resolve the IP 54.93.209.220
It took longer than expected, but since today I get a new certificate for supl.nokia.com
Hope to see you all here again in a year!Code:Issuer: C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 Secure Server CA - G3 Validity Not Before: May 14 00:00:00 2015 GMT Not After : May 14 23:59:59 2016 GMT Subject: C=NL, ST=Noord-Brabant, L=Veldhoven, O=HERE Global BV, CN=supl.nokia.com
With Neo900 of course <wish>,running Maemo</wish>
__________________
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman
|
|
2016-09-27
, 19:52
|
|
Posts: 46 |
Thanked: 160 times |
Joined on Jun 2010
@ Germany, Berlin
|
#227
|
Hi gianko, the current cert of supl.nokia.com is not expired. It has been renewed in February.
This is the bash oneliner I use to check:
Works on N900 and most linux boxes.
For looking after other certificate problems see this post:
https://talk.maemo.org/showpost.php?...&postcount=101
Try the cmcli commands with your N900 and see if you get "Verified OK".
And for proper GPS-testing I suggest seeing the posts on this page:
https://talk.maemo.org/showthread.php?t=90651&page=6
and this post:
http://talk.maemo.org/showpost.php?p...5&postcount=31
I dont have any issues with GPS here currently. Using supl.nokia.com with fingers crossed ...
Anyway, glad to see some of you still using their "Apparat" here
Cheers, Ulle
This is the bash oneliner I use to check:
Code:
/usr/bin/openssl s_client -connect supl.nokia.com:7275 2>&1 | /bin/grep -A40 BEGIN | /usr/bin/openssl x509 -noout -text | /bin/grep -i -A1 -B3 "Not After"
For looking after other certificate problems see this post:
https://talk.maemo.org/showpost.php?...&postcount=101
Try the cmcli commands with your N900 and see if you get "Verified OK".
And for proper GPS-testing I suggest seeing the posts on this page:
https://talk.maemo.org/showthread.php?t=90651&page=6
and this post:
http://talk.maemo.org/showpost.php?p...5&postcount=31
I dont have any issues with GPS here currently. Using supl.nokia.com with fingers crossed ...
Anyway, glad to see some of you still using their "Apparat" here
Cheers, Ulle
|
|
2017-02-04
, 12:34
|
|
Community Council |
Posts: 683 |
Thanked: 1,227 times |
Joined on Sep 2010
@ Mbabane
|
#228
|
Hmm, noticed yesterday that I have problems with supl.nokia.com lately:
The device has CSSU-Thumb with openssl 0.9.8zh-1+maemo1+0m5+0cssu0
My other N900, with openssl 0.9.8zf-1+maemo1+0m5+0cssu0 gets quick fix, with exactly the same settings. Here's the log:
An interesting thing is - the 2nd N900 never tries to contact h-slp.mncXXX.mccXXX.pub.3gppnetwork.org, whereas the 2nd one does. XXX depends on the operator whose SIM is in the device
cmcli output for both N900 is the same
and with both,
Last edited by sicelo; 2017-02-04 at 21:05.
Code:
Feb 4 14:32:01 fremantle location-proxy[1297]: GLIB DEBUG default - Socket to supl.nokia.com opened, fd=12, verify_res=19 Feb 4 14:32:01 fremantle location-proxy[1297]: GLIB WARNING ** default - host: supl.nokia.com not verified, result: 19 Feb 4 14:32:01 fremantle location-proxy[1297]: GLIB WARNING ** default - Connection to h-slp.mnc002.mcc655.pub.3gppnetwork.org:7275 failed Feb 4 14:32:01 fremantle location-proxy[1297]: GLIB WARNING ** default - error:2006A066:BIO routines:BIO_get_host_ip:bad hostname lookup Feb 4 14:32:01 fremantle location-proxy[1297]: GLIB DEBUG default - Socket fd=12 closed on request
My other N900, with openssl 0.9.8zf-1+maemo1+0m5+0cssu0 gets quick fix, with exactly the same settings. Here's the log:
Code:
Feb 4 22:11:42 Nokia-N900 location-proxy[1300]: GLIB DEBUG default - Socket to supl.nokia.com opened, fd=12, verify_res=0 Feb 4 22:11:43 Nokia-N900 location-proxy[1300]: GLIB DEBUG default - Socket to supl.nokia.com opened, fd=13, verify_res=0 Feb 4 22:11:43 Nokia-N900 location-proxy[1300]: GLIB DEBUG default - Socket fd=12 closed on request Feb 4 22:11:43 Nokia-N900 location-proxy[1300]: GLIB DEBUG default - Socket fd=13 closed on request
cmcli output for both N900 is the same
Code:
cmcli -T common-ca -v supl.nokia.com:7275 1ad16dd494e161abd39bd94ed94bf8eafe4ede28 supl.nokia.com Verification failed: self signed certificate
Code:
openssl s_client -connect supl.nokia.com:7275 -CApath /etc/certs/common-ca/
...
...
New, TLSv1/SSLv3, Cipher is AES256-SHA
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1
Cipher : AES256-SHA
Session-ID: ...
Session-ID-ctx:
Master-Key: ...
Key-Arg : None
PSK identity: None
PSK identity hint: None
Start Time: 1486242237
Timeout : 300 (sec)
Verify return code: 0 (ok)
Last edited by sicelo; 2017-02-04 at 21:05.
| The Following User Says Thank You to sicelo For This Useful Post: | ||
|
|
2017-02-04
, 23:07
|
|
Community Council |
Posts: 683 |
Thanked: 1,227 times |
Joined on Sep 2010
@ Mbabane
|
#229
|
Found the problem
Downgraded all *maemosec* packages to versions 0.1.4+0m5 (had 0.1.5 from devel), and 0.2.3 (had 0.2.7 from devel, and my 2nd N900 has 2.4, but doesn't seem to be in any repos)
Instant fix on my 1st N900 and no attempts to contact 3gppnetwork.org
Last edited by sicelo; 2017-02-04 at 23:16. Reason: correcting the versions
Downgraded all *maemosec* packages to versions 0.1.4+0m5 (had 0.1.5 from devel), and 0.2.3 (had 0.2.7 from devel, and my 2nd N900 has 2.4, but doesn't seem to be in any repos)
Instant fix on my 1st N900 and no attempts to contact 3gppnetwork.org
Last edited by sicelo; 2017-02-04 at 23:16. Reason: correcting the versions
| The Following User Says Thank You to sicelo For This Useful Post: | ||
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman