Still disconnecting- UDP port changing causing disco?

[ENO]

After each UDP port change I notice one particular client is continuously disco'd.

 

Does this point to a bug?

 

Crashing consistently since the update today- 7570 I think it is.

 

 

 

03020.160 INFO NET: [4] UDP port changed from 25026 to 32064

03065.504 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-01.bmp

03065.508 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-03.bmp

03065.511 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-02.bmp

03065.515 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrm_b.bmp

03065.518 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrm_centre.bmp

03065.522 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50_st_paint1.bmp

03065.526 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-05.bmp

03065.537 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-06.bmp

03065.549 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrm-1.bmp

03065.553 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrmpart-1.bmp

03065.561 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-04.bmp

03154.015 INFO NET: Lua: Disconnected client [4] "mwooten"

03154.015 INFO NET: remove: client 4

03191.355 INFO NET: client[2] is ready to start

03191.355 INFO NET: spawning client[2]

03191.358 INFO NET: client[2] started

03270.299 INFO NET: Lua: Client [2] "tempus" joined Blue in "Ka-50"(225)

03349.096 INFO NET: client[2] has left the game

03350.174 INFO NET: Lua: Disconnected client [2] "tempus"

03350.174 INFO NET: remove: client 2

03493.374 INFO NET: accepting connection from 92.xxxxx

03493.408 INFO NET: append: client 2

03493.457 INFO NET: Lua: Connected client: id = [2], addr = 92.xxxxx, name = "tempus", ucid = "4bceeb0cxxxxx164122ffa57909b"

03494.721 INFO NET: [2] UDP port changed from 50965 to 53175

03495.515 INFO NET: Lua: Disconnected client [2] "tempus"

03495.515 INFO NET: remove: client 2

03681.723 INFO NET: Lua: Client [3] "Wheel" joined Blue in "Ka-50"(225)

03705.012 INFO NET: accepting connection from 92.xxxxxxxx

03705.048 INFO NET: append: client 2

03705.097 INFO NET: Lua: Connected client: id = [2], addr = 92.xxxxx:51000, name = "tempus", ucid = "4bceeb0c173xxxxx22ffa57909b"

03706.374 INFO NET: [2] UDP port changed from 51000 to 64493

03725.776 INFO NET: Lua: Client [3] "Wheel" joined Blue in "Ka-50"(224)

04060.322 INFO NET: Lua: Disconnected client [2] "tempus"

04060.322 INFO NET: remove: client 2

04065.645 INFO NET: accepting connection from xxxxxxx:51017

04065.663 INFO NET: append: client 2

04065.712 INFO NET: Lua: Connected client: id = [2], addr = 92.15.xxxxx51017, name = "tempus", ucid = "4bceebxxxxxx122ffa57909b"

04066.969 INFO NET: [2] UDP port changed from 51017 to 64494

04127.945 INFO NET: Lua: Disconnected client [2] "tempus"

04127.945 INFO NET: remove: client 2

04155.816 INFO NET: accepting connection from 92xxxxx:51028

04155.827 INFO NET: append: client 2

04155.876 INFO NET: Lua: Connected client: id = [2], addr = 92.xxxxx51028, name = "tempus", ucid = "4bcexxxxxxxx164122ffa57909b"

04157.093 INFO NET: [2] UDP port changed from 51028 to 64495

04443.965 INFO NET: Lua: Disconnected client [2] "tempus"

Logs 11.25.12.zip

Edited November 26, 2012 by ENO

[tempusmurphy]

just to add to this thread , that now I cannot join to Enos server at all ... (since the latest update) it will now hang at the mission loading screen for approx 10 min then gives the "server ping timeout " error I have tried several other servers and can connect to them fine in under 3 mins

 

also the log for the crash looks different to the usual "access violation at location xxxxxx" there seem to be a lot of the"@" symbols

 

 

# -------------- 20121126-220802 --------------

 

# C0000005 ACCESS_VIOLATION at 402934AF 00:00000000

00000000 00000000 0000:00000000

402934AF 0029F100 0000:00000000

4029407E 0029F130 0000:00000000

4028C202 0029F220 0000:00000000

EF215150 0029F300 0000:00000000 ?process_@ActionDispatcher@@AEAAXUActionEntry@@W4ActionOrigin@@I@Z()+60

EF215386 0029F340 0000:00000000 ?dispatch@ActionDispatcher@@QEAAXAEBUActionEntry@@W4ActionOrigin@@I@Z()+16

EF215666 0029F3A0 0000:00000000 ?feedToDispatcher_@ActionSource@@AEAAXAEBV?$vector@VNewInputAction@@V?$allocator@VNewInputAction@@@ed@@@ed@@@Z()+D6

EF216335 0029F400 0000:00000000 ?processInput_@ActionSource@@AEAAXXZ()+75

4026F4B2 0029F490 0000:00000000

40271EDD 0029F4F0 0000:00000000

40289544 0029F520 0000:00000000

40289439 0029F580 0000:00000000

40310998 0029F5F0 0000:00000000

40311DD8 0029FAE0 0000:00000000

403147BF 0029FB90 0000:00000000

7712652D 0029FBC0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

776CC521 0029FC10 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

Edited November 27, 2012 by tempusmurphy

[c0ff]

After each UDP port change I notice one particular client is continuously disco'd.

 

Does this point to a bug?

 

UDP port change is caused by a client's NAT. The log just reflects the current situation.

If DCS had an option to lock client's ports to specific values, then port forwarding could be used to fix the situation. While it's not the case, I can only suggest to try a DMZ option if the router has it.

[Kuky]

damn... just tried some MP and I got 2 "connection interrupted" instances :(

[Dejjvid]

Kuky, you didn't test MP before release?

Sorry just had to. :megalol:

 

So, people with NAT can not connect to a server with the latest update?

[ENO]

More to the point I think it's a continuing problem.

[ENO]

I can only suggest to try a DMZ option if the router has it.

 

Isn't that like sticking your tongue directly on a busy subway turnstile?

 

I suppose we'll soon see how bad guys want to connect lol.

[SkateZilla]

you can assign DMZ to only forward to a Certain internal IP. that way the only thing at risk is a stripped server box with DCS on it, hardly interesting to any intruders.

 

You could Set DMZ for the Server IP. and run software firewall, and monitor what ports DCS/Traffic are trying to access.

 

Why is the DCSW MP code constantly switching ports anyway? shouldnt it be a set range? Does A-10C 1.1.1.x operate the same way?

 

Being able to Set a UDP Port Range for MP in the Server LUAs would prolly resolve the issue,

That way you can open a Specific Port Range on the Router/PortForwrd.

 

and you can instruct people to open those same ports.

 

You wont need to open anymore ports than the max allowed players either.

 

ie:

port = 10300-10350,

 

or

portstart=10300

portend =10350

 

(edit: those are not real lines, i was making an example)

Edited November 27, 2012 by SkateZilla

[ENO]

Okay so the issue is the client is switching to a port the server isn't open to? So I can resolve that on my end by entering those parameters?

[SkateZilla]

those parems are real entries, they are examples for ED, if they wanna program teh ability for server config to control a range, if they already dont have a way to do it.

[Wrecking Crew]

But if the server computer is locked to an IP address in the router's NAT then the server should stay on that address and everything should be fine. ??

 

Wrecking Crew

[SkateZilla]

the IP is fine, its jumping UDP Ports.

[ENO]

Okay Skate- so just let me be clear on your direction here...

 

If those entries are put in on the client side- will that lock the client ports to those you wrote.

 

Or is that a concept that needs to be programmed in on the dev side?

 

 

Edit:

 

So if I set up the DMZ within the router- I can set it to only leave it open from that specific IP address- presumably the DCS Master server list?

Edited November 27, 2012 by ENO

[Dejjvid]

He was just writing a concept. We have no clue if the devs have this feature or not.

[SkateZilla]

it was a concept, those commands dont exist.

 

 

Every router is different,

But both of my main routers (Dlink and Belkin) both offer Setting DMZ to a specific Local IP/HostName/Mac Address.

 

And that Device is moved outside of the routers Firewall / DHCP and shares the Public IP Address, so, no Ports are blocked, and the Computer will receive all incoming data packets on all ports without having to forward them to a specific DHCP Internal IP address.

 

 

It eliminates problems with Router Ports being Closed or having to be forwarded, but its basically the same as a direct connection to the internet, you can run a software firewall, but it will prompt you for a yes/no every time a port switch happens,

 

if it's just a server with Windows and DCS, then it's prolly OK to leave it DMZ for a while to test or until ED allows Servers to specify a Range.

 

Setting it from DMZ will also remove that System from the Local Network. so even if someone were to try getting into that system other systems on the network would be OK and still behind the firewall of the router

Edited November 27, 2012 by SkateZilla

[SkateZilla]

He was just writing a concept. We have no clue if the devs have this feature or not.

 

This kinda makes it sound like the feature/settings arent there.

 

UDP port change is caused by a client's NAT. The log just reflects the current situation.

If DCS had an option to lock client's ports to specific values, then port forwarding could be used to fix the situation. While it's not the case, I can only suggest to try a DMZ option if the router has it.

[SkateZilla]

seems to effect server lists too.

http://forums.eagle.ru/showthread.php?t=98296

 

behind router vs direct connect vs DMZ.

 

 

i know i was unable to connect (sat at loading mission), a week or so ago..

 

so if that happens again tonite, I'll throw my PC to DMZ.

[ENO]

But is it your PC in DMZ that is going to allow the traffic or the server one?

[wild turkey]

Server should be on the DMZ, putting a main computer on a dmz is like taking a hammer to some primers, eventually you're gonna get it in the eye...

 

DMZ like Skate said for the server will allow ANYTHING and EVERYTHING to communicate on ANY port. NAT uses port forwarding(must manually enter port range in both UDP and TCP). Now if you wanna give yourself a headache, You can also set external ports to fwd to internal ports and vice/versa...

[SkateZilla]

Server should be the only System on DMZ.

[St3v3f]

Usually you can only set a single ip as dmz. It means that the router will forward all incoming requests on ports that have no specific forwarding rule set to that ip.

[ENO]

Okay, well I guess my question is:

 

Is that the solution to this UDP port switching issue until it can be fixed? Is the port switching actually creating the problem of disconnection? Could it at LEAST be contributing? Is anyone else experiencing this issue?

[BRooDJeRo]

I must say that im kind of fond of some hardware firewallage and routing before any signal reaches any computer in the network. Turning on DMZ is cool for troubleshooting. Permanent on DMZ is asking for trouble in our homenetwork.

Edited November 28, 2012 by BRooDJeRo

[St3v3f]

Edit: Please excuse this bs posting :)

Edited November 28, 2012 by St3v3f