View Single Post
Old 04-05-2024, 12:57 PM   #4
jhughes2466
Junior Member
jhughes2466 began at the beginning.
 
Posts: 3
Karma: 10
Join Date: Apr 2024
Device: kindle
Quote:
Originally Posted by PeterT View Post
When you define the Docker container you have to specify which ports on the external device (the host where Docker runs) are forwarded to ports within the container; so for instance you could configure external port 9080 to map to internal port 8080. You would then access the application running in the container that was listening on port 8080 by connecting to port 9080 of your physical host.




Sent from my Pixel 7a using Tapatalk

FIRST, thank you very much both for the responses, really appreciate you trying to help me. Let me give a little further context as to what I'm seeing so maybe it will make sense.

=========
That part I've done, I defined the ports, so like I said, I can get to the GUI for example internally and import books etc. But I thought the listener or the share/connect wireless would let me provide that as a listener to be able to connect internally with some of lets say my kids kindle devices and just pick which books they want to import.

Here's where I'm at currently:

Docker: Configured port 8085 - reachable internally via 192.x.x.x:8085

Click "Connect / Share" and it creates listener on a default 172.x.x.x IP range. That range is NOT in the docker compose, its not on the DHCP mapping for my router, and its not part of the Unraid NAS I'm running this thing on. So my assumption is there is some configuration file within Calibre that is saying to "try" initially on 172.x.x.x as a listener.

I can port forward external to internal, but because NOTHING internal on this network has a 172.x.x.x IP I can't actually forward to that IP because its not mapped anywhere. Like if I go to my router and look at all IP's assigned to devices, there is not one that is 172.x.x.x they are all 192.x.x.x.

I believe if I can find where that configuration is set and change it to use a static 192.x.x.x my port forwarding will work. Or then I can use wireguard back to my internal network and hit the listener port. But for the life of me, I cannot find any configuration around the share / listener port. I thought I Found an article that was a couple years old calling out a plugin in the "tweaks" section but I did not have it. So this is a base install, I've added no plugins beyond the ones that came with the initial install.
jhughes2466 is offline   Reply With Quote