[bf1942] punkbuster (was: BF2 demo: Random freezing)

[Luke]

My server is still getting 'there is a problem with your connection' when
PB is enabled..... is it just me, or are there others who still can't
figure out why?

Luke

Luke said:
> oops. there are two files needed: pbsv.cfg and pbsvlog.cfg
>
> both are attached and here is the code:
>
> copy this into a text file called pbsv.cfg and place it in your 'bf2/pb'
> folder
>
> --------begin code---------------
> ;Auto Generated by PunkBuster Server
> pb_sv_MsgPrefix "PunkBuster Server" //[PB Message Prefix
> (default=^3PunkBuster Client)]
> pb_sv_MaxDlRate 8 //[KB/sec requested per file (default=4)] changed from 4
> pb_sv_MaxConDls 3 //[concurrent downloads (default=1)] changed from 1
> PB_SV_UpdateGrace 960 //[seconds that pb allows a player to update
> (default 600)] - added this cvar
>
> pb_sv_KickLen 5 //[minutes (default=2)] changed from 2
>
> pb_sv_CvarFreq 1 //[# of range checks per minute] changed from 6
> pb_sv_CvarLogging 2 //[1=Reg. Log, 2=Var Log, 3=Both, 0=Neither] changed
> from 1
> pb_sv_CvarWalk 0 //[0=disabled, 1-4=Walk through obtained Cvar lists]
> changed from 1
> pb_sv_CvarUserPulse 15 //[How often (in min.) to auto-send CvarUser
> command] changed from 99
> pb_sv_CvarChangedPulse 15 //[How often (in min.) to auto-send CvarChanged
> command] changed form 99
>
> //log settings
> pb_sv_CQC 1 //[0=No, 1=Yes (default=1)]
> pb_sv_LogSync 0 //[0=No, 1=Yes (default=0)]
> pb_sv_LogCeiling 5000 //[High log filename serial #] changed form 1000
>
> //screen shot settings
> pb_sv_SsFloor 1 //[Low screenshot filename serial #]
> pb_sv_SsCeiling 100 //[High screenshot filename serial #]
> pb_sv_SsCmd "" //[Filename of system command to run after screenshots]
> pb_sv_SsWidth 320 //[Requested pixel width of remote screenshots]
> pb_sv_SsHeight 240 //[Requested pixel height of remote screenshots]
> pb_sv_SsXpct 50 //[Percentage across screen for remote screenshots]
> pb_sv_SsYpct 50 //[Percentage down screen for remote screenshots]
> pb_sv_SsSrate 1 //[Sample Rate for remote screenshots]
> pb_sv_SsDelay 0 //[Maximum delay client waits before capturing screenshot]
> pb_sv_SsPath "" //[Path where remote screenshots are saved]
> pb_sv_AutoSsFrom 60 //[Minimum # of seconds to wait before requesting next
> ss]
> pb_sv_AutoSsTo 1200 //[Maximum # of seconds to wait before requesting next
> ss]
> pb_sv_AutoSs 0 //[0=No, 1=Yes (default=0)] 0= screen shots off
>
> //pb scanner settings
> pb_sv_Sleep 60 //[# of Milliseconds (default=60)]
> pb_sv_PowerMin 10 //[power points]
> pb_sv_PowerDef 1 //[power points]
> pb_sv_PowerKickLen 5 //[minutes (default=5)]
>
> //pb web settings
> pb_sv_httpPort 0 //[port #]
> pb_sv_httpAddr "" //[external IP Address]
> pb_sv_httpRefresh 30 //[seconds]
> pb_sv_httpKey "" //[key]
> pb_sv_httpMaps "" //[map list (separate by spaces)]
>
> //pb monitored game settings
> pb_sv_scoreKick 0 //[minimum score (negative)]
> pb_sv_changePeriod 999 //[seconds]
> pb_sv_changeMax 1 //[max name changes allowed]
> pb_sv_dupNameGrace 0 //[seconds]
> //Badname List - pb_sv_badname [grace_period_secs] [disallowed text]
>
> pb_sv_autoUpdBan 0 //[0=No, 1=Yes (default=0)]
> pb_sv_extChar 1 //[0=No, 1=Yes (default=0)]
> pb_sv_guidRelax 2 //[1=UNKN, 2=WRONGIP, 4=DUP (add desired values)]
> pb_sv_load pbsvlog.cfg //load remote logging settings (if pbsvlog.cfg
> exists)
>
> //cvars to check
> ;Cvar Range List - pb_sv_cvar [cvar_name] [type] [value(s)]
> pb_sv_cvarempty
> ----end code---------
>
> copy this into a text file called pbsvlog.cfg and enter it into your
> 'bf2/pb' folder
>
> ----begin code-----
> pb_sv_LogUser "" //[remote_log_username]
> pb_sv_LogPw "" //[remote_log_password]
> pb_sv_LogAddr "" //[remote_log_address]
> pb_sv_LogPort 24389 //[remote_log_port]
> ---end code--------
>
> Luke
>
> InCisT said:
>> Luke wrote:
>>
>>>Attached are two config files I worked on which elliminate the
>>> 'connection
>>>interrupt' issues (at least on my 32-bit Linux binary) - according to my
>>>testing - that I and other admins were having when PB is enabled.
>>>
>>>It would be great to get other admins to test these configs out as well
>>>and report if their connection problems (related to PB) are ellinated as
>>>well.
>>>
>>>Place the two files in your 'bf2/pb' folder and restart the server.
>>>
>>>If the attachments dont go through, I will copy the code into another
>>> email.
>>>
>>>Luke
>>>
>>>Luke said:
>>>
>>>
>>>>To be honest, I am not a PB expert - and there are ususally a lot of
>>>>
>>>>
>>>settings that can be tweaked. I am hoping that EvenBalance releases some
>>>documentation for BF2 or that someone on this list who is more
>>>experienced with PB can offer some insight.
>>>
>>>
>>>>Otherwise, I am going to add this to my server, enable Pb and see how
>>>> it
>>>>
>>>>
>>>goes....
>>>
>>>
>>>>Luke
>>>>
>>>>ScratchMonkey said:
>>>>
>>>>
>>>>>--On Friday, June 17, 2005 7:47 AM -0500 Luke <luke at techfreak.org>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Teh 'basic' fix for COD was to
>>>>>>write a config file called 'pbcl.cfg' located in the PB folder and
>>>>>> enter
>>>>>>'pb_sv_CvarWalk 0' - this elliminated the connection interrupts for
>>>>>> COD.
>>>>>>
>>>>>>
>>>>>I'm guessing that disables PB's check that program variables aren't
>>>>> being
>>>>>messed with at runtime. Is there a way to just reduce the priority
>>>>> without
>>>>>disabling it altogether?
>>>>>
>>>>>
>> The pbsv.cfg made it thru, is there another file too?
>>
>
>
> --
> Blessed are the geeks: for they shall inherit the earth.


-- 
Blessed are the geeks: for they shall inherit the earth.