MobileRead Forums - View Single Post

chaley · 12-21-2019, 06:16 AM

If the Chromebook is doing NAT for the Android VM then it is acting like a router. That is the way NAT works -- routing address:port to internal-address:internal-port.

Both the content server and wireless device connections are initiated by the client. If one works then the other should too unless the Chromebook is recognizing HTTP and handling it differently, which I doubt.

In a NAT situation there is no hope that CC will be able to auto-find the calibre server. Auto-connect uses broadcast UDP and MDNS. The NAT router (the Chromebook) will not propogate these packets. However, entering the calibre server IP address and port into the Wireless Device parameters should work if the content server connection works.

Things to check:

Is the wireless driver in calibre actually started?
Are you using a reserved port for the wireless device (<1024)?
Has your antivirus changed and is now blocking the connection?
Do you see any evidence of a "SmartDevice" connection in a calibre debug log?
On the device, connect to the wireless device using a web browser, something like 192.168.1.6:9090 where "9090" is replaced by the port you use. You should see "invalid response", and there should be a lot of chatter in the calibre debug log. If you don't see this but connecting to content server manually (something like 192.168.1.6:8080) does work then something on the calibre machine is blocking wireless device connections.

12-21-2019, 06:16 AM	#4
chaley Grand Sorcerer Posts: 12,488 Karma: 8065348 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	If the Chromebook is doing NAT for the Android VM then it is acting like a router. That is the way NAT works -- routing address:port to internal-address:internal-port. Both the content server and wireless device connections are initiated by the client. If one works then the other should too unless the Chromebook is recognizing HTTP and handling it differently, which I doubt. In a NAT situation there is no hope that CC will be able to auto-find the calibre server. Auto-connect uses broadcast UDP and MDNS. The NAT router (the Chromebook) will not propogate these packets. However, entering the calibre server IP address and port into the Wireless Device parameters should work if the content server connection works. Things to check: Is the wireless driver in calibre actually started? Are you using a reserved port for the wireless device (<1024)? Has your antivirus changed and is now blocking the connection? Do you see any evidence of a "SmartDevice" connection in a calibre debug log? On the device, connect to the wireless device using a web browser, something like 192.168.1.6:9090 where "9090" is replaced by the port you use. You should see "invalid response", and there should be a lot of chatter in the calibre debug log. If you don't see this but connecting to content server manually (something like 192.168.1.6:8080) does work then something on the calibre machine is blocking wireless device connections.