Calibre can support one device connection at a time (any device, not just a wireless device). Neither the client nor the server are stateless. After connecting, the client (the device) is passive, waiting for calibre to tell it what to do. The wireless device is a private application protocol based on JSON. The server can support multiple clients connecting at the same time. The client asks the server to do things for it. The content server is a "pure" HTTP connection, where the client has control. However, at the application level the two are completely different. Both make TCP connections to a listening calibre server. Up through the TCP layer there isn't any significant difference. What are the networking differences between the connection types? It would be nice to get the wireless device connection working. Other than these I don't know what else to suggest. Some linux users have reported that linux thinks that calibre is doing a SYN flood. That will tell you if CC thinks it connects but fails to send data, or if CC thinks it does not connect. Send yourself a CC debug log (CC / Settings / Other / Send a debug log). Is CC using exactly the same URL as you are typing into the browser? In other words, does work in the browser? If you are doing some sort of reverse proxy then this URL might fail. All the site certs, intermediate and otherwise, must be installed on the device running CC. Seriously, you have no firewall installed on the calibre computer or on any router between the device and the calibre computer?Īre you using HTTPS with a self-signed cert? CC does not support these. The connect from the browser is done from the same device as the CC. Therefore I configured fixed IP/Port in the CC. But there is no multicast between the networks.
There is no firewall, just routing between the WLAN network 192.168.26.0/24 and the LAN 192.168.10.0/24. When you say that you can access the server using a browser, on what computer are you running that browser? My guess is that it isn't the device running CC. Also, if there is a router between the device running CC and the calibre server then you must enter the calibre IP address and port into CC. The reason that CC would terminate the connection is that calibre does not send any data, or that the connection was never actually made. What you describe sounds like the antivirus or the firewall on the calibre computer is blocking CC's connection. Have you gone through our FAQ on connecting to calibre? Terminates the connection without any data transfer. "wireshark" and I can see, that the client sets up a connection and I am testing the demo version prior to buy the fully featured version.
0 kommentar(er)
