UDP Data for Console-based Plugin

jdtzn

1RPM
Apr 14, 2019
1
0
30
Is there anything special that has to be done to get acServer to send UDP data to a plugin?

Here is a snippet from server_cfg.ini:

UDP_PORT=9600
TCP_PORT=9600
HTTP_PORT=8081
UDP_PLUGIN_LOCAL_PORT=11000
UDP_PLUGIN_ADDRESS=127.0.0.1:10000

I've been running the python project at https://github.com/mathiasuk/ac-pserver
but not getting any output when listening on either port 10000 or 11000.

My firewall is disabled, and I am running pserver.py on the same machine as acServer.exe.

Also when I run netstat to see what ports acServer is listening on, the only (UDP) ports listed are 9600 and (sometimes) 27036.


$ netstat -a -v -b | grep -B 1 acServer
TCP 0.0.0.0:8081 EC2AMAZ-FGB6RC1:0 LISTENING
[acServer.exe]
TCP 0.0.0.0:9600 EC2AMAZ-FGB6RC1:0 LISTENING
[acServer.exe]
--
TCP 172.31.20.64:8081 46:50127 ESTABLISHED
[acServer.exe]
TCP 172.31.20.64:8081 83-81-49-25:57907 ESTABLISHED
[acServer.exe]
TCP 172.31.20.64:8081 host212-250-dynamic:61789 ESTABLISHED
[acServer.exe]
TCP 172.31.20.64:8081 89-95-214-168:59015 ESTABLISHED
[acServer.exe]
TCP 172.31.20.64:8081 159-255-236-152:52894 ESTABLISHED
[acServer.exe]
TCP 172.31.20.64:8081 host-176-41-54-54:63802 ESTABLISHED
[acServer.exe]
TCP 172.31.20.64:8081 ZG095207:60665 ESTABLISHED
[acServer.exe]
--
TCP 172.31.20.64:50397 93-57-10-21:http ESTABLISHED
[acServer.exe]
--
TCP [::]:8081 EC2AMAZ-FGB6RC1:0 LISTENING
[acServer.exe]
TCP [::]:9600 EC2AMAZ-FGB6RC1:0 LISTENING
[acServer.exe]
--
UDP 0.0.0.0:9600 *:*
[acServer.exe]
--
UDP [::]:9600 *:*
[acServer.exe]



I have also used LiveTcpUdpWatch to record UDP transmissions, and it only shows UDP transmissions coming from port 9600, and they all go to other machings (none to 127.0.0.1) and none of them are sent to ports 10000 or 11000.



Is there anything else required in the server_cfg.ini to enable this UDP connectivity? For example, is some [PLUGIN_0] section required?

Does acServer.exe automatically start sending data on UDP to the appropriate location, or does it only start sending data on UDP after it receives a packet (a CSP_REALTIMEPOS_INTERVAL packet, for instance)? Or does at least one car have to be loaded into the session?