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

(solved) WiFi is not working correctly since 1.0.8.19 [answered]

asked 2014-07-17 15:42:05 +0300

Badevil gravatar image

updated 2014-07-22 10:03:19 +0300

jiit gravatar image

Hi together,

since the last update I could freaking out my WiFi was working well before. Now I was also looking for other topics with a similar problem and I also found a few but with a different problem. My phone connects without any issues with the WiFi but that it gets the exclamation mark or for US people exclamation point. The funny thing is that the Browser is working fine as well as SSH which is strange because all other apps like Mitäkuuluu, Jolla store, Warehouse, Sailbox... also Android apps are not working.

Does someone has an Idea?


[nemo@Jolla ~]$ tail -F /var/log/wpa_supplicant.log
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked
rfkill: WLAN unblocked

[root@Jolla nemo]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: rmnet0: <> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/[530]
3: rmnet1: <> mtu 2000 qdisc noop state DOWN qlen 1000
    link/[530]
4: rmnet2: <> mtu 2000 qdisc noop state DOWN qlen 1000
    link/[530]
5: rmnet3: <> mtu 2000 qdisc noop state DOWN qlen 1000
    link/[530]
6: rmnet4: <> mtu 2000 qdisc noop state DOWN qlen 1000
    link/[530]
7: rmnet5: <> mtu 2000 qdisc noop state DOWN qlen 1000
    link/[530]
8: rmnet6: <> mtu 2000 qdisc noop state DOWN qlen 1000
    link/[530]
9: rmnet7: <> mtu 2000 qdisc noop state DOWN qlen 1000
    link/[530]
10: sit0: <NOARP> mtu 1480 qdisc noop state DOWN
    link/sit 0.0.0.0 brd 0.0.0.0
11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 100
    link/ether 50:56:a8:XX:XX:XX brd ff:ff:ff:ff:ff:ff
    inet XXX.XX.X.XXX/XX brd XXX.XX.XXX.XXX scope global wlan0
    inet6 fe80::5XXX:a8XX:fXX1:2XX7/64 scope link
       valid_lft forever preferred_lft forever
12: p2p0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 100
    link/ether 50:56:a8:XX:XX:XX brd ff:ff:ff:ff:ff:ff

[root@Jolla nemo]# ip route
default via XXX.XX.XXX.XXX dev wlan0
XXX.XX.X.X/XX dev wlan0  proto kernel  scope link  src XXX.XX.X.XXX
XXX.XX.XXX.XXX dev wlan0  scope link

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Badevil
close date 2014-07-21 19:10:55.614317

Comments

is ping working? what about dns?

rod ( 2014-07-17 18:16:53 +0300 )edit

As I wrote Browser is working fine, so DNS is working and as I can connect to my phone ICMP as well. To prove both here is a ICMP to google.de:

[root@Jolla nemo]# ping google.de
PING google.de (173.194.113.55) 56(84) bytes of data.
64 bytes from fra02s20-in-f23.1e100.net (173.194.113.55): icmp_req=1 ttl=56 time=21.9 ms
64 bytes from fra02s20-in-f23.1e100.net (173.194.113.55): icmp_req=2 ttl=56 time=34.6 ms
64 bytes from fra02s20-in-f23.1e100.net (173.194.113.55): icmp_req=3 ttl=56 time=36.1 ms
64 bytes from fra02s20-in-f23.1e100.net (173.194.113.55): icmp_req=4 ttl=56 time=38.9 ms
^C
--- google.de ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 21.974/32.939/38.975/6.521 ms
Badevil ( 2014-07-17 21:57:18 +0300 )edit

2 Answers

Sort by » oldest newest most voted
1

answered 2014-07-17 22:19:00 +0300

tigeli gravatar image

updated 2014-07-19 13:42:02 +0300

Can I get the output for the following command:

curl -D - http://ipv4.jolla.com/return_204

It should return "HTTP/1.1 204 No Content" if succesful.

EDIT: setting the proxy setting in the wlan-service settings to "No proxy" resolved the issue.

edit flag offensive delete publish link more

Comments

Of curse you can :-)

[root@Jolla nemo]# curl -D - http://ipv4.jolla.com/return_204
HTTP/1.1 204 No Content
Date: Thu, 17 Jul 2014 19:35:17 GMT
Server: nginx
X-Cache: MISS from Psycho-efw.localdomain
X-Cache-Lookup: MISS from Psycho-efw.localdomain:8080
Via: 1.1 Psycho-efw.localdomain (squid/3.3.8)
Connection: keep-alive
Badevil ( 2014-07-17 22:36:21 +0300 )edit

@Badevil Ok, the output seems valid.

To really see what's going on I would need you to install connman-tracing-package as root with

pkcon install connman-tracing
reboot

Connect to the wlan if not already connected and wait for 1 min. Then run following command to get the tracing log (as root):

journalctl -b > debug.log

Let the command finish and send the log file (debug.log) to tigeli at jolla.com.

After the logging you can remove the connman-tracing with

pkcon remove connman-tracing
tigeli ( 2014-07-17 23:35:08 +0300 )edit

@tigeli mail is out.

Badevil ( 2014-07-18 11:21:52 +0300 )edit

@barevil

Here are the lines from the debug.log which matter the most:

--cut--

Jul 18 10:14:47 Jolla connmand[779]: src/proxy.c:connman_proxy_driver_lookup_notify() service 0x3398d0 url http://ipv4.jolla.com/return_204 result PROXY 1.2.3.4:8080; DIRECT

Jul 18 10:14:47 Jolla connmand[779]: src/wispr.c:proxy_callback() proxy PROXY 1.2.3.4:8080; DIRECT

Jul 18 10:14:47 Jolla connmand[779]: src/wispr.c:connman_wispr_message_init()

Jul 18 10:14:47 Jolla connmand[779]: src/wispr.c:wispr_portal_request_portal()

Jul 18 10:14:47 Jolla connmand[779]: src/service.c:connman_service_unref_debug() 0x3398d0 ref 4 by src/proxy.c:49:remove_lookup()

Jul 18 10:14:47 Jolla connmand[779]: src/service.c:connman_service_unref_debug() 0x3398d0 ref 3 by plugins/pacrunner.c:362:request_lookup_reply()

Jul 18 10:14:47 Jolla connmand[779]: src/wispr.c:wispr_portal_web_result()

Jul 18 10:14:47 Jolla connmand[779]: src/wispr.c:wispr_portal_web_result() status: 404

Jul 18 10:14:47 Jolla connmand[779]: src/service.c:__connman_service_online_check_failed() service 0x3398d0 type 1 count 7

Jul 18 10:14:47 Jolla connmand[779]: src/service.c:connman_service_ref_debug() 0x3398d0 ref 4 by src/service.c:6153:__connman_service_online_check_failed()

--cut--

It seems that you have proxy defined for the particular wlan service (1.2.3.4:8080) and connman will do the online check through the proxy. The proxy returns HTTP status code 404 instead of returning 204. You would need to check the proxy-service why it is returning 404 for this request.

tigeli ( 2014-07-18 11:43:59 +0300 )edit

@tigeli yes I have a proxy, but for the WiFi it is a transparent one, because not every device accept a proxy. The Proxy itself is acting fine Jolla should not ask for the proxy settings, of curse they are available but not needed. Before the update it was no problem and usually my phone should think it is directly connected to the internet... I also can not see any proxy hit beside of the GET request for be proxy.pac. When I open the browser I see the hits but not the online check. Could it be that the browser is configured for direct access as it should and all other apps try to use the "proxy settings"? As I wrote before its a transparent one, do not ask for and handle each request as direct connected. I have many devices connected which are working fine. There is still something fishy with this phone. Where can I configure the proxy settings/behaviour on my Jolla to avoid this?

Badevil ( 2014-07-18 13:30:43 +0300 )edit
0

answered 2014-07-21 15:51:33 +0300

Spock112 gravatar image

Hi,

in my configuration all WiFi's were set to "No Proxy" and my problems where solved - at least partial - by setting it to "automatic".

edit flag offensive delete publish link more

Question tools

Follow
2 followers

Stats

Asked: 2014-07-17 15:42:05 +0300

Seen: 1,303 times

Last updated: Jul 21 '14