Command and Conquer: Renegade Official Forums: Other Products » Brenbot-135 linux problem with renguard

Home » Tiberian Technologies / Blackhand Studios » Other Products » Brenbot-135 linux problem with renguard

Show: Today's Messages :: Polls :: Message Navigator

Brenbot-135 linux problem with renguard [message #88764]

Wed, 19 May 2004 15:05

mac
Messages: 1018
Registered: February 2003

Karma:

General (1 Star)
Administrator/General

Hmm, it seems that port 4853/tcp is not setup in brenbot.cfg

try connecting manually to the wrapper
ie telnet localhost 4853 - it should work.

Be sure your brenbot.cfg has right port.

EkkoTheGekko

ok brenbot is working now Very Happy

thnx for the help on that one

but it can't connect to the wrapper. This is wat happens when i start the wrapper:

Renegade Server Wrapper 0.3 (c) 2003-2004 by Blackhand Studios
Opening TCP Port 4853
Started Server with pid 2464
Renegade Free Dedicated Server v1.037 GU-838 03/01/2003 - 19:00:34
Console mode active
*** Auto starting game. Type 'quit' to abort ***
Initializing LAN Mode
Applying server settings
Channel created OK
Loading level C&C_Islands.mix
Load 0% complete
Load 10% complete
Load 19% complete
Load 27% complete
Load 34% complete
Load 41% complete
Load 46% complete
Load 52% complete
Load 57% complete
Host: Teams have been swapped.
Load 100% complete
Level loaded OK
Initializing GameSpy Q&R
GameSpy mode active since Wed May 19 22:29:38 2004
Gameplay Pending
Map : C&C_Islands.mix
Time : 0.30.00
Fps : 50
GDI : 0/20 players 0 points
NOD : 0/20 players 0 points

To me it seems that the wrapper works. Only I can't use any of the commands like game_info.

This is what brenbot-135 says:

Starting up renrem thread...
BRenBot 1.35 linux.
brenbot is Copyright 2003-2004 by Blackhand Studios. All Rights reserved.
Connecting to RenGuard...
Could not load ssc_ignore.txt - No users are being ignored by RenGuard!
Got serverlist..
Sending to ... 130.89.165.71:25400
Opening server port ...
IRC Initialization...joining irc.n00bstories.com:6667
my nick is Dragoncave_linux
Setting up protected nickname thread...
Setting irc refresh thread...
Can't connect to LFDS Wrapper!
Connected to RenGuard.
Connecting to IRC... waiting for welcome message
Got Server Welcome Message...
Identifying with NickServ...
Joining IRC Channel...
Connection to renrem not possible. Can't send msg BlazeRegulator/BlazeRenBot 1.3
5 linux starting up...
Connection to renrem not possible. Can't send game_info
Connection to renrem not possible. Can't send player_info
IRC: Dragoncave_linux :+wx
IRC: Dragoncave_linux!Dragoncave@n00b-37CC13A5.student.utwente.nl joined #dragon
cave_linux
IRC: Dragoncave_linux changed to #dragoncave_linux
Can't connect to LFDS Wrapper!
Can't connect to LFDS Wrapper!
Can't connect to LFDS Wrapper!
Can't connect to LFDS Wrapper!
Can't connect to LFDS Wrapper!
Connection to renrem not possible. Can't send player_info
Can't connect to LFDS Wrapper!
Can't connect to LFDS Wrapper!
Can't connect to LFDS Wrapper!
Can't connect to LFDS Wrapper!

Anyone has a suggestion????

Quote:

danpaul88: buggy bugs brenbot because buggy befriends brainlessness

Report message to a moderator

[Message index]

		Brenbot-135 linux problem with renguard By: EkkoTheGekko on Tue, 18 May 2004 11:26
		Brenbot-135 linux problem with renguard By: mac on Tue, 18 May 2004 14:24
		Brenbot-135 linux problem with renguard By: EkkoTheGekko on Tue, 18 May 2004 14:39
		Brenbot-135 linux problem with renguard By: mac on Tue, 18 May 2004 14:48
		Brenbot-135 linux problem with renguard By: Ladios on Wed, 19 May 2004 04:20
		Brenbot-135 linux problem with renguard By: EkkoTheGekko on Wed, 19 May 2004 13:35
		Brenbot-135 linux problem with renguard By: mac on Wed, 19 May 2004 15:05
		Brenbot-135 linux problem with renguard By: EkkoTheGekko on Thu, 20 May 2004 03:54

Previous Topic:	Brenbot 1.35 for linux bug
Next Topic:	Possible bug Brenbot

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Oct 21 04:36:15 MST 2025

Total time taken to generate the page: 0.00776 seconds