Community Forums Today's Posts     Member List     Archive    
Results 1 to 3 of 3
  1. #1
    Join Date
    Feb 2004
    Location
    U.K
    Posts
    4

    Server Logging and other ideas

    Hi people,

    This is my first post on here and i'm sure it won't be my last. I have a few ideas which would help server admins to no end.

    The first being server logging of the ip's of people who join the server you run. There's nothing more annoying than having a muppet come onto your server, throw a load of abuse at users and then quickly leave. There's no way of banning them after they have left so the only logical answer would be to have some sort of server ip logging.

    Another idea is those users you ban for abuse and they keep coming back under their different ip's (this applies to dial up and some adsl connections). It would be great if you could ban a block range of ip's rather than just individual ip's, this way then people that have been banned from a server, stay banned.

    My server, EL-Angel-Eyes WildWest server, is becoming more and more popular and I would hate to see it go downhill because of some lack of logging.

    BTW:

    You guys are the tops. What a great piece of software TS is, beats the hell out of RW and Battlecom. Keep up the good work.

  2. #2
    Bastian Guest
    Both features are already available.

    Banning IP ranges works with wildcards. Example: 217.85.*.*

    IP logging works since the new developer server versions. The maximum Log Level is as follows:

    Code:
    access=1
    access_r=1
    access_u=1
    channel_registerred=1
    channel_unregisterred=1
    sa=1
    chat=1
    kick_server=1
    kick_channel=1
    This will log all joins, leaves, kicks, ServerAdmin logins and even public chat messages.

  3. #3
    Join Date
    May 2003
    Location
    Sweden
    Posts
    23
    Originally posted by Ch'Ih-Yu
    Both features are already available.

    Banning IP ranges works with wildcards. Example: 217.85.*.*
    That's not a very good method for banning network ranges though. It would be better to support standard CIDR notation.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •