Unexpected address bindings when starting server.

[jmurtari]

Folks, our club is trying to do more with multiplayer. Having some issues with Condor 3 running on Windows 11, tried to follow the setup in the user's manual. I'm a software engr with network experience, to summarize, Condor 3 doesn't seem to bind to all available interface addresses (voice does, but flight info does not) and this can make port forwarding from a router difficult.

I searched the forum, don't see other folks talking about this, but we've had three different club members run into these issues when attempting to host. Not sure if it's Windows versions, different network defaults in the United States?

Excuse the length, but wanted to give the development team as much info as possible. I do believe one way to make this more predictable is to have the user specify the address to be used.

My PC, Win 11, my interfaces:

Ethernet adapter Ethernet:
Link-local IPv6 Address . . . . . : fe80::7adc:6b82:f7ca:a6d6%18
IPv4 Address. . . . . . . . . . . : 192.168.0.173

Ethernet adapter Ethernet 2: (Note: this is for an internal VPN, the 10.0.0.5 is not acceptable to the router, different LAN) I've seen users running other software have other private addr ranges shows, e.g. 172....
Link-local IPv6 Address . . . . . : fe80::dc3b:894f:dec9:8234%9
IPv4 Address. . . . . . . . . . . : 10.0.0.5


#### Case #1 - Starting Multiplayer from within Condor 3 and choosing the "Host" option:
All normal up to the point where I press "Start Server", then over about 10 seconds I see the following:

# FIRST - I see the audio has bound to all interface addresses (good), but the flight info only binds to the 10.x and v6.
jmurtari@saw:/cygdrive/c/John>netstat -na | egrep '56278|56279|56280'
UDP 0.0.0.0:56279 *:*
UDP 0.0.0.0:56280 *:*
UDP 10.0.0.5:56278 *:*
UDP [fe80::7adc:6b82:f7ca:a6d6%18]:56278 *:*
UDP [fe80::dc3b:894f:dec9:8234%9]:56278 *:*

# On my PC screen I see connecting to host -- receiving data, I get the green bar, it stops at 50%, I then get "Host not found", server appears to stop:
jmurtari@saw:/cygdrive/c/John>netstat -na | egrep '56278|56279|56280'
-- no results

##### Case #2 - Staring the CondorDedicated server directly. Interface comes up, load a flight plan, accept the defaults for server options, and press "Start server". I see the following:

jmurtari@saw:/cygdrive/c/John>netstat -na | egrep '56278|56279|56280'
UDP 0.0.0.0:56279 *:*
UDP 0.0.0.0:56280 *:*
UDP 10.0.0.5:56278 *:*
UDP [fe80::7adc:6b82:f7ca:a6d6%18]:56278 *:*
UDP [fe80::dc3b:894f:dec9:8234%9]:56278 *:*

# The above is stable, I can then go into Condor Multiplayer, and if I use the 10.0.0.5 addr, I can connect successfully locally, but again, not of use for external folks.

Any suggestions are welcome!
John

[n98Bk9-NT3]

Are you using an IPv6 network ISP?
I also have a problem passing through IPv4 over an IPv6 ISP network.
In Japan, MAP-E, IPv4 over IPv6, similar to DS-Lite, is widely used.
I try to publish online tasks by a Condor Dedicated server through my home router by using UPnP-IGD.
It works to communicate flight data, but I couldn’t establish voice channels.
I mean that we can enjoy flying together but cannot communicate through Condor voice channels.

On the contrary, I tried another ISP that only uses an IPv4 network, and there is no problem communicating flight and voice data by using one-by-one port forwarding settings for three ports.

I am afraid that communication/negotiation of voice channels by the Condor dedicated server is different from flight data communication channel, under the environment of IPv6 Internet communication.

Naoki

P.S. MAP-E, IPv4 over IPv6, shares one IPv4 address with several ISP users. Therefore, different range of ports are assigned to each users for opening their own service purposes.

[janjansen]

Ill report this, but as a temporary workaround, maybe you can try this:
https://r1ch.net/projects/forcebindip

[n98Bk9-NT3]

I tried ForcebindIP to apply Condor dedicated server.
But it didn't work in my case.

Naoki