asked 2016-05-07 15:04:40 +0200
My mother has an internet box which is connected to an Apple Airport Express wireless access point. My wife has no internet problem with her Nexus 5, the 2 PCs here (one on Ubuntu and one on Fedora) have no internet problem too. With the Jolla, I just can't have any internet traffic, settings applet says "Limited connectivity".
Any idea?
answered 2016-05-30 08:04:38 +0200
It indeed is a bug and it has nothing to do with your AP. It is plain and simple: The Jolla phone often does not write a proper DNS configuration to /etc/resolv.conf. I always have to add my DNS server IP address manually. Connman only writes 127.0.0.1 and ::1 to the file but not the address provided by the DHCP service. Also reenabling the connection or restarting the device does NOT work. Oh and airplane mode too...
can you provide more about this bug? is this already known/tracked at jolla / connman?
as it seems to / could be the root cause for the behavior i described here: https://together.jolla.com/question/127076/dns-lookup-fails-was-doesnt-fall-back-to-ipv4/ (sorry, it became a markup mess :/ )
dmnk ( 2016-06-06 11:09:25 +0200 )editI really don't know much about it. What i know is that connman changes resolv.conf when there is a change in connectivity. Yet i do not know why localhost has to be in there at all. it's not like the Jolla has a working DNS service installed that could probably reply. On 3G all is fine but if i change back to my home wifi, only 127.0.0.1 and its IPv6 equivalent are in resolv.conf. For now i "solved" the issue by putting in a few of the opennic public servers and making the file immutable, so connman can not change it. This works 100% but is not really a solution i'd like to install permanently. If it helps: My DHCP and router is a PC running arch Linux and the DNS server provided by the DHCP is not within the scope of my home network, which uses private class B IPv4(172.23.0.0/16) and no IPv6.
Shoppinguin ( 2016-06-07 23:14:47 +0200 )edit@fishegg: You need to have developer mode on. In fingerterm, you need to become root by entering "devel-su" and your password. then use vi or nano to add a line like "nameserver "ip address of your DNS server"" to the top of /etc/resolv.conf. Then make the file immutable "chattr +i /etc/resolv.conf". This should fix it for the time until it is officially fixed. @dmnk: I'd go as far as calling this question a possible duplicate to yours.
Shoppinguin ( 2016-06-08 10:14:02 +0200 )editanswered 2016-05-08 16:24:59 +0200
ping 8.8.8.8)nslookup slashdot.org, or use ping)In my case, connman gets confused by some wireless network setups' nameservers (e.g.: when moving from/to the eduroam WiFi at the universities where I work) and is unable to correctly resolve DNS names (though direct IP connections still work).
Either restarting the connection (GUI : enter Airplane mode, then resume normal network), or restarting connman (devel-su systemctl restart connman.server) fixes my problems.
correction for restarting connection: devel-su systemctl restart connman.service not server
Asked: 2016-05-07 15:04:40 +0200
Seen: 671 times
Last updated: May 30 '16
Just a guess - If I remember right Apple Airport supports 802.11 ac. Is the Airport router only configured to allow wifi only on that? Jolla Phone 1 wifi supports Wi-Fi on 802.11 b/g/n
sifartech ( 2016-05-07 15:19:23 +0200 )editThanks, that could be an idea. But in such a case, why I can connect the wifi network?
romu70 ( 2016-05-08 21:17:43 +0200 )editGood point. Sorry, no idea.
sifartech ( 2016-05-08 23:48:11 +0200 )edit