MobileRead Forums - View Single Post

chaley · 08-27-2019, 03:39 PM

This is a reply to a PM that the OP sent me. He suggested that I add it to this thread, which is a good idea.
-----
I no longer am involved with CC development. I do help people from time to time if the question is straightforward, which yours is not. The CC developer is samcohen.

As for your problem, it is almost certainly related to routing on your home network. Setting up a routed network requires one to be extremely careful about IP ranges and routing tables. No two subnets can have the same IP prefix. The routers must know how to redirect packets between the networks, which means that they must know where the networks are "located" -- e.g. the routing tables.

In order for CC to work, the device must be able to "ping" the calibre computer and vice versa. If either ping does not succeed then local connectivity is broken. If the pings do succeed then the next test is to connect from the mobile device to calibre's content server (browser, not CC). If that doesn't work then probably the anti-virus on the calibre computer is blocking access, but it could be other things such as firewall or wireless isolation. If it does work then CC should work if given the correct IP address and port on the calibre computer.

CC's auto-connect will not work on a routed network. It uses broadcasts, which are not propagated by routers.

Things can fail if there are multiple paths between the device and the calibre computer, because packets can be routed off a cliff.

Good luck,
Charles

Edit not in the PM: And as theducks said, routing private networks is problematic. It can be done, but doing so requires routing table magic. The reason: the entire point of a private network is to avoid polluting the public IP space.

The solution is to pick a large private network space, for example 10., and subnet it. For example, in your case you might have subnets 10.1., 10.2., and 10.3. Routing would be (relatively) easy to set up, and there wouldn't be any need to route outside the local network.

A better solution is to use one private net with several access points (bridges), as suggested by several people.

08-27-2019, 03:39 PM	#28
chaley Grand Sorcerer Posts: 12,450 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	This is a reply to a PM that the OP sent me. He suggested that I add it to this thread, which is a good idea. ----- I no longer am involved with CC development. I do help people from time to time if the question is straightforward, which yours is not. The CC developer is samcohen. As for your problem, it is almost certainly related to routing on your home network. Setting up a routed network requires one to be extremely careful about IP ranges and routing tables. No two subnets can have the same IP prefix. The routers must know how to redirect packets between the networks, which means that they must know where the networks are "located" -- e.g. the routing tables. In order for CC to work, the device must be able to "ping" the calibre computer and vice versa. If either ping does not succeed then local connectivity is broken. If the pings do succeed then the next test is to connect from the mobile device to calibre's content server (browser, not CC). If that doesn't work then probably the anti-virus on the calibre computer is blocking access, but it could be other things such as firewall or wireless isolation. If it does work then CC should work if given the correct IP address and port on the calibre computer. CC's auto-connect will not work on a routed network. It uses broadcasts, which are not propagated by routers. Things can fail if there are multiple paths between the device and the calibre computer, because packets can be routed off a cliff. Good luck, Charles Edit not in the PM: And as theducks said, routing private networks is problematic. It can be done, but doing so requires routing table magic. The reason: the entire point of a private network is to avoid polluting the public IP space. The solution is to pick a large private network space, for example 10., and subnet it. For example, in your case you might have subnets 10.1., 10.2., and 10.3. Routing would be (relatively) easy to set up, and there wouldn't be any need to route outside the local network. A better solution is to use one private net with several access points (bridges), as suggested by several people.