We have moved to a new Sailfish OS Forum. Please start new discussions there.
92

[hotfix] Opt-in hotfix for connectivity in upcoming update 7 [not relevant]

asked 2014-06-09 16:06:07 +0300

Aard gravatar image

updated 2015-07-25 21:31:16 +0300

eric gravatar image

Update: we just released this to subscribers. (12.6., 14:20 EEST)

We've been working for a while on updating connman to a newer version (from 1.15 to 1.23). It will fix connectivity issues in some environments - but comes at a regression risk in some networks where the old one worked fine.

We used all the different networks available to us to identify and fix issues - but there's a lot more interesting network hardware out there, so we decided not to include it in update7, but make it available for community members as opt-in hotfix, which will be published the same week as the update, hoping that the new stack gets the toughest and widest audience for testing.

If you want to test the new connectivity stack please send an email with arbitrary content to connman-hotfix@jolla.com, making sure the From-Address used is the one matching your Jolla account. After processing your email (which may take a while) you should get an update notification and be able to install the hotfix like any regular update.

Please add new issues as answers to this post or for already known issues add a comment to the answer describing your issue. If you want to go back to the old connectivity stack just send an email to connman-hotfix-opt-out@jolla.com, after a while you'll get an update notification which will bring you back to the main update.

edit retag flag offensive reopen delete

The question has been closed for the following reason "question is not relevant or outdated" by chemist
close date 2014-09-21 17:48:02.092477

Comments

This is cool, but wouldn't it be cooler by following/unfollowing here or via store?

harry ( 2014-06-09 16:21:12 +0300 )edit
8

I think this is the appropriate way - if it was too easy to opt-in, inexperienced users might try it and break something.

nodevel ( 2014-06-09 16:24:13 +0300 )edit

would be better if one could hotswap between the versions, so i could test both in places that i dont visit all too often and have baf reception like my summer home in the middle of nowhere.

Whippler ( 2014-06-09 16:27:44 +0300 )edit
11

Does this version support WPA2-PSK/AES (and others) networks or do we need to install the patched wpa_supplicant again?

Alex ( 2014-06-09 16:34:29 +0300 )edit
8

To be clear, this only affects wifi and bluetooth? Not the normal GSM/LTE reception?

BonoNL ( 2014-06-09 16:37:44 +0300 )edit

23 Answers

Sort by » oldest newest most voted
4

answered 2014-06-13 07:59:16 +0300

WhyNotHugo gravatar image

updated 2014-06-13 12:28:05 +0300

This issue (not picking up the advertised default gateway), introduced in 1.0.7.16 seems to have gone (hasn't ocurred again since, but it's always hard to tell with these intermitent issues if it was fixed or I've just been lucky).


No real improvement over connectivity. I used to have lots of disconnections and the device failed to reconnect after that. I've since discovered that the device does reconnect, but has no IP address:

ifconfig | grep inet6
inet6 addr: ::1/128 Scope:Host

You know what I realized about that? The device needs a local-link to subscribe to the RA multicast address. The device seems to NOT have a local-link address, and that's very wrong. This is probably why it's not getting any internet access.

Maybe I can provide new feedback regarding my issue? I'd be more than happy to help.


UPDATE: If I try to do stuff like "check mail", I get the wireless connection dialog, every time. I pick my home network, but the same keeps happening (as noted above, it seems I'm actually connected, but IPless). As a workaround, I've found that disabling wireless and re-enabling it generally picks up an IP.

edit flag offensive delete publish link more
0

answered 2014-06-13 08:40:25 +0300

zlatko gravatar image

I have updated to hot-fix. A connection problem appeared, which I do not know if connected to connman: During the upgrade I had my personal SIM inside the device. After that I inserted my business SIM and now mobile data is inactive. If I revert back to private SIM - mobile data is working. Both SIMs are one mobile operator, but as I work for this operator, the business one is getting different IP so it can access some parts of the corporate network. I tried several reboots, I deleted the settings for cellular in /var/lib/connman hoping that they will be recreated again. Inserted several time the different SIMs - still when business SIM inside mobile data is disabled. Any ideas? May be @Aard can suggest what to try to get back the mobile data? It had been working for months with business SIM.

edit flag offensive delete publish link more

Comments

I had a similar problem, without and also with the hotfix. I am only using one SIM card, but yesterday mobile network was gone. It worked after update to 1.0.7.16, what I installed on monday. But yesterday mobile stopped working. The option was greyed out. Trying to set the mobile provider manually failed. it did not find anything.

Then today the hotfix was available for me and I installed it. Automatic discovery of the mobile provider still didn't worked, but now I can choose it manually what fixed the problem for me.

Buschmann ( 2014-06-13 16:25:37 +0300 )edit

I managed to fix my issue:

  1. When I checked /var/lib/ofono/grps - I found out AccessPointName was missing.

  2. I stopped ofono with systemctl stop ofono.service

  3. Edited gprs file adding APN

  4. Started ofono: systemctl stop ofono.service

And voila! - all is working now :)

Still have not tried rebooting the phone though...

zlatko ( 2014-06-13 21:25:58 +0300 )edit
3

answered 2014-06-13 10:21:58 +0300

updated 2014-06-13 10:31:15 +0300

At first: Thank you to let us beta-test some of your changes. I hope, we are able to test more new software / releases in the feature.

Now to the hotfix:

I had troubles from the beginning, to connect my Jolla to my WLAN. It was absolutely unstable and I got errors like "Connection Error" and "Wrong value [...]". So I tested around and changed my WLAN encryption from WPA2/PSK-only to WPA/PSK-only (AES).

After that change, all Problems where gone and my Jolla connected with my WLAN without any (or very few) problems. But I think, that this could not be the final solution for this.

So I installed the hotfix yesterday and I tested my WLAN connection again. I updated the firmware of all my hardware to the latest versions:

  • TP-Link TL-WR1043ND with latest OpenWRT snapshot (11.06.2014)
  • TP-Link TL-WDR4900 with latest OpenWRT snapshot (11.06.2014)
  • TP-Link Powerline WLAN Access-point TP-Link TL-WPA4220 with latest firmware

After the firmware updates, I changed the WLAN encryption from WPA/PSK-only to WPA2/PSK-only again and played around a bit.

At first my Jolla connected without any problems to my WLAN, but after a while the connection problems appeared again. My Jolla lost the connection and I was able to reconnect by selecting my WLAN manually. But that happened quite often and this morning my Jolla completely refused to connect to my WLAN and I had to reboot it to get it working again. So I decided to switch the encryption back again and now it works perfectly.

In my /var/log/wpa_supplicant.log I have a lot of these two messages:

  • wlan0: CTRL-EVENT-SCAN-STARTED
  • rfkill: WLAN unblocked

All of them sometimes 6+ times in a row.

So for me, this hotfix did not solve my connection problems at all. I hope, this could be fixed somehow in the future.

edit flag offensive delete publish link more

Comments

I also have 3 access points and the same issue. How did you change to AES? I don't see sny option to chsnge it.

dash72 ( 2014-06-15 23:06:33 +0300 )edit

You have to do that on AP-side. There doesn't seem to be an (UI-)option on our Jolla to stick the encryption to an specific version / method.

ejjoman ( 2014-06-16 11:28:17 +0300 )edit

I also had all the above-mentioned problems. My solution is, I do not use the mobile data connection at all. Only when it is really necessary. And when i do so, it is necessary to reboot, no other solution. A long time ago i was programming in basic. I supose that in Sailfish OS there is the possibility to programming choises as;" if there is wifi choose wifi and only wifi" if there is "no wifi and only than chose 3G ore 4G"? I suppose that for a developer it can not be so difficult to make a similar programline? I hope that finally, the solution will be available in the next update?

MarcG ( 2014-06-25 23:40:15 +0300 )edit

yes, loaded dd-wrt on all 3 three AP's with completly identical wireless settings (N-only and WPA2 aes encryption). no more issues now

dash72 ( 2014-07-08 18:17:28 +0300 )edit
4

answered 2014-06-13 11:17:22 +0300

alci gravatar image

Here is my use case on a 24h cycle:

  • home
    • open Wifi (no security at all, except I'm in the middle of nowhere)
    • no mobile network
  • from home to work
    • alternate from 2G, to 3G, to 2G, to no network, to 3G
  • at work
    • 3G
    • WPA-PSK wifi

What happens is that after a work / home / work commuting, mobile data connextion is lost, I have to reboot. My question is: how could I get some logs from connman / ofono I could activate for one or two days to have more information ?

edit flag offensive delete publish link more

Comments

With the phone in developer mode install the connman-tracing package.

Aaron McCarthy ( 2014-06-16 04:48:51 +0300 )edit
12

answered 2014-06-13 11:24:52 +0300

sremes gravatar image

It seems that when both wifi and mobile data are enabled, the device is connected to both of them (ifconfig shows two IP addresses, wlan0 and rmnet0). Testing which connection is actually used, I downloaded a file, and it seemed to use mobile data for that (again checking ifconfig for RX/TX bytes line). Tried toggling the wifi, but the phone still prefers to use mobile data instead of wifi. The WLAN here is not encrypted (no WPA).

edit flag offensive delete publish link more

Comments

I also noticed that with both WLAN and MOBILE enabled, there was no way to use WLAN.

magullo ( 2014-06-13 11:50:30 +0300 )edit
1

Found out the same problem, it seems that only the default route to rmnet0 (mobile network) is preserved, but IP address from the WLAN is also retrieved. I know this may be too advanced, but what about having different routing tables for each connection (mobile, WLAN) etc. and then using policy routing, firewall marking for directing the traffic to correct pipe?

Karri Huhtanen ( 2014-06-13 19:52:14 +0300 )edit

It is not advanced, you just need to set different metric to the route based on interface type. This is pretty basic setup. No need to play with firewall or anything complicated. But have no idea how to do it in connman (yet).

miska ( 2014-06-13 23:53:18 +0300 )edit

my phone acts just fine. it uses wlan, mobile data is enabled with good signal strength but no connection established(ifconfig shows only loopback lo and wlan0).

nightmare ( 2014-06-14 00:40:14 +0300 )edit
2

It's a bug in connman that sometimes setting default route to the wifi connection doesn't always work.

llornkcor ( 2014-06-14 11:13:20 +0300 )edit
6

answered 2014-06-13 12:32:09 +0300

2Ti gravatar image

I haven't so far had any other problems with the hotfix, other than connecting to my university's eduroam WiFi network. It would be fantastic if the eduroam/enterprise WiFi connection problems could be fixed.

There is a full list of settings for the Sussex eduroam instance here. Please let me know if there are any logs etc. I can provide to help in getting this fixed.

edit flag offensive delete publish link more

Comments

Same experience here. My Jolla fails to connect to most enterprise wifi networks. I always get "Sorry. Could not connect to selected network. Search again", when trying to any network that requires a user name and password log in or certificate.

My home wifi has always been very stable. It acts just like before with the patch. Automatically connects when I get home and switches to mobile when I leave. No problems there. My wifi and mobile is always on. When I am at home it always use wifi.

AbyZThomas ( 2014-06-13 16:41:50 +0300 )edit

Do you use username@sussex.ac.uk as your username (Identity in conf.)? Also you need retrieve ("Thawte Premium Server CA") certificate in a file, place it to for example /etc/ssl -directory and direct CACertFile mentioned in https://together.jolla.com/question/315/wpa-8021x-enteprise-others-wifi-support-needed-workaround/ to that file. That should do it, according to those Sussex instructions. However, beware that Jolla does not really support WPA2 Enterprise properly, wish it did.

Karri Huhtanen ( 2014-06-13 20:00:18 +0300 )edit

I do use that identity. I did not have the certificate file installed before as the connection worked with the default ca-bundle.crt, I installed it now however, but the connection still does not work. The error I get in the wpa_supplicant log is

err='Server used client certificate'

I noticed that Sussex also supports TTLS-MSCHAPv2, TTLS-MSCHAP and TTLS-PAP, tried all of those but the error is always the same. I'm guessing this is the same issue as here?

2Ti ( 2014-06-18 12:55:47 +0300 )edit
0

answered 2014-06-13 13:12:31 +0300

Morpog gravatar image

Not sure if it's related to the hotfix or update 7.

Automatic sync of my imap email account doesn't work anymore. When I refresh manually new mails show up.

edit flag offensive delete publish link more

Comments

My phone overheats, with peak CPU usage and battery drains... don't know if this is about the hotfix.

dmelamet ( 2014-06-14 21:15:16 +0300 )edit
2

answered 2014-06-13 16:31:12 +0300

I am currently not in the environment where I had problem with the WLAN. At my parents home there are two access points, one FritzBox and one TP-Link AC. There I lost connections regularly.

At my home, with only one WLAN access point, I never had these problems.

But yesterday (with 1.0.7.16) my mobile connection was gone. It was greyed out and there was no way to activate it. It was set to auto discovery and the ComboBox below showed the appropriate provider. I tried to set the mobile provider manually, but it did not find anything. Today I installed hotfix (1.0.7.18). After the restart the mobile network was still not available, but now it was possible to choose the provider manually, what fixed the problem and mobile network is back.

edit flag offensive delete publish link more

Comments

1

Hi, I have the problem with loose of mobile provider, too. Once it is lost only a reboot brings the phone back online. Here is the relevant log from journalctrl pastebin journalctrl

harry ( 2014-06-13 16:51:10 +0300 )edit
1

I also have this issue, sometimes switching between "2G only" and the other options helps. If remeber correctly, this never happened in 2G only mode, but I may be wrong.

schmittlauch ( 2014-06-18 00:25:12 +0300 )edit

If I use "3g preferred" everything works stable. But If I use "4g preferred" the mobile internet is not usable. It stops working after 30seconds and can only be reset by a reboot. My mobile provider has 4g support but I have to pay for it. So it is not enabled with my current data plan. Maybe this causes problems.

harry ( 2014-06-24 11:53:04 +0300 )edit

I now used manual Network selection and prefer 2G for a while. And it works without any problem. Will try and observe it with 3G only mode.

Buschmann ( 2014-07-07 14:04:03 +0300 )edit
2

answered 2014-06-13 23:19:25 +0300

Tomasz gravatar image

Both before and after the update Jolla does not see my network shared with the laptop. This network is the type IBSS, and checking from Jolla tool 'iw' network is seen. The network is unhidden, unsecured and has its own DHCP, other devices connect to it properly. Below result from tool for this network:

[root@dhcppc9 nemo]# iw dev wlan0 scan
BSS 4e:55:92:1d:e1:96 (on wlan0)
        TSF: 1657059766 usec (0d, 00:27:37)
        freq: 2412
        beacon interval: 100
        capability: IBSS (0x0002)
        signal: -37.00 dBm
        last seen: 0 ms ago
        SSID: MyWlan
        Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
        DS Parameter set: channel 1
        ERP: <no flags>
        Extended supported rates: 6.0 9.0 12.0 48.0
        ...

Would it be a chance to turn on the visibility and the ability to connect to this type of network?

edit flag offensive delete publish link more

Comments

1

I do not understand why developers connman turned off the connection to the Ad-Hoc (IBSS) networks. I have not found anywhere clear justification of the decision. I found that the change was introduced this simple commit:

https://gitorious.org/connman/vudentz-clone/commit/cd9d9e6

So maybe the developers SailfishOS could try to rebuild connman without this change. I use Ad-Hoc network with a DHCP server and other devices connect properly. The combination with Ad-Hoc network with DHCP is similar to the AP network and it does not require manual configuration of the connection so it would not be necessary to add such options. My card does not support AP mode, so I must use Ad-Hoc.

Tomasz ( 2014-06-18 19:33:21 +0300 )edit
0

answered 2014-06-14 00:24:23 +0300

mornfall gravatar image

No dice. Wlan (mixed-mode n/g with WPA1+WPA2) still has the same tendency to crash and/or fail to reconnect. Reloading wlan.ko and restarting connman seems to help, but before the hotfix I didn't have to do that, usually disabling/enabling wlan did the trick. Unfortunately, connman is a very opaque piece of software (and it plays tricks with wpa_supplicant just to make matters worse), so I didn't manage to extract any useful info.

edit flag offensive delete publish link more

Comments

By default connman does no logging, as it can be verbose. You'll need to use devel mode and install connman-tracing and connectionagent-qt5-tracing packages from the connmandline.

All the logging will go to journal.

llornkcor ( 2014-06-16 22:52:17 +0300 )edit

Question tools

Follow
33 followers

Stats

Asked: 2014-06-09 16:06:07 +0300

Seen: 9,749 times

Last updated: Sep 21 '14