Hi Daniel, On Fri, 30 Mar 2012 15:13:34 +0200 Daniel Wagner <[email protected]> wrote:
> On 28.03.2012 20:35, Mario Domenech Goulart wrote: >> Here's the ConnMan log generated right after booting the system: >> http://paste.debian.net/161265/ >> >> Here's the rest of the log, obtained after setting the configuration >> to be obtained via DHCP: http://paste.debian.net/161266/ > > I looked into the logs and I could not find an obvious problem. > > The state machine does not want to start DHCP because nobody is telling > the state maschine to do it. There is a missing plugins/ethernet: > cable_connect() which eventually lead to a proper DHCP discovering. > > Looking a bit more into the details, it seems that the auto connect part > is also missing. There is no __connman_service_auto_connect() in the > log. I have yet figured why this is so. Thanks for looking at it. I think I could produce a (hopefully) simpler case. Here are the scenario/steps: 1. connmand is not running. The content of /var/lib/connman/settings is [global] OfflineMode=false [WiFi] Enable=false [Bluetooth] Enable=false [Wired] Enable=true [Cellular] Enable=false [WiMAX] Enable=false The content of /var/lib/connman/ethernet_0024ee0039c1_cable/settings is [ethernet_0024ee0039c1_cable] Name=Wired Modified=2012-03-30T10:21:00.867129Z IPv4.method=dhcp IPv4.DHCP.LastAddress=10.2.254.39 IPv6.method=auto IPv6.privacy=disabled IPv4.netmask_prefixlen=24 IPv4.local_address=10.2.254.39 IPv4.gateway=10.2.254.254 Nameservers=192.168.254.254; 2. I start connmand with "connmand -n -d &> connman.log". 3. I wait for some seconds and check if the interface has been configured. 4. The interface has not been configured (checked with ifconfig). 5. I stop connmand with ^C. 6. The full log is http://paste.debian.net/161454/ If I repeat those steps, but explicitly set the network interface to get configuration via DHCP while connmand is running, it works. However, it seems that connmand is not picking the previous configuration upon starting up. While executing the steps above, I noticed that the AutoConnect property for that interface was `false', so I restarted connmand and: 1. with the network interface without configuration, tried to set AutoConnect to true. Got a net.connman.Error.InvalidService error 2. explicitly set the interface to be configured via DHCP. The interface gets proper configuration. 3. retried setting the AutoConnect property to true. This time it works. 4. shutdown connmand via ^C and got a segfault: http://paste.debian.net/161470/ 5. next time I start connmand again, the AutoConnect property is set to false. Maybe the AutoConnect property being false explains why the interface is not automatically configured when connmand is started? Why does connmand crash when I set AutoConnect to true? Shouldn't I do that? Best wishes. Mario -- http://parenteses.org/mario _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
