Linux Testing

[craigbert]

That is good to know @Jiminimonka.
I have been using Mint and a few other Ubuntu based distros for years so I am most comfortable with them.
Additionally I have a development platform that I favor and they only support Mint and Ubuntu.
So Ubuntu really is the only / next option for me.

I recently purchased a new PnP wifi adapter that is explicitly made for Linux. I just started testing with it in hopes that the issue is with my built in Wifi chipset/NIC.
Sadly, I am seeing the same errors with the new wifi adapter so I think that rules out a network hardware issue on my side.

This time tomorrow I hope to be converted over to Ubuntu so hopefully this will become a moot issue.

(edited for grammar)

[craigbert]

OK, so where do we go from here?

Screenshot from 2024-10-06 22-04-48.png

[craigbert]

Hi All,

I have installed Ubuntu 24.04, installed FGU, not installed any desktop tweaks or extensions, and I am still seeing the same error.
I have created a new campaign and the same error persists.
At the behest of support I have gone through the Network Troubleshooting page.
That can be found here:
https://fantasygroundsunity.atlassia...roubleshooting

Step 1 Ensure Correct Join Campaign Settings ~ this is not an issue. I get the error with or without any players connected.
Step 2 Check Security Software ~ My firewall is turned off and there is no virus or malware software running. I even added a rule for port 1802 UDP both directions, but I had to enable the firewall to add the rule. So I left it up and I still got the same error.
Step 3 I have gathered logs and post some with this message. I have also emailed the same logs to [email protected]
Step 4 Basic Connectivity Checks ~ I can't say that I have tried all the variations, but all my players connected this last Saturday without issues.
Step 5 VPN Usage ~ There is no VPN in use.
Step 6 My laptop does not have an ehternet port so unless I purchase an ethernet dongle that is not an option. I have purchased another USB Wifi NIC that explicitly works with Linux and is PnP. I get the same issue using it as I do on my built in Wifi adapter. For the record I did a "sudo ifconfig wlo1 down" before testing. The only interfaces up using the PnP NIC was Loopback and the NIC.
Step 7 Check Network Performance ~ at the router 609.72Mbps down and 507.69Mbps up. At the laptop 263.64 Mbps down and 228.96 Mbps Up. Pinging from the laptop to the FG Host (104.248.118.207) as shown in the network logs in FGU the latency averages around 40ms.
Step 8 ISP Analysis ~ No outages and nothing setup in the ISP Router (dumb and not a WiFi router)
Step 9 Everything Else
* Network: There is the ISP Router and my personal router. I have had this configuration for decades. I just never use the crappy ISP supplied routers except as a pass thru.
* My router does not have QoS turned on, no parental controls, no ad or image filtering
* Recent changes: I have switched from Windows back to Linux. I have been using FGU on Windows for years without issues. Due to a handfull of factors, not related to FGU, I have pitched Windows and returned to Linux.
* I do have a couple other machines including a Windows machine and it has no problems connecting to FGU and/or Hosting.
* Not sure how to use or change ports....
* No VMs.

[Moon Wizard]

As I mentioned before, we do not have an in-house Linux client specialist; so we don't have anybody that's knowledgeable in troubleshooting specific hardware/software configuration or network issues on Linux machines. This does not appear to be a general issue, since there are several Linux users that are active and no one else has reported a similar issue.

Some items to mention:

* The network log is expected to have a bunch of unreachable messages during connection negotiation, because it is trying every NIC multiplied by every routing to try and find the best connection for hosting in order to register that combination with the lobby server. So, these messages do not provide any information other than the ongoing negotiation when starting hosting.
* The lobby server disconnect is an indication that the operating system or hardware is closing the network connection while FG is still using the connection.
* Maybe there are time outs set on your machine via software or OS configuration for closing connections that are open but haven't been sending data for a while?
* Maybe the wireless connection is unstable in the current setup? Or in the location of your wireless router / computer?
* You could potentially sync up the network.log exact timing with the console.log WARNING report to see if anything shows up in the network logging. You'd need to map up exactly to the second.
* My guess is that the connection is getting interrupted/closed, probably due to wireless interference or weak signal.

Perhaps someone versed in Linux configurations might have some ideas...

Regards,
JPG