Am Freitag 19 Oktober 2007 schrieb Sahaja Talla: > Hello Marcel, Christian and All, > > (I posted this on the forum, but due to urgency of my project delivery, I > am also mailing this to you hoping to get your attention sooner) > I wrote a syncml obex client using tcpobex for transport; This client can > communicate with a local obex server; As I could see both are using ipv6. > However it can't connect with the SCTS OBEX server on different machine > which has windows and SCTS Server running; I suspect SCTS OBEX server is > using ipv6. I noticed that openobex(tcpobex) doesn't let you use IP > version4, even though the documentation says otherwise; If you attempt to > used ipv4, it resets all the parameter back to ipv6 in case of client; And > in case of server it server registration fails when ipv4 is used. Is ipv4 > really supported and tested?
If you use the CVS version of OpenOBEX and use the TcpOBEX_* functions there, IPv6 connectivity should work. Those function rely on a dual-IP stack in the OS. For Linux, the IPv4-mapped addresses work, meaning that IPv4 can be used but appear to the application as IPv6 connection. This has the advantage that only IPv6 must be supported but IPv4 is still usable. For usage on Windows, you may try my personal SVN repository which has additional patches for win32 support. However, Windows XP does not have a dual-IP stack and thus OpenOBEX is limited to IPv6 there. On Windows Vista (with its dual-IP stack), IPv4 should also work if you set the IPV6_V6ONLY socket option to 0 (use in conjunction with OBEX_GetFD()). HS ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Openobex-users mailing list [email protected] http://lists.sourceforge.net/lists/listinfo/openobex-users
