Hi everybody,
I remember that there was somebody on the mailinglist some time ago that had
problems with a device that did not work with the standard IP addresses of
169.254.2.1 (device) and 169.254.2.2 (host), but with 169.254.2.118 (device)
and 169.254.2.117 (host).
I remember that for Mark it worked after he supplied these addresses to odccm.
Somebody was asking some questions on my website about getting synce to run on
his computer with his Moto-Q device. He was also seeing the same problem that
his device was using 169.254.2.118. This means that odccm is not able to
communicate with the device, meaning all the other things won't work.
My question is now why currently we are using the static, hardcoded IP
addresses and not making use of the fact that the device contains some
elementary DHCP server that will provide the computer with the right address
when it queries for one?
Would it be possible to change odccm to make use of DHCP instead, and if so,
who has some knowledge that is sufficient to implement this?? :) The problem
is that is just a bit too high for me to implement ;)
Furthermore, I think that the same problem holds for hal-dccm, since I also
see hardcoded information in the SVN tree.
My guess is that it will cause quite some problems for end-users when they see
that their device is not working and it turns out to be because of this.
Anybody some further ideas?
Guido
--
Aviation is proof that given the will, we have the
capacity to achieve the impossible.
--Eddie Rickenbacker
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
