Fantasy Grounds - Port Forwarding - Transparent Op
  • Fantasy Grounds - Port Forwarding and a "transparent" OpenVPN setup
  • General
    • Introduction - F.G.Comms
    • GM's machine barriers
    • Internet connection barriers
    • Some NO-GO Situations
    • VPN solutions
  • Proposed Solution
    • "Transparent" OpenVPN-based Port Forwarding
    • Tools
    • Amazon Web Services
    • Setup process overview
  • Local setup - Step-by-step
    • Step 0 : Preparation
    • Step 1 : OpenVPN + Easy-RSA & "new-PKI"
    • Step 2 : Create your own PKI
    • Step 3 : Setup OpenVPN connections
  • AWS Setup - Click-by-Click
    • Step 4 : Your AWS environment
    • 4.1-Creating the IAM Role
    • 4.2-Choosing the AWS Region
    • 4.3-Creating the S3 bucket
    • 4.4-Virtual Private Cloud - Default VPC
    • 4.5-Creating an AWS Key Pair
    • 4.6-Creating an AWS Security Group
    • 4.7-Filling the bucket
    • 4.8-Building the Launch Template
  • Transfer & First Test
    • Step 5 : Transfer to S3
    • Step 6 : Launch time !
    • Step 7 : Connect, test, fix glitches
    • Step 8 : Destroy/"Terminate" after use
  • Use your server
    • Regular Usage Pattern
  • Simultaneous FG games / 1 VPN Server
    • Lifting the "1 GM at-a-time" restriction
    • FGU vs. FGC networking
    • VPNs for both FGC + FGU (LAN mode)
  • Upgrading our setup for "N-at-a-time", FGC/FGU
    • Untitled
  • Appendixes
    • Acronyms and definitions
    • AWS acronyms
    • AWS admin user + API access key
    • AWS, DNS, DDNS, CRL...
    • Possible (?) developments
  • Links
    • Fantasy Grounds Web
    • Fantasy Grounds Discord
    • FG College Web
    • FG College Discord
    • FG College KB
    • Our "EU" Discord
    • OpenVPN
    • AWS
Powered by GitBook
On this page

Was this helpful?

  1. Use your server

Regular Usage Pattern

Running 24x7 or not

Depending on your situation vs. the AWS Free Tier, you may choose to run your server :

  • either 24x7 (especially during the first year, while your total AWS monthly cost is $0)

  • or on-demand, only when needed (if you want to drastically optimize costs later on)

The drawback of starting/stopping or launching/terminating your server on-demand is that the public IP address will change at every startup, and you'll have to :

  • do "Edit Config" with the OpenVPN GUI to enter the new public IP

  • and communicate the new public IP to your players so they know where to connect

Remember that FG Alias and Test Connection are not functionnal with our setup.

This would be the regular usage pattern when running the server only when needed :

  1. Launch new instance from Launch Template and note the Public IP of the new server

  2. OpenVPN GUI :

    1. Edit Config (to enter the new server Public IP)

    2. Connect

  3. Give the new server Public IP to your players

  4. ==> Fantasy Grounds game session <==

  5. Disconnect OpenVPN

  6. Terminate the instance

As you can guess, the management of the changing public IP can become a pain, especially if the server is shared with other GMs (see following sections) and has to be started multiple times a week...

PreviousStep 8 : Destroy/"Terminate" after useNextLifting the "1 GM at-a-time" restriction

Last updated 4 years ago

Was this helpful?

This can lead you to trade some cost optimization for ease of use and run you server 24x7, even when you are out of the Free Tier bounds - be sure to check the cost minimizing techniques I mentioned earlier :

Amazon Web Services - Minimizing AWS costs when you step outside the Free Tier