Hi, On 7 September 2010 15:43, David Woodhouse <[email protected]> wrote: >> this is exactly what we used as a solution. In the release notes of >> connman 0.57 I found the hint that 0.57 should fix the bug >> http://bugs.meego.com/show_bug.cgi?id=4818 ... after all it does not >> fix the bug but at least it gave me the right idea. I've patched >> connman's resolver.c to not add "options edns0" to rsolv.conf and this >> fixed it. Now all issues with these special WiFi routers disappered. >> >> I guess this patch should also be added to upstream connman? > > Of course it shouldn't. By disabling EDNS0, you've simply confirmed that > your local network equipment is broken. Now it's up to you to get it > fixed. > > If both EDNS0 and TCP support are broken (and with ConnMan, the latter > definitely is), there will be some DNS records that you simply *cannot* > fetch. > > And please don't top-post. You make it extremely hard to follow the > conversation when you don't use email properly. > > ConnMan should probably have some logic to detect that it's working with > a broken nameserver, and fall back to not using EDNS0. Such logic does > exist in bind already. If/when this happens, we should complain *loudly* > and ensure that the user reports the fault to their network provider.
Again... sorry for the top post. So maybe the network equipment is broken (I agree) but after all users that own such a broken router (and from what I can tell there should be a lot of them at least in germany) should be able to use the internet just like all the others (and it should not happen that the connection manger's GUI tells him he's online but the browser tells him it cannot resolve any of the hostnames he'd like to visit). Furthermore as Windows machines (and also NetworkManager based Linux ditros) work just fine with these routers users of connman based machines might prefer to switch away from connman instead of buying a new router or bugging the vendor of the router to fix the firmware. I.e. the unexperienced user might consider this a connman bug and not a router bug as his windows machine can resolve the hostnames when it claims that it's online. So up to now our solution to this problem is to remove EDNS0 support from resolv.conf. And yes... I agree that connman should detect these kind of routers and not use EDNS0 if the router does not support it properly. Bye, Toby _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
