Author Topic: Dedicated server unjoinable on Debian+Wine  (Read 182 times)

imserious

  • Posts: 2
Hello,
I'm having trouble with the dedicated server and I hope to receive some guidance/advice.

Here's how I got the game files on my VPS:
Code: [Select]
$ steamcmd +@sSteamCmdForcePlatformType windows +login username +force_install_dir ~/Wreckfest +app_update 228380 validate +quit
I made sure all the necessary ports are opened (tested with socat): TCP - 27015, 27016 and UDP - 27015, 27016, 33540
Code: [Select]
# iptables -A INPUT -p tcp --match multiport --dports 27015,27016 -m state --state NEW -j ACCEPT
# iptables -A INPUT -p udp --match multiport --dports 27015,27016,33540 -m state --state NEW -j ACCEPT

I installed Wine 3.17.0 on Debian Stretch as per https://wiki.winehq.org/Debian
Tried winehq-staging, winehq-devel, winehq-stable -- server misbehaves the same way

I launch the server this way:
Code: [Select]
$ DISPLAY=:0.0 wine server/Wreckfest.exe -s server_config=server_config.cfgThe config file works fine on my windows PC - I connect and race. The DISPLAY env var points to Xvfb virtual display:
Code: [Select]
# Xvfb :0 -screen 0 1024x768x16X11 ssh forwarding display doesn't change server behavior.

My server shows up in the internet server list, but connection attempts fail asking whether I want to try again... The server listens on UDP 27015 & 27016 ports only upon launch (confirmed via ss/netstat), until I connect to it. Then it shows some more ports (will provide ss output on request)

Code: [Select]
$ DISPLAY=:0.0 wine server/Wreckfest.exe -s server_config=server_config.cfg
0010:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0018:fixme:process:SetProcessShutdownParameters (00000100, 00000001): partial stub.
0018:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0023:fixme:ver:GetCurrentPackageId (0x33fe24 (nil)): stub
0010:fixme:console:SetConsoleScreenBufferInfoEx (0x17 0x53a560): stub!
Commands:
    list - print player list
    bans - print ban list
    admins - print list of user privileges
    clearusers - clear user privileges
    tracks - list tracks
    gamemodes - list game modes
    cars - list cars
    weathers - list weathers
    exit - close application
    ? - list server and event modifiers
Chat commands:
    /message [new message] - send a message to the chat
    /kick [id] - kick a player
    /ban [id] - ban a player
    /bansteamid [steam id] - ban a steam id
    /unban [ban index] - lift a ban, use "bans" for ban indices
    /unbansteamid [steam id] - lift a ban by steam id
    /clearbans - clear all bans
    /balanceteams - balance teams
    /restart - server restart
    /bot - add a bot
    /op [id] - add moderator privileges
    /opsteamid [steam id] - add moderator privileges by steam id
    /admin [id] - add admin privileges
    /adminsteamid [steam id] - add admin privileges by steam id
    /demote [id] - clear admin and moderator privileges
    /demotesteamid [steam id] - clear admin and moderator privileges by steam id
    /password [new password] - set password
    /servername [new server name] - set name of the server
    /welcome [new welcome message] - set the welcome message
    /eventloop - toggle automatic event rotation if configured
* 23:53:18 Starting server...
0010:fixme:ntdll:EtwEventRegister ({47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x3f006d30, 0x3f04c480, 0x3f04c478) stub.
0010:fixme:ntdll:EtwEventRegister ({58a9201e-73b0-42ce-9821-7e134361bc70}, 0x3f006d30, 0x3f04c4b8, 0x3f04c4b0) stub.
0010:fixme:ntdll:EtwEventRegister ({3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x3f006d30, 0x3f04c448, 0x3f04c440) stub.
0010:fixme:ntdll:EtwEventRegister ({1432afee-73b0-42ce-9821-7e134361b433}, 0x3f006d30, 0x3f04c4f0, 0x3f04c4e8) stub.
0010:fixme:ntdll:EtwEventRegister ({4372afee-73b0-42ce-9821-7e134361b519}, 0x3f006d30, 0x3f04c528, 0x3f04c520) stub.
0010:fixme:ver:GetCurrentPackageId (0x519f20 (nil)): stub
Setting breakpad minidump AppID = 228380
* 23:53:20 Server connected to Steam.
And it stays like that until I attempt to join the server:
Code: [Select]
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0084.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 012c.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0130.
0034:fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x55d0a40, 0x1409fa60
STEAMPS3 - AsyncTCPSocket created
STEAMPS3 - AsyncTCPSocket created
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 014c.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0150.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0154.
0034:fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x55d0a40, 0x1409fa60
STEAMPS3 - AsyncTCPSocket created
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 012c.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0130.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0154.
0034:fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x55d0a40, 0x1409fa60
STEAMPS3 - AsyncTCPSocket created
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 014c.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0150.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0154.
0034:fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x55d0a40, 0x1409fa60
STEAMPS3 - AsyncTCPSocket created
STEAMPS3 - AsncTCPSocket destroyed
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0084.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0130.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 013c.
STEAMPS3 - AsncTCPSocket destroyed
0034:fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x55d0a40, 0x1409fa60
STEAMPS3 - AsyncTCPSocket created
STEAMPS3 - AsncTCPSocket destroyed
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0134.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 014c.
0034:err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0150.
0034:fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x55d0a40, 0x1409fa60
STEAMPS3 - AsyncTCPSocket created
STEAMPS3 - AsncTCPSocket destroyed
STEAMPS3 - AsncTCPSocket destroyed
STEAMPS3 - AsncTCPSocket destroyed
STEAMPS3 - AsncTCPSocket destroyed
0038:fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
0038:fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
^C

Tcpdump gives this (capture started at the same time as server): https://bpaste.net/show/b83c221aa730
It's weird that the server bombards the client with 56byte packets at 5 Hz. This happens after the 'do you wanna retry' message pops up.

I'm hoping you could help me out...

imserious

  • Posts: 2
Not getting any suggestions from developer for some reason (incompetence?)

Devin

  • *
  • Posts: 349
I've hosted a 24/7 wine wreckfest server before and I'm partially responsible for the fact that wine is compatible to it in the first place, which means one of the latest versions of wine should support it out of the box, but even if you get it to run there is a nasty wine networking bug that makes it just about impossible to use the server in the end. It simply doesn't work, as much as I'd love it to.

And calling the developer incompetent for not responding is about the worst thing you could do because they sure as hell won't respond faster from that. If anything they will ignore this at all.

You should know that only because there are forums doesn't mean the developers will respond to everything, so no matter how easily resolvable an issue is, it's more or less super rare to get an official response anyway. This is nothing personal, but they develop a game after all, not really that much time to constantly check if people need assistance.

And while they should definitely provide support for issues with the game, it's for the game only. Not for some third party stuff that tries to use the game. This is an issue with wine, not with Wreckfest, therefore they have no reason to provide support (mostly because they probably don't even know themselves what about wine is wrong and how wine works in the first place)

My suggestion: Run it in a windows VM (nested VM is also good enough) and just pass that through