Notify me about new: Guides Cheats Reviews Questions Add this game to my: Favorites Now Playing Wish List Play Queue Home QA Board More Home Summary Release Data Game Credits Also Playing Collection Stats QA Media Images Board.The Nazi blitzkrieg conquers most of Europe with a genocidal madman at the controls.
Prepare to battle the evil of the Axis powers and the hideous things that rise in their wake. This isnt just war-this is Weird War Weird War II contains everything you need to run horrific World War II adventures with the Savage Worlds game system: new powers, Edges, Hindrances, weapons, vehicles for all the major powers, an Adventure Generator, dozens of Savage Tales, new monsters, and an operational-scale Plot Point Campaign that ties it all together. Requires: A Fantasy Grounds full or ultimate license or subscription and the Savage Worlds Ruleset. Star Wars: Knights of the Old Republic II - The Sith Lords The next chapter of Star Wars: Knights of the Old Republic begins with a new storyline, force powers, characters, cla. South Park: The Stick of Truth From the perilous battlefields of the fourth-grade playground, a young hero will rise, destined to be South Parks sa. Gothic In dark, troubled times, a man will rise up to change the fate of an empire. Risen 2: Dark Waters Set several years after the end of Risen, raging titans have devastated the world and pushed humanity to the brink of. 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 Step 7: Connect, test, fix glitches Connecting your OpenVPN client You now know the Public IP for your server: you will use it to connect your OpenVPN client. Right-click your OpenVPN GUI, and Edit Config on your connection menu: Edit Config to write the public IP Remember the placeholder at line 6 Replace it with your servers pubic IP that you copied previously in the EC2 Console: Now closesave, right-click again and Connect Youll see a log flowing in a window..aaaannnnndddd. Yeah Bravo Cheers CongratZ You are now officially a geek: youre both a VPN client AND a VPN operator, all in 1 person So bookmark this and come back after you have properly celebrated this major event in your life. Your VPN client Private IP Well take a note of our VPN Private IP address, that you see in the OpenVPN balloon tooltip. For this demo, we specified VPN network in our UserData as 10.10.10.024, so we are 10.10.10.6 Being the only client for your VPN server, you should always get the.6 VPN Private IP address in the network you specify in your UserData Important: the server does Fantasy Grounds port forwarding for the.6 IP ONLY Some pings Lets open a new command prompt window and try a few commands: ping 10.10.10.1: pings the servers VPN private IP Lets have a quick look at our server various IPs: ping 172.31.10.45: pings the servers ethernet LAN adapter private IP in AWS ping 13.53.45.99: pings the servers Public IP First ping tests Hummm.The server does not reply to our ping on its Public IP. Why Because we dont have a rule in our Security Group for that. Lets add a rule to our Security Group: you can click its name in the left column of the EC2 instance Description tab, then go to the Inbound rules tab of the Security Group and click Edit, then Add Rule: We want to authorize inbound ping requests, which are in reality ICMP echo requests, so our new rule will be typed Custom ICMP rule - IPv4, with protocol Echo Request, from source 0.0.0.00: Lets Save, then go back to our EC2 instance details to check it applies: Yep Now pingable from anywhere Lets retry our ping on the public IP to check we have the replies.ok ping to public IP is now ok Fantasy Grounds Now lets start Fantasy Grounds and create a test campaign with any ruleset and Start it. Fantasy Grounds Conflict Free To ReNow lets disconnect our player FG and re-check: After player leaves the virtual table We still see our GM FG listening, and the dynamic port that was used by our player FG (TCP 55536) is now in TIMEWAIT state, belongs to no process ID, and will be completely free to re-use by Windows within 4 minutes. Connecting a player FG to the server public IP This is all well and good, but what you want is players connecting to your server (its public IP, currently 13.53.45.99 in this demo) so that they auto-magically appear in your GM FG virtual table. Lets try Connecting to the server as a player from the Internet Aarrgghh.Well, actually: Yeah It works (though it looks disappointing.) It looks like a Fail but it is a Pass Houston, we have liftoff YES Our GM FG and Player FG were actually able to talk to each other..but they have DIFFERENT IPs and the SAME license key LICENSE KEY CONLICT. Your REAL players CAN now connect to your GM FG, using the server Public IP And if you then retry our netstat command, youll see all these connections arriving on your VN Private IP on port 1802, all coming in from the server Private IP various ports. So here is an example of 2 connections, from 2 players with a Demo version of FG to my GM FG virtual table through the OpenVPN port-forwarding server: The player connections seen on my GM FG machine: Our GM FG sees ALL the port-forwarded player connections coming in: from the server Private IPv4 address (172.31.10.45 in this demo) from various TCP ports to our own VPN Private IP (10.10.10.6 in this demo) always on our TCP 1802 port Note: I have FG Ultimate license so I can host any combination of licenseddemo players; if you have FG Standard then you can host 1 demo or N licensed players. What if it fails What How When Where You have a real failure Like this one with a player FG Or worse, you cant even connect with your OpenVPN client to your shiny new server FG: Maybe you forgot what you should always remember Ok,10 seconds to..Now recheck everything for your GM machines Barriers 1-3, remembering that FG inbound connections will come to your GM FG through the VPN connection, which Windows (rightfully) considers to be a DIFFERENT network than your usual home network. Beginning of the system log After 450 to 500 lines, if you encounter the following error message, it means your fgovpn001-init.sh was saved with the CRLF mode for End-Of-Line control characters instead of LF: Error example: init script saved with CRLF mode In this example, because of a rogue CR character (M) at the end of the very first line, the init script did NOT execute AT ALL, so OpenVPN is not even installed on your (useless) virtual server In the above example, dont be confused by the following line 502 ( UserData script finished ). The very last thing that the UserData script tried to do was running fgovpn001-init.sh (line 499), so the error actually comes from that file, not from the UserData script (it has been cleansed of any CRs by importing it in the web editor in the AWS Console). Correct the error by saving fgovpn001-init.sh in LF mode in your my-fg-ovpn-s3 local sub-folder, re-transfer the file to S3 to overwrite the one you previously stored, Terminate (destroy) your current instance (right-click Instance State Terminate ) like shown in Step 8, and then launch a brand new one.finally, if you still cant make this work, then ask for help with the links at the beginning of this document. A little fix to our AWS Launch Template A little glitch caught my when we launched our server, that youll find just below the pink highlight for Sourcedest. Anyway, this came out because in the AWS region we used, we did not have the usual free tier elligible t2.micro instance type but the t3.micro instead, and i found this note in AWS EC2 documentation which explains this unexpected (at least for me) setting: Just to be sure, well disable this setting and that will give us an opportunity to experiment with creating a new version of our Launch Template. The Launch Template v2 We go to the Launch Templates section of the EC2 Console and click Create launch template again, but this time we: select Create a new template version select our existing template enter a version description select the existing version as source New template version, select our template..enter a version description and select original version as source Then we go to the bottom, expand Advanced details and put the T2T3 Unlimited setting to Disable: Disable T2T3 Unlimited And now we can click the final Create launch template button: Here we are: Now lets make this new version the default version of our Launch Template, because the original one is currently still the default one: So we check the line is selected (blue square on the left) and use the Actions button: Nothing mysterious there. Finally were done: Transfer First Test - Previous Step 6: Launch time Next - Transfer First Test Step 8: DestroyTerminate after use Last updated 1 year ago Contents Connecting your OpenVPN client Bravo Cheers CongratZ Several tests Your VPN client Private IP Some pings Fantasy Grounds Anatomy of a local connection Connecting a player FG to the server public IP Houston, we have liftoff What if it fails FG: Maybe you forgot what you should always remember OpenVPN: CRLF Check the startup log of your OpenVPN server instance A little fix to our AWS Launch Template The Launch Template v2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |