Hi Mike.
If "remotely operating" the Hermes-Lite is your objective, there are other ways to do so that are less demanding in terms of network demand then port-forwarding port 1024 and transfer all OpenHPSDR-protocol related traffic to your remote location.
I myself are remotely operating my HL-2 for half a year now with a very simple set-up:
@home: I've got my HL-2 connected to a "headless" RaspberryPi:
1a. running piHPSDR as the SDR-program processing the HL-2 output & controlling the HL-2
1b. running VNC-server (installed by default on Raspian Buster) to provide remote acces to the desktop of the headless RPI
1c. running mumble-client to transfer audio between piHPSDR and a (the) mumble-server
1d. running mumble-server to transfer audio between connected clients (typically the mumble-client that's hooked-up to piHPSDR and a remote mumble-client
@remote I "operate" either my MacBook-Air or my Samsung A50 cellphone
2a. running RealVNC to remotely access the headless RaspberryPi located @home
2b. running mumble-client to transfer audio between my MacBook-Air (or my Samsung A50) and the mumble-server @home
Right now I'm on holiday in Bavaria, Germany and attending local 80m net almost daily this way from my camper. It works flawlessly.
By only transferring the audio, made possible by having the headless RaspberryPI @home doing all the signal-processing, the dataflow between my home and my remote device is limited to only 8Kbps?! Implying I can run a one hour net and "consume" less than some 40MB out of my bundle?!
If you like, I can send you a link pointing to a file containing a micro-SD card image I made with all components properly installed.
Flash this image to a microSD-card, put it in your/a RaspberryPI and there you go.
73's Christiaan PA3FUN