Re: [hlds] 2008 R2 Timer Resolution
At 03:13 PM 3/12/2011, Munra wrote: What's resource usage on say an 600 fps server with HPET enable compared to it disabled. Or will resource usage be simply based on the configuration of the game server itself? You don't need high FPS. You only need 66fps with 66 tickrate (hz) on the OrangeBox engine. Anyone who says you need high FPS on the orangebox engine has an electrical fire in their heads. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Source RCON Protocol
I have extremely simple/naive implementation in python here you can compare against: http://nemu.pointysoftware.net/cacti/scripts/rcon.py I would recommend using one of the working implementations mentioned and compare the wireshark output to yours - Neph On 03/13/2011 11:21 AM, Brett Powell wrote: The protocol listed on http://developer.valvesoftware.com/wiki/Source_RCON_Protocol seems to be a little bit outdated. I am trying to replicate the protocol in a C# NET application (will run along side srcds.exe to allow me to reroute my server's RCON for security). When I reply to an Authorization request, I write the packet as Packet Size (4 bytes - Doesn't Including itself) Request ID (4 bytes) Auth Response : Value is 2 (4 bytes) then the two NULL terminated strings. I have tried both excluding and including the Packet Size inside of the Packet Size (so I have tried with the first value being 10 and 14) and neither works. So is the RCON Protocol on the Wiki outdated or am I doing something wrong? ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Source RCON Protocol
I don't know how C# handles strings like "\0".
Depending on the language this might result in the packet's data payload
being "\0\0" (if the languages takes the strings "literally", like Ruby or
PHP) or "\0\0\0\0" (if the languages uses 0-terminated strings, like Java or
C++).
You should always use Wireshark or something like that to check the packets
produced by your code.
2011/3/14 Brett Powell
> Hey Sebastian, thanks for the information. After messing with it some
> more, it isn't making much sense. It seems if I set the Packet Size on
> the SERVERDATA_AUTH_RESPONSE packet to any value smaller than what it
> should be, it authenticates.
>
> writer.Write((int)12);
> writer.Write(RequestID);
> writer.Write((int)RCONPacket.RCONDATA_sent.SERVERDATA_AUTH_RESPONSE);
> writer.Write("\0");
> writer.Write("\0");
>
> When I send that, it fails, but if I change the first Byte to 10, 8, or
> anything smaller it seems to work. I am printing out the length of the
> full packet, and it is 16 bytes, so without the 4 for the Packet Size
> byte, it should be 12. This has left me very confused.
>
> @Ronny - According to the RCON documentation, in the
> SERVERDATA_AUTH_RESPONSE packet both strings should be null I think.
> Same case seems to apply. Adding the password to String1 in the response
> packet makes it 20 bytes. When I set the Packet Size (first byte of the
> packet) to 16 (full packet size - 4) it fails. Anything smaller than 16
> and it says it authenticated.
>
> On 3/13/2011 2:36 PM, Sebastian Staudt wrote:
> > The Wiki page is not outdated. I have three working implementations
> (Ruby, Java and PHP) for my Steam Condenser project (
> http://koraktor.de/steam-condenser) based on the VDC docs.
> >
> > There are some tripwires though, especially when it comes to long server
> responses.
> >
> > There's also a fork of Steam Condenser (
> http://github.com/txdv/steam-condenser) trying to implement it for C#. So
> you might want to take a look at that too.
> >
> > Best regards,
> > Sebastian
> >
> > Am 13.03.2011 um 19:21 schrieb Brett Powell :
> >
> >> The protocol listed on
> >> http://developer.valvesoftware.com/wiki/Source_RCON_Protocol seems to
> be
> >> a little bit outdated.
> >>
> >> I am trying to replicate the protocol in a C# NET application (will run
> >> along side srcds.exe to allow me to reroute my server's RCON for
> security).
> >>
> >> When I reply to an Authorization request, I write the packet as
> >>
> >> Packet Size (4 bytes - Doesn't Including itself)
> >> Request ID (4 bytes)
> >> Auth Response : Value is 2 (4 bytes)
> >>
> >> then the two NULL terminated strings. I have tried both excluding and
> >> including the Packet Size inside of the Packet Size (so I have tried
> >> with the first value being 10 and 14) and neither works.
> >>
> >> So is the RCON Protocol on the Wiki outdated or am I doing something
> wrong?
> >>
> >>
> >> ___
> >> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> >> http://list.valvesoftware.com/mailman/listinfo/hlds
> >
> > ___
> > To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> > http://list.valvesoftware.com/mailman/listinfo/hlds
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
>
___
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
Re: [hlds] Source RCON Protocol
Hey Sebastian, thanks for the information. After messing with it some
more, it isn't making much sense. It seems if I set the Packet Size on
the SERVERDATA_AUTH_RESPONSE packet to any value smaller than what it
should be, it authenticates.
writer.Write((int)12);
writer.Write(RequestID);
writer.Write((int)RCONPacket.RCONDATA_sent.SERVERDATA_AUTH_RESPONSE);
writer.Write("\0");
writer.Write("\0");
When I send that, it fails, but if I change the first Byte to 10, 8, or
anything smaller it seems to work. I am printing out the length of the
full packet, and it is 16 bytes, so without the 4 for the Packet Size
byte, it should be 12. This has left me very confused.
@Ronny - According to the RCON documentation, in the
SERVERDATA_AUTH_RESPONSE packet both strings should be null I think.
Same case seems to apply. Adding the password to String1 in the response
packet makes it 20 bytes. When I set the Packet Size (first byte of the
packet) to 16 (full packet size - 4) it fails. Anything smaller than 16
and it says it authenticated.
On 3/13/2011 2:36 PM, Sebastian Staudt wrote:
> The Wiki page is not outdated. I have three working implementations (Ruby,
> Java and PHP) for my Steam Condenser project
> (http://koraktor.de/steam-condenser) based on the VDC docs.
>
> There are some tripwires though, especially when it comes to long server
> responses.
>
> There's also a fork of Steam Condenser
> (http://github.com/txdv/steam-condenser) trying to implement it for C#. So
> you might want to take a look at that too.
>
> Best regards,
> Sebastian
>
> Am 13.03.2011 um 19:21 schrieb Brett Powell :
>
>> The protocol listed on
>> http://developer.valvesoftware.com/wiki/Source_RCON_Protocol seems to be
>> a little bit outdated.
>>
>> I am trying to replicate the protocol in a C# NET application (will run
>> along side srcds.exe to allow me to reroute my server's RCON for security).
>>
>> When I reply to an Authorization request, I write the packet as
>>
>> Packet Size (4 bytes - Doesn't Including itself)
>> Request ID (4 bytes)
>> Auth Response : Value is 2 (4 bytes)
>>
>> then the two NULL terminated strings. I have tried both excluding and
>> including the Packet Size inside of the Packet Size (so I have tried
>> with the first value being 10 and 14) and neither works.
>>
>> So is the RCON Protocol on the Wiki outdated or am I doing something wrong?
>>
>>
>> ___
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> http://list.valvesoftware.com/mailman/listinfo/hlds
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives, please
> visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
___
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
