I'm in the process of developing a Yocto-based embedded solution (Wi-Fi only, similar to Raspberry Pi Zero W) with connman as the network manager. This solution needs to pass Apple's Bonjour Conformance Tests, and I've been having some difficulties getting the current version (1.38) of connman to pass.
I've set the AddressConflictDetection option to true in connman's main.conf which helps me get through most of the IPv4LL tests, but the hot-plug tests (where you have to force the Wi-Fi interface to disassociate from the AP) are failing.
Two small fixes found while ramping up again...
Daniel Wagner (2):
vpn: Send D-Bus response when connecting for daemon-less setups
session: Fix state initializiation
src/session.c | 2 +-
vpn/plugins/vpn.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
We have a product that we are selling that uses the Beaglebone Black SBC with Debian Jessie as a small network appliance in a residential environment. Connman is the network manager in this distribution. We are experiencing a very random issue where occasionally the DNS servers being returned by a network DHCP server get corrupted. All other configurations are fine - IP address, gateway, etc. When this happens, the unit still has local network connection but loses the connection to the Internet (as you would expect). This impacts the operation of the unit in a very negative manner. We have a user interface that shows the configuration settings and when the Primary DNS server gets corrupted, the user interface field normally shows the DNS server as " [ ". The Secondary DNS server is mostly blank when this happens. Manually changing the Primary DNS Server to a good nameserver always resolves the issue.
It happens often enough that it's annoying us because of the support calls we get, but it happens so infrequently that it's very difficult to reproduce. In fact, I've never seen it on my test units - I've only seen it on units installed in the field.
In almost all applications, the network appliance is connected directly to the local network router provided by the ISP or the user. We believe that something happens from the router that causes this issue (and it could even be with specific routers - we just don't know). In one particular instance, a unit had been working for several months just fine, but then there was a power outage, and after rebooting from the power outage, the Primary DNS was showing the " [ " and the Secondary DNS was blank, and we had to manually enter a good nameserver.
Since it's so hard to reproduce, I'm looking at some bandaid approaches using some scripts. But, before I did that, I thought I'd check to see if connman might have some options that I could use to resolve the issue. One potentially available option I was reading about was the use of the nodnsproxy option. This one might be extremely hard to determine if it has resolved the issue or not, as it is so hard to reproduce but would be simple to implement, if it were a potential solution. This would assume that DNS proxy feature in connman was in conflict with the external DNS server, as I was reading, which might be a real stretch.
A second option I was looking at was the "FallbackNameservers" option. However, I don't understand how this works. Does connman do a test to verify Internet connection or proper DNS operation, and if it fails that test, it "falls back" to a secondary DNS server and then if that also fails, it falls back to the "FallbackNameservers"? If this is how this works, this is a possibility to explore - I would try setting the FallBack servers to available DNS servers such as the Google nameserver at 18.104.22.168.
By the way, the connman version on my Debian distribution is V1.32. I see that connman is up to at least 1.37. Is it possible that upgrading connman might resolve this issue?
I apologize - I'm comfortable with simple networking but I'm by no means a networking expert and I'm really hoping for a sanctioned option to resolve this issue.
Any guidance would be appreciated.
DOn't know if this is the right place or not, but since moving to connman,
I have noticed that the ipv6 test page is down. the ipv4 one works fine,
but I get a mention in the log:
"connmand: Failed to find URL:
If I try to get to it from a browser, I get a '502 bad gateway error'
If I use curl on the cli, I get this:
# curl ipv4.connman.net/online/status.html
# curl ipv6.connman.net/online/status.html
<head><title>502 Bad Gateway</title></head>
<center><h1>502 Bad Gateway</h1></center>
I think something is not set right on the server...