[iOS] Problems using default settings when connecting to Calibre.

[svenlind]

I have an iPad Pro and an iPad Mini.

The Mini connects to Calibre without problems using the default settings.

The pro also used to connect to Calibre using the default settings, but then suddenly wouldn't do that anymore.

I then entered the IP address and port as reported by Calibre under settings in CC, and everything worked again.

But I noticed that CC reported the iPad's IP adress as 10.131.66.47, and told that the Calibre IP address should be similar.

Well, the IP address of the PRO is 192.168.0.2 as reported of the iPad under settings and also by my router.

The Calibre address is 192.168.0.29 and is indeed similar to the PRO's true IP address.

I believe that the false mention of the address 10.131.66.47 is the reason that default settings can't be used with the PRO.

Everything is reported correctly in the iPad Mini.

It is not a serious problem as I can connect to Calibre using the manual settings. But it may happen that the router assigns another address to the computer, or I might change to another PC where I have one of my Calibre backups.

Edit. Marvin can connect directly to Calibre.

[chaley]

CC is getting that 10... private network address from somewhere. Does the PRO have more than one network interface? Perhaps both WiFI and cellular? Or IP over bluetooth? It could be that when multiple networks are available CC is picking the wrong one.

Although my son works on iOS CC while I do the Android version, I am interesting in what is happening network-wise. If you could send me a CC debug log at cc_debug_logs AT haleys DOT org I would appreciate it. And who knows, I might actually see something useful.

[svenlind]

Originally Posted by chaley

CC is getting that 10... private network address from somewhere. Does the PRO have more than one network interface? Perhaps both WiFI and cellular? Or IP over bluetooth? It could be that when multiple networks are available CC is picking the wrong one.

Although my son works on iOS CC while I do the Android version, I am interesting in what is happening network-wise. If you could send me a CC debug log at cc_debug_logs AT haleys DOT org I would appreciate it. And who knows, I might actually see something useful.

Thank you for your reply.
I decided to use default settings and then try to connect to Calibre before I sent the log. Now everything works again.
But CC still reports the 10... address. I sent the log anyway.

The PRO does have a cellular network interface and its own simcard. But I am sure that it was connected to my local WIFI when I had the problem because I could connect when specifying the Calibre IP address.

[chaley]

Thanks for the debug log.

There are two interesting things to note:

1. CC attempts to find calibre using a "broadcast" scheme. For most people this is the most reliable way to find calibre. For you, the log says that it never works.
2. CC also uses "bonjour" (aka zeroconf, mDNS, UPNP) to find calibre. In your case this usually, but not always, works. That matches our experience with bonjour, that it is rather unreliable.

The question: why does the broadcast scheme not work? One possibility is that CC is enumerating the IP addresses available to it, selecting one of them without regard to whether it is WiFi or cellular, then broadcasting on only that address. Another is that it is *not* enumerating the addresses but is instead sending the broadcast to 0.0.0.0, something that does not work on all platforms. Steve will need to chime in at some point with how the broadcast code works on iOS CC. FWIW: Android CC enumerates the IP addresses and sends the broadcast on each of them.

You can test this (if you want) by turning off the cellular connection. After that, if you go to CC's settings then you will probably see the correct 192... address. Now attempt to connect CC to calibre. It will probably work, but at this point we don't know why because it could be bonjour. Whether or not the broadcast worked will be in the CC debug log. If you want to check it yourself, send yourself the log, open it in an editor, go to the end, search up for "ServerScan: Broadcasting" (no quotes), then read down until you see something like "WirelessDevice: Found 1 servers". If the broadcast worked you will see "ServerScan: Received response from <IP>:9090 via Broadcast" just above that line. If you don't want to check it, send it to me.

As for why iOS CC is showing the 10... address, I suspect it is also because iOS CC is taking the first address available to it instead of filtering for a WiFi address.

[svenlind]

Originally Posted by chaley

Thanks for the debug log.


You can test this (if you want) by turning off the cellular connection. After that, if you go to CC's settings then you will probably see the correct 192... address. Now attempt to connect CC to calibre. It will probably work, but at this point we don't know why because it could be bonjour. Whether or not the broadcast worked will be in the CC debug log. If you want to check it yourself, send yourself the log, open it in an editor, go to the end, search up for "ServerScan: Broadcasting" (no quotes), then read down until you see something like "WirelessDevice: Found 1 servers". If the broadcast worked you will see "ServerScan: Received response from <IP>:9090 via Broadcast" just above that line. If you don't want to check it, send it to me.

As for why iOS CC is showing the 10... address, I suspect it is also because iOS CC is taking the first address available to it instead of filtering for a WiFi address.

I did as you suggested and here is the relevant part of the log:

2016-12-18 13:47:11.094 [Default|INFO] ServerScan: Broadcasting on port 54982
2016-12-18 13:47:11.097 [Default|INFO] ServerScan: Broadcasting on port 48123
2016-12-18 13:47:11.099 [Default|INFO] ServerScan: Broadcasting on port 39001
2016-12-18 13:47:11.100 [Default|INFO] ServerScan: Broadcasting on port 44044
2016-12-18 13:47:11.100 [Default|INFO] ServerScan: Broadcasting on port 59678
2016-12-18 13:47:11.102 [Default|INFO] Searching Bonjour
2016-12-18 13:47:11.134 [Default|INFO] Received response from 192.168.0.29 via Bonjour
2016-12-18 13:47:11.577 [Default|INFO] Received response from 192.168.0.29 via Bonjour
2016-12-18 13:47:15.110 [Default|INFO] ServerScan: Received response from 192.168.0.29:9090 via Broadcast
2016-12-18 13:47:15.115 [Default|INFO] WirelessDevice: Found 1 servers
2016-12-18 13:47:15.120 [Default|INFO] WirelessDevice: Connecting to http://192.168.0.29:9090

And yes if I turn off the cellular connection the CC reports the correct IP address. When I turn the connection back on CC reports a (new) 10... address.

Thank you for swift replies

[Steve_Haley]

Originally Posted by chaley

Thanks for the debug log.
The question: why does the broadcast scheme not work? One possibility is that CC is enumerating the IP addresses available to it, selecting one of them without regard to whether it is WiFi or cellular, then broadcasting on only that address. Another is that it is *not* enumerating the addresses but is instead sending the broadcast to 0.0.0.0, something that does not work on all platforms. Steve will need to chime in at some point with how the broadcast code works on iOS CC. FWIW: Android CC enumerates the IP addresses and sends the broadcast on each of them.

....

As for why iOS CC is showing the 10... address, I suspect it is also because iOS CC is taking the first address available to it instead of filtering for a WiFi address.

Ha, an issue with choosing the cellular network and the WiFi network is very likely. The iPhone I use to test and develop doesn't have a SIM card in it, so it's never connected to a cellular network. I'll see what I can do about making it either try all networks, or more intelligently choose the WiFi network, when I next make an update.

[svenlind]

Originally Posted by Steve_Haley

Ha, an issue with choosing the cellular network and the WiFi network is very likely. The iPhone I use to test and develop doesn't have a SIM card in it, so it's never connected to a cellular network. I'll see what I can do about making it either try all networks, or more intelligently choose the WiFi network, when I next make an update.

Thank you