Hi, Marcel

Marcel Holtmann wrote:
> Hi Jiajia,
> 
>>>> I still have problem with DHCP on my machine. It can not get IP
>>>> address automatically for Ethernet interface or WiFi interface.
>>>> Below are my detailed steps. And I attached the output log of
>>>> ConnMan deamon. 
>>>> 1. reboot machine (ConnMan is not running)
>>>> ---> My Ethernet interface got its IP address.
>>>> 2. ps -ef | grep Net
>>>> root      4676     1  0 09:41 ?        00:00:00
>>>> /usr/sbin/NetworkManager --pid-file
>>>> /var/run/NetworkManager/NetworkManager.pid
>>>> root      4690     1  0 09:41 ?        00:00:00
>>>> /usr/sbin/NetworkManagerDispatcher --pid-file
>>>> /var/run/NetworkManager/NetworkManagerDispatcher.pid
>>>> root      5499  5479  0 09:42 tty1     00:00:00 grep Net
>>>> 3. kill NetworkManager (kill -9 4676; kill -9 4690)
>>>> 4. ps -ef | grep dh
>>>> root      5140     1  0 09:41 ?        00:00:00 /usr/sbin/dhcdbd
>>>> --system dhcp      5372  5140  0 09:41 ?        00:00:00
>>>> /sbin/dhclient -1 -lf /var/lib/dhcp3/dhclient.eth0.leases -pf
>>>> /var/run/dhclient.eth0.pid -q -e dhc_dbus=31 -d eth0
>>>> root      5509  5479  0 09:43 tty1     00:00:00 grep dh
>>>> 5. kill dhcdbd and dhclient (kill -9 5140; kill -9 5372)
>>>> 6. reload e1000 module (modprobe -r e1000; modprobe e1000)
>>>> ---> Ethernet interface is up, without IP address
>>>> 7. start ConnMan deamon (connmand -d -n)
>>>> 8. ps -ef | grep dh
>>>> dhcp      5553  5552  0 09:45 tty1     00:00:00 /sbin/dhclient -d
>>>> -q -n -e BUSNAME=org.moblin.connman -pf
>>>> /usr/local/var/run/connman/dhclient.eth0.pid -lf
>>>> /usr/local/var/run/connman/dhclient.eth0.leases -cf
>>>> /usr/local/lib/connman/scripts/dhclient.conf -sf
>>>> /usr/local/lib/connman/scripts/dhclient-script eth0
>>>> 9. wait for more then 10 minutes
>>>> ---> still did not get IP address for eth0
>>>> 10. stop ConnMan deamon.
>>> 
>>> so I was looking through your log file. First thing that is
>>> suspicious is this one: 
>>> 
>>> connmand[5552]: bluetooth.c:adapters_reply()
>>> connmand[5552]: Argument 0 is specified to be of type "array", but
>>> is actually of type "string" 
>>> 
>>> What kind of BlueZ version do you have running? It could be
>>> nothing, but it might affect the D-Bus interaction.
>>> 
>> 
>> It is bluez-4.17. actually, I do not have a bluetooth device on my
>> machine. 
> 
> that doesn't really explain it. However we did fix some bugs there so
> updating to the latest bluez-4.24 might help this.
> 

I could try to update to bluez-4.24.

>>> connmand[5552]: dhclient.c:dhclient_probe() element 0x805ee18 name
>>> dhcp connmand[5552]: dhclient.c:dhclient_probe() request eth0
>>> connmand[5553]: dhclient.c:task_setup() task 0x805b690 name eth0
>>> connmand[5552]: dhclient.c:dhclient_probe() executed /sbin/dhclient
>>> with pid 5553 
>>> 
>>> So the dhclient program gets executed, but it seems it never really
>>> runs since at least not from the log.
>>> 
>>> Can you check that /usr/local/lib/connman/scripts/dhclient-script
>>> does exists, because that script does the interaction with connmand.
>>> 
>> yes, it is there.
>> -rw-r--r-- 1 root root   137 2008-12-24 09:14 dhclient.conf
>> -rwxr-xr-x 1 root root 10355 2008-12-24 09:14 dhclient-script
> 
> That looks right.
> 
>>> Can you use the instructions from HACKING document and check if
>>> using bootstrap-configure and running from the source directory
>>> without installing it works. 
>>> 
>>> 
>> I was running from the source directory, using "./src/connmand -d
>> -n". 
>> previously, I used the below steps to build ConnMan:
>>      ./bootstrap-configure ./configure
>>      make
>>      make install
>> However, when I tried to use "./configure --enable-maintainer-mode"
>> just now, I met error in "make". I attached the log to the mail,
>> please take a look. thanks.  
> 
> generating symbol list for `loopback.la'
> /usr/bin/nm -B  .libs/loopback.o  |  | /bin/sed 's/.* //' | sort |
> uniq 
>> .libs/loopback.exp
> ../libtool: eval: line 4352: syntax error near unexpected token `|'
> ../libtool: eval: line 4352: `/usr/bin/nm -B  .libs/loopback.o  |
>> /bin/sed 's/.* //' | sort | uniq > .libs/loopback.exp'
> make[2]: *** [loopback.la] Error 1
> make[2]: Leaving directory `/home/zjj/connman/plugins'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/zjj/connman'
> make: *** [all] Error 2
> 
> I have seen that before, but I have no idea why that happens. What
> distro are you using. I had some issues on Fedora 10. It seems to be
> only present with maintainer mode, but on Ubuntu that is not a
> problem. 
> 
Yes, it only present with maintainer mode. But I am using Ubuntu 7.10. :(
Do I really need to "enable maintainer mode"? If not, I won't try on it now.

Thanks,
jiajia_______________________________________________
connman mailing list
[email protected]
https://lists.moblin.org/mailman/listinfo/connman

Reply via email to