sOn Mon, 2010-09-06 at 17:50 +0200, Tobias Schröpf 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. -- dwmw2 _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
