Quote:
Originally Posted by DoctorOhh
I don't know what you mean by "Calibre program", but Calibre has an excellent built in reader.
|
As I mentioned in his other mostly-identical post in the calibre forum, I think by "calibre program" he means "calibre companion".
And yes, his "universal simple steps" aren't so universal. They leave out a few things, such as
- Handling ISP (WAN) dynamic IP addresses.
- DNS (static or dynamic) setup.
- Home routers that use DMZs instead of port forwarding, and the near incomprehensibility of port forwarding setup on some routers.
- Non-static DHCP addresses on the home network (LAN) and their interaction with port forwarding.
- LAN vs WAN access of the content server (router packet reflection).
- Interactions of port forwarding with multi-band and guest mode.
- HTTP vs HTTPS, WAN packet sniffing, ISP "pirate detection", etc.
- Choice of authentication type.
- The interplay of connection metering and attacks. One good thing: kovid added automatic IP address blocking to the content server, making it harder for dictionary attacks to consume paid-for metered bandwidth.
- As you said, the security impact of opening the LAN to bad guys.
- And finally, connection methods that don't involve a calibre content server, such as the cloud, calibre-to-OPDS, and COPS.
However, if his solution works for him reliably over time then fine and dandy.
In order to avoid opening ports on my LAN, something I refuse to do, I use a commercial VPS (linode) to run the content server. Like you I also use Dropbox, which conveniently also syncs the library from my home net to my VPS.