Jump to content


[Problem] L4D v1.0.1.5 + Rev Patcher + SETTI = Fail


  • Please log in to reply
30 replies to this topic

#1 Guest_

Guest_
  • Guests

Posted 20 October 2009 - 06:03 PM

Hi, I have 7 servers L4D. When server there were versions 1.0.1.4, I used for breaking RevEmu/VUP and a server were perfectly displayed in SETTI. After updating of servers to version 1.0.1.5, I began to use for breaking REVOLUTiON Source Engine Patcher v1.3b and now a server have ceased to be displayed in SETTI.

IP my servers:

84.22.140.86:27015
84.22.140.86:27016
84.22.140.86:27017
84.22.140.86:27018
84.22.140.86:27019
84.22.140.86:27025
84.22.140.86:27027

Very much I want that server were displayed in SETTI, but thus I wish to use for breaking REVOLUTiON Source Engine Patcher v1.3b, instead of RevEmu/VUP.

Thankful in advance.

Sorry for my english http://css.setti.inf...tyle_emoticons/default/icon_redface.gif

#2 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 20 October 2009 - 09:10 PM

Revolution source engine patcher is probably old. You should update the patch just as you update your game.

There has been some talk about how server patches should work. Rev crew probably have the best idea how things should work.

#3 Guest_

Guest_
  • Guests

Posted 21 October 2009 - 08:02 AM

Thanks for the answer. Simply RevEmu works astably (as it the emulator, and emulators always worked worse than idle time patcher): the server can fall, can be gameplay problems. VUP it is bad that gives out absolutely to all (owners of licences, standalone clients, Cracked Steam) identical SteamID kind STEAM_1:0:0 - agree, that it is not so good. And here Rev Patcher both works stably, and gives out to owners of their licences real SteamID, and standalone to clients accordingly identical STEAM_1:0:0. Yes, it old (2007), but works much better than its present analogues. But all the same thanks for the answer. It is a pity that with it nothing can be made.

P.S.: badly that the version 1.3b last also was not updated any more. Though even without updatings works perfectly.

#4 Guest_

Guest_
  • Guests

Posted 26 October 2009 - 05:56 PM

Hi,

There's some problem with the latest version 1.0.1.5 l4d server.

One of my servers (linux + rev-emu 2.7RC1) also shows itself offline at http://css.setti.inf....140.73.87:4500 , but it's responding ok to basic a2s queries:

quakestat -a2s 89.140.73.87:4500

ADDRESS           PLAYERS      MAP   RESPONSE TIME    NAME

89.140.73.87:4500      3/ 4 l4d_garage02_lots     13 / 0  left4dead L4D digitaleden #1[SPAIN][COOP][CUSTOM MAPS]

quakestat -a2s 89.140.73.87:4500 -P

ADDRESS           PLAYERS      MAP   RESPONSE TIME    NAME

89.140.73.87:4500      3/ 4 l4d_garage02_lots     15 / 1  left4dead L4D digitaleden #1[SPAIN][COOP][CUSTOM MAPS]

         10 frags  2h18m46s Zoey

         19 frags    21m31s [BE]Weedheads

          7 frags    22m41s [FI]HULK

         16 frags  1h27m37s [VE]Makako

quakestat -a2s 89.140.73.87:4500 -R

ADDRESS           PLAYERS      MAP   RESPONSE TIME    NAME

89.140.73.87:4500      3/ 4 l4d_garage02_lots      6 / 1  left4dead L4D digitaleden #1[SPAIN][COOP][CUSTOM MAPS]

        protocol=7,gamedir=left4dead,gamename=L4D - Co-op - Advanced,dedicated=1,sv_os=linux,secure=1,version=1.0.1.5,coop=0,deathmatch=1,sv_cheats=0,sv_contact=ToDieFor,sv_password=0,sv_steamgroup=,sv_tags=DIGITALEDEN,NON-STEAM,SPAIN,sv_voiceenable=1,tv_password=0,tv_relaypassword=0


notice that rules query is truncated (bug introduced by valve with last update). Can some admin inspect setti logs to see the reason to show it offline?

#5 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 26 October 2009 - 10:04 PM

The server starts to show offline if it's not patched. Have you upgraded your server and forgot to patch it again?

PS. The "bug" about truncated rules is probably "bug" in qstat because Valve updated the rules reply (and every other reply) in the engine so that the reply is bzip2'd before sent if it can't fit into one packet.

#6 Guest_

Guest_
  • Guests

Posted 27 October 2009 - 07:03 AM

Yes, its patched with rev-emu.

The weird thing is that i run 2 fork instances over the same process (-fork 2). The other instance is shown online here http://css.setti.info/stats/servers/ser ... 73.87:4501 , and of course both of them share libraries and engine.

#7 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 27 October 2009 - 07:39 AM

It's been fixed now manually, but it is very much possible that it will be automatically removed from the list soon. Your other server is also going to be removed soon unless it accepts the test client from Setti to join.

#8 Guest_

Guest_
  • Guests

Posted 27 October 2009 - 08:06 AM

I saw is was rejected with some error message (STEAM certificate length error, i think). Clients using latest rev-emu can join, can i ask which patch use you test user?

Thanks for the help.

#9 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 27 October 2009 - 09:48 AM

Do you have latest rev patch? Rev crew is updating their patches so often and they make them incompatible with each other on purpose, so make sure you keep the old clients allowed if you update.

#10 Guest_

Guest_
  • Guests

Posted 27 October 2009 - 01:23 PM

Im using currently the latest version. 2.7RC1. Just for test, i have also installed the previous one (2.6).

I get this with both of them:

RejectConnection: 188.40.40.201:35146 - STEAM certificate length error! 0/2048

The problem is that those two versions are the only ones working with the latest 1.0.1.5 l4d version. i think most if not all of the linux server for l4d out there are using one of these 2 versions of rev-emu.

Support for old versions is configured as usual.

#11 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 27 October 2009 - 01:43 PM

Have you enabled all the stuff in the patcher? There are few 1.0.1.5 L4D servers in the server list. They might or might not be using Rev emu.

#12 Guest_

Guest_
  • Guests

Posted 27 October 2009 - 01:56 PM

Config is almost default:

# Enable server logging to log all connections to your server.

# This option will also save UserID tickets.

# NOTE: UserID tickets of legitimate users will not be saved

# if ExternalModule setting is used!

# If this is not configured, logging will be disabled.

#

#Logging

# Use the ExternalModule setting to enable STEAM features

# such as VAC, Valve Master Server communication, etc.

# If this is not configured, the server will not be VAC secured,

# and will not be listed on Valve master server.

# Also, if this is not configured, the server will be invisible

# for some server browsers like HLSW.

# To use this setting correctly, you need to specify the path

# to the original Valve's steamclient library

#

ExternalModule=steamclient_linux.so.orig

# Enable the VUP mode to enable only basic revEmu features

# to prevent "No Steam logon" and such error messages.

# Use this setting only if you use VUP/eSTEAMATiON by vityan666.

# VUP mode is disabled by default.

# NOTE: ExternalModule is required for this setting to work!

#

#VUP



# Use DisableUnlockedItems to disable unlocked items for Team Fortress 2.

# If these are disabled, users will not be able to use the new weapons.

# If this is not configured, all new weapons will be unlocked.

#

DisableUnlockedItems



######### GameServer policy rules #########



# "OldEmu" clients are clients who use revEmu v9.63 ~ v9.73.

# Really old clients (v9.62 and below) are rejected anyway.

# If these are not configured, the server will reject all,

# except the latest revEmu clients

#

AcceptOldEmu

AcceptCracked

AcceptLegit

AcceptUnknown

Just enabled log to see if something can bring some light there. I havent test disabling ExternalModule but thats a must because of hardware based steam ids.

#13 Guest_

Guest_
  • Guests

Posted 13 November 2009 - 04:06 PM

Hi,

i opened a ticket to rev-crew to look into this issue, (details here )

css.setti.info unfortunately does not send any ticket (their "client" ticket length is 0 the way I see it). This error is not revEmu's fault, but setti's fault. The Emu does not reject this client - the game engine rejects it. Nothing to do with revEmu....


hope it helps.

#14 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 13 November 2009 - 06:55 PM

Could you use Wireshark to capture network traffic when you join some server. Try to shut down all other network programs like uTorrent and youtube when you're capturing. Then start Wireshark capture, join any server and then quit. Stop capturing and send the capture dump here.

Thanks.

The core rev crew have probably taken couple of their friends in the crew who don't know so much about the authentication system. At least that's how it seems.

#15 Guest_

Guest_
  • Guests

Posted 14 November 2009 - 08:28 AM

They are taken server side:

- setti_scanner.cap : i submitted 87:4500 server to css list, if becomes online in monitor, then capture the traffic till if showed offline.
- setti_scanner2.cap: the same, but for 87:4501 server
- client_connect_4501.cap: traffic for a succesfull client connection (rev-emu user) to 87:4501 server.

edit: removed capture, if you need it again or something, tell me.

#16 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 14 November 2009 - 10:06 AM

Big thanks. :D

The data seems good. Update coming when it's made into better use.

#17 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 14 November 2009 - 01:05 PM

Thanks. It's now in use.

It's quite weird how the 1.0.1.5 version behaves differently than 1.0.1.6 and the other versions. The 1.0.1.5 version replied "9STEAM certificate length error! 0/2048". For example 1.0.1.6 servers had no problem accepting the previous Setti dummy client userauth ticket.

Here's little update. Maybe someone from Rev Crew (who doesn't use someone else's API but actually knows what he's talking about) can enlighten what is the important part for them:

This is full packet that is copy&pasted from ToDieFor's network capture:

0000   ff ff ff ff 6b f8 03 00 00 03 00 00 00 9f 70 3d  ....k.........p=

0010   0a 50 6c 75 67 6f 75 74 00 00 01 d0 06 9d dd 97  .Plugout........

0020   db db 18 5a 18 1d 00 0c 80 da 5b de 57 58 1d dd  ...Z......[.WX..

0030   5b 58 5a 1b 59 58 1b 5c 99 1b 00 0c 80 5b 58 5b  [XZ.YX......[X[

0040   19 00 14 5b dd d9 5b 1d 1d c0 18 db 57 9a 1b 5d  ...[..[.....W..]

0050   99 1c dc 97 5c 18 5d da 1b 80 0c c0 18 db 17 9c  .....].........

0060   5c 19 59 da 18 1d 40 0c c0 18 db 57 1d 1c 59 18  .Y...@....W..Y.

0070   5d 99 5c 18 5d 19 80 0c 0c c0 1c 5c d9 d8 57 18  ]..]........W.

0080   1b db db 9d dc 5b 58 5b 9a db 19 40 0c c0 18 db  .....[X[...@....

0090   57 db 5b dd 5c 19 db db db 1a 40 0c c0 18 db d7  W.[......@.....

00a0   5c d9 dc 5c da 9b 1b 00 80 dd 5b da 58 d9 17 db  ........[.X...

00b0   db 1b 9c 58 d8 d8 1a 00 0c c0 18 db 17 5b d8 d9  ...X.........[..

00c0   d8 5b 1b 5c 99 db 5c 18 5d da 9b 1b 40 0c c0 18  .[....]...@...

00d0   db db 5c d9 58 18 1c 5d da 9b 1b 40 0c c0 18 db  ...X..]...@....

00e0   17 5b 98 db 59 5d d8 59 19 40 99 db 19 5b da 1c  .[..Y].Y.@...[..

00f0   1a c0 1c 5c d9 d8 d7 58 9a 5b 59 5b 18 5d da 18  ......X.[Y[.]..

0100   00 0c c0 18 db 57 1a 59 59 18 db d7 1c 5c d9 d8  .....W.YY......

0110   57 db 1b 59 19 40 0d 00 5a 18 dc 17 52 d8 1c 51  W..Y.@..Z...R..Q

0120   99 5d da 58 19 00 0c 80 dd 5b da 58 d9 d7 1c 5c  .].X.....[.X...

0130   18 5d 5a 18 5b 9a 5e 19 00 0c 40 99 db 19 5b da  .]Z.[.^...@...[.

0140   1c 1a 40 0c c0 9c 1b d9 57 5b dd 5c da 98 dd 1b  ..@.....W[.....

0150   5b 5d 5b 19 40 0c c0 18 db d7 58 1b 99 5c 18 5d  [][.@.....X...]

0160   19 80 0c 0c 80 5b 19 dd 57 5b 18 9e dc 5b 1d 5d  .....[..W[...[.]

0170   98 18 5b 19 40 8c 0c 0c 0c 80 5c 18 5d 19 80 0c  ..[.@......]...

0180   0c 0c 0c 0c c0 18 db 17 9c 5c 19 59 da 18 dd 5d  ..........Y...]

0190   59 18 dc 9b db 1c 40 0c c0 18 db 57 58 1d dd 1b  Y.....@....WX...

01a0   5a 19 1b 1c 40 0c c0 18 db 57 9a 1b 5d 99 1c dc  Z...@....W..]...

01b0   1b 5b 18 5d 19 40 0c c0 18 db 57 9a 1b 5d 99 1c  .[.].@....W..]..

01c0   1c 00 8c 4b 0c 80 d9 9b dd 17 59 d9 5c 9a 5c 19  ...K......Y...

01d0   19 40 0e 0c 00 00 00 00 00 00 00 00 00 52 00 25  .@...........R.%

01e0   00 00 80 47 ba 7d 74 bb 32 39 00 00 00 00 00 8f  ...G.}t.29......

01f0   74 fb e8 00 00 88 00 99 1b 1c 99 1a 9b 9a 9c 19  t...............

0200   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

0210   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

0220   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

0230   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

0240   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

0250   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

0260   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

0270   00 00 00 00 00 00 00 10 00 00 80 00 00 00 00 00  ................

0280   00 00 80                                         ...

Here's explanation:


HEADER      = ffffffff6b (5 bytes)

GAMEVERSION = f8030000 (4 bytes)

PROTOCOL(?) = 03000000 (4 bytes)

CHALLENGE   = 9f703d0a (4 bytes)
After that the stuff goes more cryptic, but apparently the following piece is the name, which ends in nullbyte. Then there is usually (at least in two separate userauth packets) "00 00 01". Then there's lots of crap that doesn't make sense. Some part of it is probably some use for steam emulators (or do the steam emus redirect it to Steam's authentication servers and wait for reply there?). Anyway, here's what the mystic part is from Setti's eyes:

Name        = [variable length ends in nullbyte, eg. "Plugout"]



???         = 00 (nullbyte)

???         = 01



???????     = something something something probably padded to some length

For example here's clip from the DoOrDie's network capture. Different parts are colored:

ffffffff6b[color=#FF0080]f8030000[color=#FF00FF]03000000[color=#FF80FF]9f703d0a[color=#FF8080]506c75676f757400[color=#FF8000]00[color=#BF8000]01...

#18 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 16 November 2009 - 11:10 AM

@ ToDieFor
Thanks again for the network captures.

It seems that 1.0.1.4 servers are incompatible with this new Userauth ticket / packet (rev crew calls it ticket, but it's still unclear what they really mean by *ticket*). All L4D servers 1.0.1.4 and before have disappeared from the Setti list. This is because they don't accept Setti client anymore. But it's important that updated servers are on the list now.

#19 Guest_

Guest_
  • Guests

Posted 16 November 2009 - 11:13 AM

Thanks man, gj :)

#20 Ghost

Ghost

    Admin

  • Moderators - Admin
  • 3,638 posts
274

Posted 16 November 2009 - 03:58 PM

If you don't mind you could copy&paste the question for Rev Crew from the previous post [ viewtopic.php?p=2695#p2695 ] so that they can share their knowledge if they want to do so.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users