ok... So I am going to have to make it quick and to the point as I am dealing with a bit much right now with work. But heres the "rough" steps I took to get it going.
Pre-Starting: Make sure you are doing this from the location (i.e. your IP address you started the container with)
1.) make sure to to get signed up for a DYNDNS type account. I used DuckDNS.org (you get 4 for free)
2.) add a DuckDNS, DYNDNS and put it on something, I used my Samsung Galaxy Note 4, and follow the prompts to add your token and get the device setup and verify it on DuckDns.org that it really is updating
3.) add your FQDN via SSH to box as root (./add-FQDN) e.x.
Code:
./add-fqdn note4 myphone.duckdns.org
3 a.) I choose all options under privileges to test with since I can delete this account later
4.) change the /root/ipchecker file via nano as describer in
wardmundy guide to reflect your new FQDN under
5.) add the time limit that you desire to
as also described on NerdVittles.com (I chose 3 minutes, I'm impatient)
6.) configure a port knocker utility. I used PortKnocker as suggested by Ward on NerdVittles.com article for my Note 4. And added the 3 unique ports
7.) test out by running Port Knocker on your device (you dont have to use Port Knocker, just for my case it made things easier)
8.) you can if still SSH'd in to the box in question, look at the ipchecker.log file. The only thing that would hold up this process is possibly having to wait the amount of time you have allotted in crontab for the script to run & the DYNDNS client update time.
Hope this helps. This post as raw and unedited as it is has now taken me since about 3:15pm EDT until now which is 10:30PM EDT. Being busy is nice. Yet has it's downsides as well.
*** Knock on Wood......... Everything has worked fine with this setup for 2-3 weeks now using "public" WiFi which was of course not the greatest being at a mall, but hey, no cell coverage during that time and its what I had to work with. And it worked great during that time even as horrible as the WiFi was.