I figured I would submit a summary of results should anyone else run across this:
- DCS OpenBeta server operational on local machine with WebGUI for administration.
- Settings configured in SavedGames\DCS.OpenBeta_Server\config with the following files:
serverSettings.lua - the main config file
nicknames.lua - configures the server’s player name.
autoexec.cfg - configures some runtime parameters such as disabling track files and automatically submitting error reports to ED.
Port forwarding confirmed valid at the router level and no local firewalls appeared to be setup to block access.
The problem sits at the ISP level as @whareagle‘s internet access comes from a microwave relay. His router is given a WAN address in the 100.64.X.X range which is actually a private range for ISPs to use for these types of relays - meaning the address isn’t “public” it’s the equivalent of 192.168.X.X or 10.X.X.X range addresses for your home LAN, just at the ISP level. His actual public IP ends up being in another range entirely, that is registered to his ISP.
The result is a two fold issue. The router can present NAT between LAN and the 10.64.X.X address, which DCS picks up and listens on. The DCS master server registers him on the list under his public IP - so we have a mismatch already. The other problem is that while his router can port forward from LAN to 10.64, we don’t know if from the 10.64 range to public is open or not, and I suspect not. Normal basic firewall setup would allow outbound connections, but not inbound which could be the problem as servers requires open connections for a client (player) to be able to initiate.
Before checking that out with the ISP, two things have to be covered:
-Check your WAN IP as stated by your router (which it may label as “public” as in it’s view, that is external)
-Check your actual public IP (you can google “what is my IP” for that)
That’s as far as we covered last night!