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
  • Create/have an account available on AWS
  • Check that you know/learn :
  • Prepare a "safe" place on your own machine.

Was this helpful?

  1. Local setup - Step-by-step

Step 0 : Preparation

PreviousSetup process overviewNextStep 1 : OpenVPN + Easy-RSA & "new-PKI"

Last updated 4 years ago

Was this helpful?

Let's begin with :

Create/have an

...as explained there... ...and create your first admin user !

Check that you know/learn :

  • with your version of Windows

  • in Windows Explorer

Also useful :

  • in Windows

  • to the Windows Taskbar

It may also be a good idea to know/learn in Windows Explorer as well...

...and remember you'll end up needing a at some point !

Prepare a "safe" place on your own machine.

Create that on another drive than your system C: drive if you can, mandatorily in a place where you have Read+Write permissions...and of course NOT in a "recovery" drive/partition.

We'll create an empty folder to store your whole thing, then empty sub-folders in it to store different types of files by category.

It is always easier to have multiple sub-folders that you can independently rename/move/copy/zip/etc..., rather than a messy bunch of "more or less" related files in a single folder !

I suggest an organization like this one (in this example i prepared sub-folders for 2 GMs = VPN "clients") :

In the T: drive, I created the fg-ovpn root folder, with :

  • docs for docs & infos you may download in case you need to look them up years later...

  • new-PKI for a blank PKI installation, ready to be duplicated to initialize a PKI from scratch

  • source-install for downloaded installation packages

We also have a separate Tests folder for tests and messing around with temporary things.

Choose a simple "configuration name" for your setup, and try to use it to prefix/idenfity all related things.

This "configuration name" is VERY important : it will be used by configuration scripts; many of the files you will create later on MUST start with it as a prefix, so : better get used to it !

In this sample setup we use "my-fg-ovpn" for our configuration name...

...and we create the MY-FG-OVPN folder (in capitals to remember it must be kept safe) to store our own FG OpenVPN setup, with these sub-dirs:

  • my-fg-ovpn-clients will store the complete set of parameter/security files needed for each VPN client (with a sub-folder for each), ready to be zipped/copied/emailed

  • my-fg-ovpn-s3 will store the source files we'll transfer to the AWS S3 bucket for server auto-initialization

  • my-fg-ovpn-server could store files you may want to copy from your OpenVPN server (logs,...)

  • MY-FG-OVPN-PKI will be the "safe" storage for our entire PKI, ready to use at any time if we need to create additional certificates or revoke an existing certificate.

I suggest you ONLY use CAPITAL letters on your local Windows machine, to be reminded of the folders you NEED TO KEEP SAFE, and use lowercase for all folder and file names you will transfer to AWS and the server.

Your OpenVPN server will be Linux-based, which implies case-sensitive !

CAPITAL LETTERS = YOUR MOST PRECIOUS LOCAL FOLDERS.

MY-FG-OVPN for our own FG OpenVPN setup

Read this again !

Got it ?

⚠️
⚠️
👆
like this
how to open a command line
how to show file extensions
how to set your Windows connections to "private" or "public"
how to create shortcuts
how to pin shortcuts
how to show hidden/system files
👆
👆
account available on AWS
proper text editor