This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I have tried all I can to re-enable VAC on my CS 1.6 server. It was running
fine with VAC and then a friend pointed out it no longer was secure, I don't
know exactly when it happened. I did a yum update on my server and think it
may have been after that. The only error I can find when I start it up is:

cminterface.cpp (588) : Assertion Failed: NULL != m_hConnection

I'm running Fedora 4 behind a Sprint ZyXEL 645 Series modem/bridge bridged
with a static ip, and a Linksys WRT54GS. Ports 27015 and 27016 tcp and udp
both forwarded, the Fedora firewall opened up on those ports also. I
originally only had 27015 forwarded and all was fine then after finding it
was insecure and researching I also did 27016 and added -sport 27016 to my
start up which is:

./hlds_run -game cstrike -sport 27016 +map de_dust +maxplayers 10 +exec
server.cfg +log on -debug + sv_lan 0

The server runs fine and is available to all 65.40.144.4:27015 UPlayHere CS
1.6 and on my LAN it just will not secure with VAC.

Another problem I'm having is:

Enabling debug mode

./hlds_run: line 141: gdb: command not found

Please install gdb first.

goto http://www.gnu.org/software/gdb/

I have tried and tried and can not get gdb to do anything. I can usually
follow instruction pretty well but this has got me beat. I'm a cut and paste
from tutorials Linux user so if you get too technical I'll get lost and ask
silly questions BUT I am a fast learner and good at researching my own
problems and fixing them. I'm not too concerned with gdb unless someone here
tells me it is necessary to trouble shoot the VAC not working problem.

I don't know what other information is relevant to post to assist in getting
an answer, just ask and I'll provide.

Thanks in advance,

MR. S.

--



_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to