Tizen WebSockets: can access Internet WebSocket server but cannot acces LAN WebSocket server
<p>last week I started to develop apps for a Samsung Smartwatch with the Tizen SDK 2.4.0. My sample web application connects to a remote Websocket server (a simple echo server) and sends some random requests and prints the received messages (Server is <a href="http://www.websocket.org/echo.html" rel="nofollow">http://www.websocket.org/echo.html</a>). This works fine on an emulated devices as well as on the real Gear S2 Smartwatch (Example was taken from <a href="https://developer.tizen.org/zh-hans/development/tutorials/web-application/w3chtml5supplementary-features/communication/websocket?langredirect=1" rel="nofollow">https://developer.tizen.org/zh-hans/development/tutorials/web-application/w3chtml5supplementary-features/communication/websocket?langredirect=1</a>)</p>

<p>But as soon as I start a Websocket server in my home LAN I run into problems. The server is launched via a simple Python example I found on Github (<a href="https://github.com/dpallot/simple-websocket-server" rel="nofollow">https://github.com/dpallot/simple-websocket-server</a>). The emulator device from the SDK connects to this server without any problems using the local IPv4. But the real device, which is logged in to the same WiFi access point, doesn't. </p>

<p>Note that the connection between my PC and my watch device works fine, since the SDK flashes the developed apps via WiFi to the device. </p>

<p>In my config.xml all connections are allowed </p>

<pre><code>&lt;access origin="*" subdomains="true"&gt;&lt;/access&gt;
</code></pre>

<p>and the privilege for "Internet" is available. </p>

<p>The logs show that the watch tries to open a connection, but is then stuck. No error message is printed - the watch just does not go beyond the initial creation of the websocket.</p>

<p>Do you have any hints or thoughts about how I could debug this issue? 
Thanks in advance!</p>