Jump to content

IP Protocol Issue


Wesjet

Recommended Posts

After some troubles testing my DCS server, I found a solution.

Problem & Solution outlined below.

 

Problem:

DCS VOIP would not show myself and another user in the room list. We could only see ourselves, and we can not hear each other.

 

Local Configuration:

DCS Server on LAN IP 192.168.1.127

Client on LAN IP 192.168.1.5

Public IP will not be included for privacy, but will be referenced by "A.B.C.D"

Router has port 10308 forwarded to DCS Server @ 192.168.1.127, and working for over a year.

Connection to Public Internet is by IPv4 only.

 

Router Info:

Make: ASUS

Model: RT-AC3200

Firmware: 3.0.0.4.382_51640

 

Tested Setups:

  • No Port Forward on 10309 - leaving this to UPNP
  • Port forward enabled for 10309

 

Results:

Clients still cannot see each other.

 

Observations:

My local client sees the DCS server in the listing (and as the last IP in the "Connect by IP" dialog) as its IPv6 link-local [FE80::/10 series] address.

 

Subsequent Test:

  • Attempting to connect to DCS server on same LAN via IPv6 does not allow VOIP traffic.
  • Attempting to connect to DCS server on same LAN via A.B.C.D (IPv4/Public) fails "Address Unavailable". [Not particularly an issue, should be using a LAN IP anyway]
  • Attempting to connect to DCS server on same LAN via IPv4 192.168.1.127 succeeds, with functional VOIP traffic.

 

Results:

  • VOIP traffic does not appear to be able to cross between IPv4 and IPv6 clients, at least for LAN.
  • DCS server could also bind/broadcast LAN IPv4 in addition to public IPv4 and IPv6, so users on the same LAN as thier server can connect from the list using LAN IPv4. (If this is feasible)


Edited by Tiburtius

My Rig:

 

 

CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz.

Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD

DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD.

Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.

 

 

Link to comment
Share on other sites

To follow up with my initial report, as it is related but not exactly the same issue.

 

After the successful test above, I turned off the port forward for 10309 again to test with UPNP since we were able to verify that the VOIP would work. Relying on UPNP, we were unable to make a successful VOIP connection and encountered some client crashes.

 

My friend connecting over the internet had one client crash on slot selection.

Connecting myself encountered crashes with IPv4 or IPv6 LAN IPs (crash reports submitted).

 

Re-enabling the port forward solved the issue for my friend, and using the IPv4 LAN IP myself brought back the successful VOIP connection. LAN IPv6, still failed as described above.

My Rig:

 

 

CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz.

Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD

DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD.

Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.

 

 

Link to comment
Share on other sites

  • ED Team

Thank you for the feedback.

 

I will make sure the team see's it.

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • ED Team

Please add to server's 'Saved Games\DCS\Config\autoexec.cfg' line:

 

net.force_ipv4_lan=true

 

and check again - is it helps?

 

(create autoexec.cfg if necessary, this file doesn't created by DCS automatically)

Men may keep a sort of level of good, but no man has ever been able to keep on one level of evil. That road goes down and down.  
Можно держаться на одном уровне добра, но никому и никогда не удавалось удержаться на одном уровне зла. Эта дорога ведёт вниз и вниз.

G.K. Chesterton

DCS World 2.5: Часто задаваемые вопросы

Link to comment
Share on other sites

BigNewy & USSR_Rik,

 

Thank you for the prompt response!

I have added the line to my autoexec.cfg (I also have the line to disable tracks to save disk space from long MP sessions) and the server restarted successfully showing it bound to the IPv4 address for LAN.

 

I will follow up after work when I can hopefully do a other round of testing.

 

Cheers!

My Rig:

 

 

CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz.

Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD

DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD.

Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.

 

 

Link to comment
Share on other sites

USSR_Rik,

 

It doesn't seem that the autoexec change of adding net.force_ipv4_lan = true worked, at least as hoped.

I have disable_write_track = true as well, which is working - so I know the file is being read.

 

In the Server browser I still see the link-local IPv6 address from the LAN, and it appears to connect with that unless I manually connect via IP like mentioned above. VOIP works with a manual connect via LAN IPv4 and does not with Link-Local IPv6, same as before.

 

Excerpts from my DCS Log file, emphasis added, personal information redacted.

Note, ports 10308 and 10309 are forwarded at the router.

 

2019-12-04 04:18:46.034 INFO NET: UPNP IGD detected.

2019-12-04 04:18:46.034 INFO NET: Internal LAN IP address: 192.168.1.127

2019-12-04 04:18:46.034 INFO NET: External WAN IP address: <public IPv4 address>

2019-12-04 04:18:46.076 INFO NET: TCP external <public IPv4 address>:8088 is redirected to internal 192.168.1.127:8088

2019-12-04 04:18:46.077 ERROR NET: AddPortMapping(10309, 10309, 192.168.1.127, TCP) failed with code 718 (ConflictInMappingEntry)

2019-12-04 04:18:46.082 ERROR NET: GetSpecificPortMappingEntry(10309, TCP) failed with code 714 (NoSuchEntryInArray)

2019-12-04 04:18:46.104 ERROR NET: AddPortMapping(10309, 10309, 192.168.1.127, TCP) failed with code 718 (ConflictInMappingEntry)

2019-12-04 04:18:46.109 ERROR NET: GetSpecificPortMappingEntry(10309, TCP) failed with code 714 (NoSuchEntryInArray)

2019-12-04 04:18:46.109 ERROR NET: UPNP failed to map WebRTC port 10309

2019-12-04 04:18:46.109 INFO NET: Registering HTTP control interface as <public IPv4 address>:8088 (port is forwarded by UPNP)

 

 

2019-12-04 04:18:46.680 INFO Dispatcher: //=== END OF INIT ======================================//

2019-12-04 04:18:46.681 INFO NET: server has started

2019-12-04 04:18:46.682 INFO NET: Using LEDBAT for UDP congestion control.

2019-12-04 04:18:46.683 ERROR NET: AddPortMapping(10308, 10308, 192.168.1.127, TCP) failed with code 718 (ConflictInMappingEntry)

2019-12-04 04:18:46.687 ERROR NET: GetSpecificPortMappingEntry(10308, TCP) failed with code 714 (NoSuchEntryInArray)

2019-12-04 04:18:46.709 ERROR NET: AddPortMapping(10308, 10308, 192.168.1.127, TCP) failed with code 718 (ConflictInMappingEntry)

2019-12-04 04:18:46.713 ERROR NET: GetSpecificPortMappingEntry(10308, TCP) failed with code 714 (NoSuchEntryInArray)

2019-12-04 04:18:46.713 ERROR NET: UPNP failed to map server port 10308

2019-12-04 04:18:46.714 ERROR NET: AddPortMapping(10309, 10309, 192.168.1.127, TCP) failed with code 718 (ConflictInMappingEntry)

2019-12-04 04:18:46.718 ERROR NET: GetSpecificPortMappingEntry(10309, TCP) failed with code 714 (NoSuchEntryInArray)

2019-12-04 04:18:46.739 ERROR NET: AddPortMapping(10309, 10309, 192.168.1.127, TCP) failed with code 718 (ConflictInMappingEntry)

2019-12-04 04:18:46.743 ERROR NET: GetSpecificPortMappingEntry(10309, TCP) failed with code 714 (NoSuchEntryInArray)

2019-12-04 04:18:46.743 ERROR NET: UPNP failed to map WebRTC port 10309

2019-12-04 04:18:46.743 INFO NET: Successfully set up Dual-Stack socket, using both IPv4 and IPv6

2019-12-04 04:18:46.744 INFO NET: Listen to IPv6 on port 10308

2019-12-04 04:18:46.744 INFO Dispatcher: loadMission C:\Users\<user>\Saved Games\DCS.openbeta_server\Missions\<mission file>"

2019-12-04 04:18:46.744 INFO WORLDGENERAL: loading mission from: "C:\Users\<user>\Saved Games\DCS.openbeta_server\Missions\<mission file>"

2019-12-04 04:18:47.306 INFO NET: Loading mission: "C:\Users\<user>\Saved Games\DCS.openbeta_server\Missions\<mission file>"

2019-12-04 04:18:47.307 INFO NET: Registering server as <public IPv4 address>:10308 (port is assumed to be open)

My Rig:

 

 

CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz.

Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD

DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD.

Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.

 

 

Link to comment
Share on other sites

  • ED Team

It's very strange, I answered yesterday ticket in Tech. Support with similar issue (v4 and v6 conflict on server) and net.force_ipv4_lan = true helps.

 

Will consult with programmers.

Men may keep a sort of level of good, but no man has ever been able to keep on one level of evil. That road goes down and down.  
Можно держаться на одном уровне добра, но никому и никогда не удавалось удержаться на одном уровне зла. Эта дорога ведёт вниз и вниз.

G.K. Chesterton

DCS World 2.5: Часто задаваемые вопросы

Link to comment
Share on other sites

Thanks Rik,

 

I updated to the newest Open Beta earlier this morning on the server.

Haven’t had a chance to test client yet, but the server logs don’t look any different,

the entry about dual stack and listen on ipv6 are still there.

My Rig:

 

 

CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz.

Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD

DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD.

Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.

 

 

Link to comment
Share on other sites

  • ED Team
net.force_ipv4_lan = true
Sorry, this advise was not quite correct. Forcing IP v4 is applicable for DCS clients only. Server always listen both v4 and v6 protocols.

 

Secondly, VC now works only by v4 (work in progress).

 

Note (just by the way). If your server forced another port than default (using webrtc_port parameter) your clients also have to use the same port. I.e. all clients have to add webrtc_port = XXXXX into their autoexec.cfg (already fixed in internal version but not tested properly and not ready to release in OB).

Men may keep a sort of level of good, but no man has ever been able to keep on one level of evil. That road goes down and down.  
Можно держаться на одном уровне добра, но никому и никогда не удавалось удержаться на одном уровне зла. Эта дорога ведёт вниз и вниз.

G.K. Chesterton

DCS World 2.5: Часто задаваемые вопросы

Link to comment
Share on other sites

Rik,

 

Useful information for future reference, thank you.

We are using standard 10308 and 10309 - I saw the note about alternate ports but didn’t want to put clients through having to make a configuration change.

 

Can you make sure that when IPv6 support is ready, it’s in the changelog?

I’ll remove the autoexec line at that time and give it a test!

 

c0ff,

 

Thank you for this option - I have restarted my server with it, and the log now states listening on IPv4 with no mentions of dual-stack or IPv6. I’ll have to test later but I am fairly confident based on the logs that it will work.

My Rig:

 

 

CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz.

Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD

DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD.

Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.

 

 

Link to comment
Share on other sites

Follow up on my previous post, with the net.use_ipv6 = false code in the autoexec the server as expected does not respond to it's IPv6 address but also it not listed in the server browser from the LAN. I had a friend verify that it is still listed from the WAN side.

 

Is there any solution for that? Not a critical issue, I can still connect manually. Just a matter of convenience.

 

Thanks!

My Rig:

 

 

CPU: i9-9900k - Corsair H150 Cooler. RAM: 32GB, 3200Mhz.

Mobo: Asus MAXIMUS Formula XI - Main Drive: 512GB NvME SSD

DCS Drive: 512GB NvME SSD - Graphics: GTX 1070 Ti. Display: 23" 1080p LG LCD.

Input: Razer Naga & Blackwidow Ultimate, TrackIR 5, HOTAS Warthog & MFDs (x4), Saitek Rudder Pedals, TurtleBeach PX22 Headset.

 

 

Link to comment
Share on other sites

  • 1 month later...

Greetings,

 

I currently have a minor issue and not sure if the above will also help me. Am have two PCs, the 'upstairs' PC runs a stand-alone DCS Open-beta server. All that join have no issues talking to each other via voice-chat. I fly with them using my 'downstairs PC', but only my name shows on the voice-chat.

 

It appears to have something to do with the way I am connected to the 'upstairs PC', verses everyone else (outside connections). I would like to mention, that when I use the 'downstairs PC' as the server PC, I can connect with everyone else.

 

How do I connect with the others, when using the 'Upstairs PC' is the separate server?


Edited by brindle
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...