Skip to forum content

You are not logged in. Please login or register.

forums.pvpgn.pro → [EN] Diablo → Server is running but unable to see any realm

Pages 1

You must login or register to post a reply

RSS topic feed

Posts: 23

1 Topic by rogercj (edited by rogercj 20.07.2019 14:38)

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Topic: Server is running but unable to see any realm

I have managed to run bnetd, d2cs, d2gs, and d2dbs on linux while d2gs running in Wine, I don't see any obvious error in log, but game client just couldn't see any realm, below are log files.

By the way, VPS server firewall have 6112 to 6114 open as well as 4000, and I can login bnetd, after login, game client feedback "no realm available right now"

Anywhere I should look into?

d2gs.log

7/20 17:57:53.041 DoCleanup: Calling cleanup routine 'D2GS Timer'
07/20 17:57:53.041 D2GSTimerProcessor: Terminate timer thread
07/20 17:57:53.042 DoCleanup: Calling cleanup routine 'Administrator Console'
07/20 17:57:54.042 DoCleanup: Calling cleanup routine 'D2GS Network'
07/20 17:57:55.044 CloseConnectionToD2CS: Close Connection to D2CS
07/20 17:57:55.044 DoCleanup: Calling cleanup routine 'Diablo II Game Engine'
07/20 17:57:56.187 D2GEThread: Game Engine thread terminated
07/20 17:57:56.187 DoCleanup: Calling cleanup routine 'Global Variables'
07/20 17:57:56.187 DoCleanup: Calling cleanup routine 'Server Mutex'
07/20 17:57:56.187 DoCleanup: Cleanup done.
07/20 18:05:18.757 D2GEThread: Server Thread 42 Created
07/20 18:05:20.397 D2GEThread: Game Server Thread Start Successfully
07/20 18:05:20.399 D2GSResetGameList: End all game in the Game List and in the GE
07/20 18:05:20.400 watchdog_init: CreateThread watchdog_thread, 49
07/20 18:05:20.400 main: Entering Main Server Loop
07/20 18:05:20.402 D2GSConnectToD2xS: Connected to D2DBS Successfully
07/20 18:05:20.403 D2GSSendClassToD2DBS: Send connection class packet to D2DBS
07/20 18:05:20.404 D2GSConnectToD2xS: Connected to D2CS Successfully
07/20 18:05:20.405 D2GSSendClassToD2CS: Send connection class packet to D2CS
07/20 18:05:20.405 D2GSNetRecvPacket: CS socket become writable
07/20 18:05:20.406 D2GSAuthreq: Auth request for 'ZenityD'
07/20 18:05:20.406 D2GSNetRecvPacket: DBS socket become writable
07/20 18:05:20.462 D2GSAuthReply: Game Server Activated by D2CS
07/20 18:05:20.462 D2GSSetD2CSMaxGameNumber: Tell D2CS to set max game to 50
07/20 18:05:20.462 D2GSSetGameInfoByD2CS: Set current maxgame to 50

d2cs.log

Jul 20 18:26:01 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:26:01 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:26:01 [info ] d2cs_conn_create: created session=449 socket=4 (2 current connections)
Jul 20 18:26:01 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:26:01 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:26:01 [info ] d2cs_conn_destroy: [4] closed connection 449 (1 left)
Jul 20 18:26:12 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:26:12 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:26:12 [info ] d2cs_conn_create: created session=450 socket=4 (2 current connections)
Jul 20 18:26:12 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:26:12 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:26:12 [info ] d2cs_conn_destroy: [4] closed connection 450 (1 left)
Jul 20 18:26:23 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:26:23 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:26:23 [info ] d2cs_conn_create: created session=451 socket=4 (2 current connections)
Jul 20 18:26:23 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:26:23 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:26:23 [info ] d2cs_conn_destroy: [4] closed connection 451 (1 left)
Jul 20 18:26:34 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:26:34 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:26:34 [info ] d2cs_conn_create: created session=452 socket=4 (2 current connections)
Jul 20 18:26:34 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:26:34 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:26:34 [info ] d2cs_conn_destroy: [4] closed connection 452 (1 left)
Jul 20 18:26:45 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:26:45 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:26:45 [info ] d2cs_conn_create: created session=453 socket=4 (2 current connections)
Jul 20 18:26:45 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:26:45 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:26:45 [info ] d2cs_conn_destroy: [4] closed connection 453 (1 left)
Jul 20 18:26:56 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:26:56 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:26:56 [info ] d2cs_conn_create: created session=454 socket=4 (2 current connections)
Jul 20 18:26:56 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:26:56 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:26:56 [info ] d2cs_conn_destroy: [4] closed connection 454 (1 left)
Jul 20 18:27:07 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:27:07 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:27:07 [info ] d2cs_conn_create: created session=455 socket=4 (2 current connections)
Jul 20 18:27:07 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:27:07 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:27:07 [info ] d2cs_conn_destroy: [4] closed connection 455 (1 left)
Jul 20 18:27:19 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:27:19 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:27:19 [info ] d2cs_conn_create: created session=456 socket=4 (2 current connections)
Jul 20 18:27:19 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:27:19 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:27:19 [info ] d2cs_conn_destroy: [4] closed connection 456 (1 left)
Jul 20 18:27:30 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:27:30 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:27:30 [info ] d2cs_conn_create: created session=457 socket=4 (2 current connections)
Jul 20 18:27:30 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:27:30 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:27:30 [info ] d2cs_conn_destroy: [4] closed connection 457 (1 left)
Jul 20 18:27:41 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:27:41 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:27:41 [info ] d2cs_conn_create: created session=458 socket=4 (2 current connections)
Jul 20 18:27:41 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:27:41 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:27:41 [info ] d2cs_conn_destroy: [4] closed connection 458 (1 left)
Jul 20 18:27:52 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:27:52 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:27:52 [info ] d2cs_conn_create: created session=459 socket=4 (2 current connections)
Jul 20 18:27:52 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:27:52 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:27:52 [info ] d2cs_conn_destroy: [4] closed connection 459 (1 left)
Jul 20 18:28:03 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:28:03 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:28:03 [info ] d2cs_conn_create: created session=460 socket=4 (2 current connections)
Jul 20 18:28:03 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:28:03 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:28:03 [info ] d2cs_conn_destroy: [4] closed connection 460 (1 left)
Jul 20 18:28:14 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:28:14 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:28:14 [info ] d2cs_conn_create: created session=461 socket=4 (2 current connections)
Jul 20 18:28:14 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:28:14 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:28:14 [info ] d2cs_conn_destroy: [4] closed connection 461 (1 left)
Jul 20 18:28:25 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:28:25 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:28:25 [info ] d2cs_conn_create: created session=462 socket=4 (2 current connections)
Jul 20 18:28:25 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:28:25 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:28:25 [info ] d2cs_conn_destroy: [4] closed connection 462 (1 left)
Jul 20 18:28:36 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:28:36 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:28:36 [info ] d2cs_conn_create: created session=463 socket=4 (2 current connections)
Jul 20 18:28:36 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:28:36 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:28:36 [info ] d2cs_conn_destroy: [4] closed connection 463 (1 left)
Jul 20 18:28:47 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:28:47 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:28:47 [info ] d2cs_conn_create: created session=464 socket=4 (2 current connections)
Jul 20 18:28:47 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:28:47 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:28:47 [info ] d2cs_conn_destroy: [4] closed connection 464 (1 left)
Jul 20 18:28:58 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:28:58 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:28:58 [info ] d2cs_conn_create: created session=465 socket=4 (2 current connections)
Jul 20 18:28:58 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:28:58 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:28:58 [info ] d2cs_conn_destroy: [4] closed connection 465 (1 left)
Jul 20 18:29:09 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:29:09 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:29:09 [info ] d2cs_conn_create: created session=466 socket=4 (2 current connections)
Jul 20 18:29:09 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:29:09 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:29:09 [info ] d2cs_conn_destroy: [4] closed connection 466 (1 left)
Jul 20 18:29:20 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:29:20 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:29:20 [info ] d2cs_conn_create: created session=467 socket=4 (2 current connections)
Jul 20 18:29:20 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:29:20 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:29:20 [info ] d2cs_conn_destroy: [4] closed connection 467 (1 left)
Jul 20 18:29:31 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:29:31 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:29:31 [info ] d2cs_conn_create: created session=468 socket=4 (2 current connections)
Jul 20 18:29:31 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:29:31 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:29:31 [info ] d2cs_conn_destroy: [4] closed connection 468 (1 left)
Jul 20 18:29:42 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:29:42 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:29:42 [info ] d2cs_conn_create: created session=469 socket=4 (2 current connections)
Jul 20 18:29:42 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:29:42 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:29:42 [info ] d2cs_conn_destroy: [4] closed connection 469 (1 left)
Jul 20 18:29:53 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:29:53 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:29:53 [info ] d2cs_conn_create: created session=470 socket=4 (2 current connections)
Jul 20 18:29:53 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:29:53 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:29:53 [info ] d2cs_conn_destroy: [4] closed connection 470 (1 left)
Jul 20 18:30:04 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:30:04 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:30:04 [info ] d2cs_conn_create: created session=471 socket=4 (2 current connections)
Jul 20 18:30:04 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:30:04 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:30:04 [info ] d2cs_conn_destroy: [4] closed connection 471 (1 left)
Jul 20 18:30:15 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:30:15 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:30:15 [info ] d2cs_conn_create: created session=472 socket=4 (2 current connections)
Jul 20 18:30:15 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:30:15 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:30:15 [info ] d2cs_conn_destroy: [4] closed connection 472 (1 left)
Jul 20 18:30:26 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:30:26 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:30:26 [info ] d2cs_conn_create: created session=473 socket=4 (2 current connections)
Jul 20 18:30:26 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:30:26 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:30:26 [info ] d2cs_conn_destroy: [4] closed connection 473 (1 left)
Jul 20 18:30:37 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:30:37 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:30:37 [info ] d2cs_conn_create: created session=474 socket=4 (2 current connections)
Jul 20 18:30:37 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:30:37 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:30:37 [info ] d2cs_conn_destroy: [4] closed connection 474 (1 left)
Jul 20 18:30:48 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:30:48 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:30:48 [info ] d2cs_conn_create: created session=475 socket=4 (2 current connections)
Jul 20 18:30:48 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:30:48 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:30:48 [info ] d2cs_conn_destroy: [4] closed connection 475 (1 left)
Jul 20 18:30:59 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:30:59 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:30:59 [info ] d2cs_conn_create: created session=476 socket=4 (2 current connections)
Jul 20 18:30:59 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:30:59 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:30:59 [info ] d2cs_conn_destroy: [4] closed connection 476 (1 left)
Jul 20 18:31:10 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:31:10 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:31:10 [info ] d2cs_conn_create: created session=477 socket=4 (2 current connections)
Jul 20 18:31:10 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:31:10 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:31:10 [info ] d2cs_conn_destroy: [4] closed connection 477 (1 left)
Jul 20 18:31:22 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:31:22 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:31:22 [info ] d2cs_conn_create: created session=478 socket=4 (2 current connections)
Jul 20 18:31:22 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:31:22 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:31:22 [info ] d2cs_conn_destroy: [4] closed connection 478 (1 left)
Jul 20 18:31:33 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 20 18:31:33 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 20 18:31:33 [info ] d2cs_conn_create: created session=479 socket=4 (2 current connections)
Jul 20 18:31:33 [info ] conn_handle_connecting: connected to 47.52.141.109:6112
Jul 20 18:31:33 [info ] handle_bnetd_init: sent init class packet to bnetd
Jul 20 18:31:33 [info ] d2cs_conn_destroy: [4] closed connection 479 (1 left)

bnetd.log

Jul 20 18:33:57 [debug] ipbanlist_check: lastcheck: 1563618803, now: 1563618837, now-lc: 34.
Jul 20 18:33:57 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:33:57 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36840 on 0.0.0.0:6112
Jul 20 18:33:57 [debug] conn_create: [21][19] sessionkey=0x1245556958 sessionnum=0x00000512
Jul 20 18:33:57 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:33:57 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:33:57 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36840
Jul 20 18:33:57 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:33:57 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:08 [debug] ipbanlist_check: lastcheck: 1563618837, now: 1563618848, now-lc: 11.
Jul 20 18:34:08 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:34:08 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36842 on 0.0.0.0:6112
Jul 20 18:34:08 [debug] conn_create: [21][19] sessionkey=0x1694748854 sessionnum=0x00000513
Jul 20 18:34:08 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:08 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:34:08 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36842
Jul 20 18:34:08 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:08 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:19 [debug] ipbanlist_check: lastcheck: 1563618837, now: 1563618859, now-lc: 22.
Jul 20 18:34:19 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:34:19 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36848 on 0.0.0.0:6112
Jul 20 18:34:19 [debug] conn_create: [21][19] sessionkey=0x173851152 sessionnum=0x00000514
Jul 20 18:34:19 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:19 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:34:19 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36848
Jul 20 18:34:19 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:19 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:30 [debug] ipbanlist_check: lastcheck: 1563618837, now: 1563618870, now-lc: 33.
Jul 20 18:34:30 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:34:30 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36850 on 0.0.0.0:6112
Jul 20 18:34:30 [debug] conn_create: [21][19] sessionkey=0x1816215011 sessionnum=0x00000515
Jul 20 18:34:30 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:30 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:34:30 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36850
Jul 20 18:34:30 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:30 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:38 [debug] ipbanlist_check: lastcheck: 1563618870, now: 1563618878, now-lc: 8.
Jul 20 18:34:38 [debug] ipbanlist_check: checking 178.236.130.4
Jul 20 18:34:38 [info ] sd_accept: [21] accepted connection from 178.236.130.4:39448 on 0.0.0.0:6112
Jul 20 18:34:38 [debug] conn_create: [21][19] sessionkey=0x1806323893 sessionnum=0x00000516
Jul 20 18:34:38 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:38 [error] handle_init_packet: [21] client requested unknown class 0x47 (length 1) (closing connection)
Jul 20 18:34:38 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:38 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:41 [debug] ipbanlist_check: lastcheck: 1563618870, now: 1563618881, now-lc: 11.
Jul 20 18:34:41 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:34:41 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36852 on 0.0.0.0:6112
Jul 20 18:34:41 [debug] conn_create: [21][19] sessionkey=0x300487622 sessionnum=0x00000517
Jul 20 18:34:41 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:41 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:34:41 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36852
Jul 20 18:34:41 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:41 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:48 [debug] ipbanlist_check: lastcheck: 1563618870, now: 1563618888, now-lc: 18.
Jul 20 18:34:48 [debug] ipbanlist_check: checking 31.129.128.196
Jul 20 18:34:48 [info ] sd_accept: [21] accepted connection from 31.129.128.196:44960 on 0.0.0.0:6112
Jul 20 18:34:48 [debug] conn_create: [21][19] sessionkey=0x1355307635 sessionnum=0x00000518
Jul 20 18:34:48 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:48 [error] handle_init_packet: [21] client requested unknown class 0x47 (length 1) (closing connection)
Jul 20 18:34:48 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:48 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:49 [debug] ipbanlist_check: lastcheck: 1563618870, now: 1563618889, now-lc: 19.
Jul 20 18:34:49 [debug] ipbanlist_check: checking 213.133.168.72
Jul 20 18:34:49 [info ] sd_accept: [21] accepted connection from 213.133.168.72:59934 on 0.0.0.0:6112
Jul 20 18:34:49 [debug] conn_create: [21][19] sessionkey=0x1230485559 sessionnum=0x00000519
Jul 20 18:34:49 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:49 [error] handle_init_packet: [21] client requested unknown class 0x47 (length 1) (closing connection)
Jul 20 18:34:49 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:49 [info ] conn_destroy: [21] closed init connection
Jul 20 18:34:52 [debug] ipbanlist_check: lastcheck: 1563618870, now: 1563618892, now-lc: 22.
Jul 20 18:34:52 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:34:52 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36854 on 0.0.0.0:6112
Jul 20 18:34:52 [debug] conn_create: [21][19] sessionkey=0x1965393198 sessionnum=0x00000520
Jul 20 18:34:52 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:34:52 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:34:52 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36854
Jul 20 18:34:52 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:34:52 [info ] conn_destroy: [21] closed init connection
Jul 20 18:35:03 [debug] ipbanlist_check: lastcheck: 1563618870, now: 1563618903, now-lc: 33.
Jul 20 18:35:03 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:35:03 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36856 on 0.0.0.0:6112
Jul 20 18:35:03 [debug] conn_create: [21][19] sessionkey=0x1734809126 sessionnum=0x00000521
Jul 20 18:35:03 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:35:03 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:35:03 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36856
Jul 20 18:35:03 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:35:03 [info ] conn_destroy: [21] closed init connection
Jul 20 18:35:14 [debug] ipbanlist_check: lastcheck: 1563618903, now: 1563618914, now-lc: 11.
Jul 20 18:35:14 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:35:14 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36858 on 0.0.0.0:6112
Jul 20 18:35:14 [debug] conn_create: [21][19] sessionkey=0x40855567 sessionnum=0x00000522
Jul 20 18:35:14 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:35:14 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:35:14 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36858
Jul 20 18:35:14 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:35:14 [info ] conn_destroy: [21] closed init connection
Jul 20 18:35:25 [debug] ipbanlist_check: lastcheck: 1563618903, now: 1563618925, now-lc: 22.
Jul 20 18:35:25 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:35:25 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36864 on 0.0.0.0:6112
Jul 20 18:35:25 [debug] conn_create: [21][19] sessionkey=0x663447724 sessionnum=0x00000523
Jul 20 18:35:25 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:35:25 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:35:25 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36864
Jul 20 18:35:25 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:35:25 [info ] conn_destroy: [21] closed init connection
Jul 20 18:35:36 [debug] ipbanlist_check: lastcheck: 1563618903, now: 1563618936, now-lc: 33.
Jul 20 18:35:36 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:35:36 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36866 on 0.0.0.0:6112
Jul 20 18:35:36 [debug] conn_create: [21][19] sessionkey=0x1603470047 sessionnum=0x00000524
Jul 20 18:35:36 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:35:36 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:35:36 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36866
Jul 20 18:35:36 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:35:36 [info ] conn_destroy: [21] closed init connection
Jul 20 18:35:47 [debug] ipbanlist_check: lastcheck: 1563618936, now: 1563618947, now-lc: 11.
Jul 20 18:35:47 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:35:47 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36868 on 0.0.0.0:6112
Jul 20 18:35:47 [debug] conn_create: [21][19] sessionkey=0x803132183 sessionnum=0x00000525
Jul 20 18:35:47 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:35:47 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:35:47 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36868
Jul 20 18:35:47 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:35:47 [info ] conn_destroy: [21] closed init connection
Jul 20 18:35:58 [debug] ipbanlist_check: lastcheck: 1563618936, now: 1563618958, now-lc: 22.
Jul 20 18:35:58 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:35:58 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36870 on 0.0.0.0:6112
Jul 20 18:35:58 [debug] conn_create: [21][19] sessionkey=0x1478915096 sessionnum=0x00000526
Jul 20 18:35:58 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:35:58 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:35:58 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36870
Jul 20 18:35:58 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:35:58 [info ] conn_destroy: [21] closed init connection
Jul 20 18:36:09 [debug] ipbanlist_check: lastcheck: 1563618936, now: 1563618969, now-lc: 33.
Jul 20 18:36:09 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:36:09 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36872 on 0.0.0.0:6112
Jul 20 18:36:09 [debug] conn_create: [21][19] sessionkey=0x1253429005 sessionnum=0x00000527
Jul 20 18:36:09 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:36:09 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:36:09 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36872
Jul 20 18:36:09 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:36:09 [info ] conn_destroy: [21] closed init connection
Jul 20 18:36:20 [debug] ipbanlist_check: lastcheck: 1563618969, now: 1563618980, now-lc: 11.
Jul 20 18:36:20 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:36:20 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36878 on 0.0.0.0:6112
Jul 20 18:36:20 [debug] conn_create: [21][19] sessionkey=0x1049709548 sessionnum=0x00000528
Jul 20 18:36:20 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:36:20 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:36:20 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36878
Jul 20 18:36:20 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:36:20 [info ] conn_destroy: [21] closed init connection
Jul 20 18:36:31 [debug] ipbanlist_check: lastcheck: 1563618969, now: 1563618991, now-lc: 22.
Jul 20 18:36:31 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:36:31 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36880 on 0.0.0.0:6112
Jul 20 18:36:31 [debug] conn_create: [21][19] sessionkey=0x1415573927 sessionnum=0x00000529
Jul 20 18:36:31 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:36:31 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:36:31 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36880
Jul 20 18:36:31 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:36:31 [info ] conn_destroy: [21] closed init connection
Jul 20 18:36:42 [debug] ipbanlist_check: lastcheck: 1563618969, now: 1563619002, now-lc: 33.
Jul 20 18:36:42 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:36:42 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36882 on 0.0.0.0:6112
Jul 20 18:36:42 [debug] conn_create: [21][19] sessionkey=0x1768579605 sessionnum=0x00000530
Jul 20 18:36:42 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:36:42 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:36:42 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36882
Jul 20 18:36:42 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:36:42 [info ] conn_destroy: [21] closed init connection
Jul 20 18:36:53 [debug] ipbanlist_check: lastcheck: 1563619002, now: 1563619013, now-lc: 11.
Jul 20 18:36:53 [debug] ipbanlist_check: checking 47.52.141.109
Jul 20 18:36:53 [info ] sd_accept: [21] accepted connection from 47.52.141.109:36884 on 0.0.0.0:6112
Jul 20 18:36:53 [debug] conn_create: [21][19] sessionkey=0x272346945 sessionnum=0x00000531
Jul 20 18:36:53 [debug] sd_accept: [21] client connected to a bnet listening address
Jul 20 18:36:53 [info ] handle_init_packet: [21] client initiated d2cs_bnetd connection
Jul 20 18:36:53 [info ] handle_init_packet: [21] d2cs connection from unknown ip address 47.52.141.109:36884
Jul 20 18:36:53 [trace] conn_shutdown: [21] connection already closed
Jul 20 18:36:53 [info ] conn_destroy: [21] closed init connection

rogercj's Website

2 Reply by batmanReturns

  • batmanReturns
  • newbie
  • Offline
  • Registered: 08.07.2019
  • Posts: 17

Re: Server is running but unable to see any realm

Can you tell how are ports configured in VPS firewall? (Inbound/outbound) TCP/UDP.

3 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

batmanReturns wrote:

Can you tell how are ports configured in VPS firewall? (Inbound/outbound) TCP/UDP.

Inbound configuration
6112, 6113, 6114, 4000 allowed

outbound is allowed all traffic by default, it's not likely to be vps firewall problem, since I have tested with firewall disabled, and the miracle didn't happen.

rogercj's Website

4 Reply by hehpe

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

Post your configuration files...

5 Reply by batmanReturns

  • batmanReturns
  • newbie
  • Offline
  • Registered: 08.07.2019
  • Posts: 17

Re: Server is running but unable to see any realm

rogercj wrote:
batmanReturns wrote:

Can you tell how are ports configured in VPS firewall? (Inbound/outbound) TCP/UDP.

Inbound configuration
6112, 6113, 6114, 4000 allowed

outbound is allowed all traffic by default, it's not likely to be vps firewall problem, since I have tested with firewall disabled, and the miracle didn't happen.

Please indicate if TCP or UDP, so I can compare with my firewall rules.

6 Reply by rogercj (edited by rogercj 21.07.2019 06:24)

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

hehpe wrote:

Post your configuration files...

my d2cs

#################################################################################
# d2cs.conf  -  Configuration file for the diablo2 game control server        #
#-------------------------------------------------------------------------------#
#                                        #
# This file is an example configuration and may require modification to        #
# suit your needs or your site.  Blank lines and lines starting with a "#"    #
# are ignored.  Use quotes around values that contain spaces.            #
#                                        #
#################################################################################


#################################################################################
# Server Major Settings                                #
#-------------------------------------------------------------------------------#
#                                        #
# Your realm server name                            #
# Here you put the value of the first column from the realm line in realm.conf
# Example, if you have the line
# "MyRealm" "My Super Realm" <someIP>:6113
# in realm.conf then here you put realmname = "MyRealm"
realmname        =    ZenityD

# This is a comma delimited list of hostnames that the server should
# listen on.  Generally, YOU DONT NEED TO TOUCH THIS but it might be useful 
# to make an internal-only server on a gateway machine for example.  If the 
# list is not set or if it has a entry with no host component, the server will 
# bind to that port on all interfaces.
# d2cs default listening port is 6113
# WARNING!! DO NOT USE "127.0.0.1" or "localhost" !!!
servaddrs        =    0.0.0.0:6113

# This is a comma delimited list of game servers. Put here the IPs
# (without ports) of the machines running d2gs. If you run d2gs on the same 
# machine as d2cs you put the IP of that machine here.
# Example: gameservlist = 192.168.1.10
# (if you have a d2gs running on a machine with the IP 192.168.1.10)
#
# YOU MUST CHANGE THIS OR D2CS WON'T WORK PROPERLY
#
# WARNING!! DO NOT USE "127.0.0.1" or "localhost" !!!
gameservlist        =    47.52.141.109

# Put here the address and port of the machine running bnetd (or pvpgn.exe). 
# If you run d2cs on the same machine as bnetd (or pvpgn.exe) then here you 
# put the IP of that machine.
#
# YOU MUST CHANGE THIS OR D2CS WON'T WORK PROPERLY
#
# bnetd default listening port is 6112
# WARNING!! DO NOT USE "127.0.0.1" or "localhost" !!!
bnetdaddr        =    47.52.141.109:6112

# Set this to the maximum number of concurrent connections allowed on 
# this server. DO NOT TOUCH UNLESS STRICTLY NECESSARY!
max_connections = 1000

# This sets the realm to Classic or LOD or Both
# Classic = 0
# LOD = 1
# Both = 2 (default)
lod_realm = 2

# This sets whether you can convert a clasic char to
# an expansion char.
# Allow Convert = 1
# Don't allow Convert = 0
allow_convert = 0

# here u can enter the symbols allowed in accountnames (additional to 
# alphanumerical symbals which are always accepted). please note that
# it is absolutly mandatory that u set up the same symbols here as in
# bnetd.conf or else u wont be able to play D2 with some characters
# (those whose symbols are allowed in bnetd.conf but not here)
# same warnings as in bnetd.conf apply here - be warned - and just
# change something if you know what you are doing
#default setting is "-_[]"
account_allowed_symbols = "-_[]"

#                                        #
#################################################################################

#################################################################################
# Message logs                                    #
#-------------------------------------------------------------------------------#
# Multiple log levels can be defined by connecting them with a comma (,)
# Available loglevels are:
#   none
#   trace
#   debug
#   info
#   warn
#   error
#   fatal
#loglevels = fatal,error,warn,info
loglevels = fatal,error,warn,info,debug,trace

#                                        #
#################################################################################

#################################################################################
# File and Path section                                #
# Use absolute paths in these lines to avoid problems!                #
#-------------------------------------------------------------------------------#
#                                        #
logfile            =    "/usr/local/var/pvpgn/d2cs.log"
charsavedir        =    "/usr/local/var/pvpgn/charsave"
charinfodir        =    "/usr/local/var/pvpgn/charinfo"
bak_charsavedir        =    "/usr/local/var/pvpgn/bak/charsave"
bak_charinfodir        =    "/usr/local/var/pvpgn/bak/charinfo"
ladderdir        =    "/usr/local/var/pvpgn/ladders"
transfile        =    "/usr/local/etc/pvpgn/address_translation.conf"
d2gsconffile        =    "/usr/local/etc/pvpgn/d2server.ini"
#pidfile        =    "/usr/local/var/pvpgn/d2cs.pid"

# d2s template for a new created characters
newbiefile_amazon        =    "/usr/local/var/pvpgn/files/newbie.save"
newbiefile_sorceress        =    "/usr/local/var/pvpgn/files/newbie.save"
newbiefile_necromancer        =    "/usr/local/var/pvpgn/files/newbie.save"
newbiefile_paladin        =    "/usr/local/var/pvpgn/files/newbie.save"
newbiefile_barbarian        =    "/usr/local/var/pvpgn/files/newbie.save"
newbiefile_druid        =    "/usr/local/var/pvpgn/files/newbie.save"
newbiefile_assasin        =    "/usr/local/var/pvpgn/files/newbie.save"

#                                        #
#################################################################################

#################################################################################
# Misc                                        #
#-------------------------------------------------------------------------------#
#                                        #
# Message Of The Day
motd                    =       "No Message Of The Day Set" 

# Set to non-zero to allow creation of new realm character
allow_newchar        =    1

# Do you want d2cs to check client for multilogin for security reason?
check_multilogin    =    0

# Maxinum number of character per account
# Max allowed value is 18 (enforced by server)
maxchar            =    8

# Character sorting. Options are: level, ctime, mtime, name, none. (none assumed if
# not specified).
#charlist_sort = "none"

# Do we need ascending or descending order for charlist?
#charlist_sort_order = "ASC"

# Maxinum number of games will be shown in join game list
# Zero = infinite
maxgamelist        =    20

# Set to non-zero to allow show all games with difficulty < character difficulty
# Otherwise, only game with difficulty = character difficulty will be shown
gamelist_showall    =    0

# Maxinum time in seconds that a user can idle
# Zero = infinite
idletime        =    3600

# Amount of time to delay shutting down server in seconds.
shutdown_delay        =    300

# Amount of time delay period is decremented by either a SIGTERM or SIGINT
# (control-c) signal in seconds.
shutdown_decr        =    60
#
#################################################################################


#################################################################################
# Internal System Settings                            #
# You may just ignore them and use the default value                #
#-------------------------------------------------------------------------------#
#
# How often will the server purge all list to clean unused data (in seconds)
listpurgeinterval    =    300

# How often will the server check game queues (in seconds)
gqcheckinterval        =    60

# How often will the server retry to connect to bnetd 
# when connection lost (in seconds)
s2s_retryinterval    =    10

# How long time the s2s connection will timeout 
s2s_timeout        =    10

# How often the server will check server queues for expired data
sq_checkinterval    =    300

# How long time will a server queue data expire
sq_timeout        =    300

# Game serer binary files checksum, use zero to skip this checking
d2gs_checksum        =    0

# Game server version, use zero to skip this checking
d2gs_version        =    0

# Game server password
d2gs_password        =    "cjyueyue123"

# Maxinum number of second that a game will be shown on list( zero = infinite )
game_maxlifetime    =    0

# Maximum level allowed in this (realm) game.
# Normal games have a max level 99, while the internal field size limit is 255.
# Extreme game MODs may have higher values, but be warned:
# !!! Use them at your own risk !!!
# game_maxlevel       = 255

# A game will be automatically destroied after how long time idle
max_game_idletime    =    0

# Allow Limitation created game with password, player number or level limit?
allow_gamelimit        =    1

# Ladder refresh time
ladder_refresh_interval =    3600

# server to server connection max idle time in seconds
s2s_idletime        =    300

# server to server connection keepalive interval
s2s_keepalive_interval    =    60

# all connection timeout check interval
timeout_checkinterval    =    60

# game server restart interval
# when sending SIGUSR2 signal to your d2cs this issues a restart
# of all connected d2gs after d2gs_restart_delay seconds
d2gs_restart_delay    =    300

# ladder start time
# format: yyyy-mm-dd hh:mm:ss
# be carefull:
# all chars created before this date will revert to non-ladder chars
ladder_start_time    =    ""

# number of days before a char expires (default 0=unlimited)
char_expire_day        =    0

#
#################################################################################

my d2dbs

#################################################################################
# d2dbs.conf  -  Configuration file for the Diablo2 Game database server    #
#-------------------------------------------------------------------------------#
#                                        #
# This file is an example configuration and may require modification to        #
# suit your needs or your site.  Blank lines and lines starting with a "#"    #
# are ignored.  Use quotes around values that contain spaces.            #
#                                        #
#################################################################################

#################################################################################
# Server Major Settings                                #
#-------------------------------------------------------------------------------#
# This is a comma delimited list of hostnames that the server should
# listen on.  Generally, YOU DONT NEED TO TOUCH THIS but it might be useful 
# to make an internal-only server on a gateway machine for example.  If the 
# list is not set or if it has a entry with no host component, the server will 
# bind to that port on all interfaces.
# d2dbs default listening port is 6114
# WARNING!! DO NOT USE "127.0.0.1" or "localhost" !!!
servaddrs    = 0.0.0.0:6114

# Put here EXACTLY the same thing you put in d2cs.conf gameservlist setting.
# For more information about this setting consult the d2cs.conf comments
# above it.
#
# YOU MUST CHANGE THIS OR D2DBS WON'T WORK PROPERLY
#
# WARNING!! DO NOT USE "127.0.0.1" or "localhost" !!!
gameservlist            =       47.52.141.109

#                                        #
#################################################################################

#################################################################################
# Message logs                                                                  #
#-------------------------------------------------------------------------------#
# Multiple log levels can be defined by connecting them with a comma (,)
# Available loglevels are:
#   none
#   trace
#   debug
#   info
#   warn
#   error
#   fatal
#loglevels = fatal,error,warn,info
loglevels = fatal,error,warn,info,debug,trace

#                                                                               #
#################################################################################

#################################################################################
# File and Path section                                #
# Use absolute paths in these lines to avoid problems!                #
#-------------------------------------------------------------------------------#
logfile        =    "/usr/local/var/pvpgn/d2dbs.log"
logfile-gs    =    "/usr/local/var/pvpgn/d2dbs-gs.log"
charsavedir    =    "/usr/local/var/pvpgn/charsave"
charinfodir    =    "/usr/local/var/pvpgn/charinfo"
ladderdir    =    "/usr/local/var/pvpgn/ladders"
bak_charsavedir    =    "/usr/local/var/pvpgn/bak/charsave"
bak_charinfodir    =    "/usr/local/var/pvpgn/bak/charinfo"
#pidfile    =    "/usr/local/var/pvpgn/d2dbs.pid"

#                                        #
#################################################################################

#################################################################################
# Misc                                        #
#-------------------------------------------------------------------------------#
#                                        #
# Ladder save interval
laddersave_interval    =    3600

# Time that allow characters create after it insert into ladder
# These code should be rewritted to support string formmated time
ladderinit_time        =    0

# create extra ladder file in XML format that can be parsed more easy
# 0 = turn extra output off (default)
# 1 = turn on the XML output
XML_ladder_output       =       0

# Amount of time to delay shutting down server in seconds.
shutdown_delay          =       360

# Amount of time delay period is decremented by either a SIGTERM or SIGINT
# (control-c) signal in seconds.
shutdown_decr           =       60

# connection max idle time in seconds
idletime        =    300

# connection keep alive interval
keepalive_interval    =    60

# connection time out check interval
timeout_checkinterval    =    60

# experience threshold, minimum experience needed to register on the ladder
ladderupdate_threshold    =    0

# What chars will be added to ladder?
# 0 = ladder and non-ladder chars
# 1 = only ladder chars
ladder_chars_only    =    1

# This setting activates a workaround for the well known "Lvl 100" bug.
# It should be activated for mods where the max level is greater than 99.
# Activating this should work for mods with any max level
# If level is greater than 255, it will be set to 255
# 0 = deactivated
# 1 = activated
difficulty_hack         =       0

#                                        #
#################################################################################

realm.conf

#################################################################################
# realm.list  -  List of Diablo II Realms                    #
#-------------------------------------------------------------------------------#
#                                        #
# Realms are areas that hold closed characters and games.            #
# Users are given this list of realms to choose from when            #
# creating a new character.  Next time the character is                #
# used, they will automatically join the same realm.                #
#                                        #
# The realm server runs on port 6113 by default.                #
# If you do not specify a port number, it will use this by default.        #
#                                        #
# <realmname> : the realm name (mandatory; must start and end with " )        #
# <description> : the realm description (optional; must start and end with " )    #
# ip:port - actual ip the d2cs server is running on (mandatory)            #
#                                            #
# --- realm name ---    --- description ---    --- real address ---        #
#    (mandatory)        (optional)             (mandatory)        #
#-------------------------------------------------------------------------------#
#   "<realmname>"     ["<description>"]          <ip:port>            #
#                                        #
#################################################################################

# WARNING!! DO NOT USE "127.0.0.1" or "localhost" FOR ANY IP ADDRESS

# example (having a d2cs server running on IP 1.2.3.4):
"ZenityD"            "PVPGN Closed Realm"        47.52.141.109:6113

d2gs.reg

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\D2Server\D2GS]
@="Diablo II Close Game Server"
"AutoUpdate"=dword:00000000
"AutoUpdateUrl"="http://www.mywebsite.com/for.update"
"AutoUpdateVer"=dword:00000000
"AutoUpdateTimeout"=dword:00007530
"D2CSIP"="47.52.141.109"
"D2CSPort"=dword:000017e1
"D2DBSIP"="47.52.141.109"
"D2DBSPort"=dword:000017e2
"MaxGames"=dword:00000032
"MaxGameLife"=dword:00003840
"AdminPassword"="10a453fd4399d158848857cabd4aa6fb73338759"
"AdminPort"=dword:000022b8
"AdminTimeout"=dword:00000e10
"D2CSSecrect"="cjyueyue123"
"EnableNTMode"=dword:00000000
"EnablePreCacheMode"=dword:00000001
"IdleSleep"=dword:00000001
"BusySleep"=dword:00000001
"CharPendingTimeout"=dword:00000258
"DebugNetPacket"=dword:00000000
"DebugEventCallback"=dword:00000000
"EnableGSLog"=dword:00000001
"EnableGELog"=dword:00000001
"EnableGEMsg"=dword:00000000
"EnableGEPatch"=dword:00000001
"IntervalReconnectD2CS"=dword:00000032
"MultiCPUMask"=dword:00000001
"MaxPreferUsers"=dword:000000b4
"MaxPacketPerSecond"=dword:000004b0
"ServerConfFile"="D2Server.ini"
"MOTD"="Welcome to ZenityD!"

edit
My setup is like this:
bnetd,d2cs,d2dbs,d2gs all running on the same ubuntu vps terminal. except d2gs is running in wine.  it must be ip configure problem in between ubuntu host and wine. but I couldnt figure out where to pinpoint.

By the way, my open bn game running just fine.

rogercj's Website

7 Reply by hehpe (edited by hehpe 21.07.2019 06:23)

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

Change serveraddrs and you should be able to see your realm.
d2cs.conf  serveraddrs = 47.52.141.109:6113
d2dbs.conf serveraddrs = 47.52.141.109:6114

8 Reply by rogercj (edited by rogercj 21.07.2019 06:44)

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

hehpe wrote:

Change serveraddrs and you should be able to see your realm.
d2cs.conf  serveraddrs = 47.52.141.109:6113
d2dbs.conf serveraddrs = 47.52.141.109:6114

still no luck, but I have interesting finding.

look at my Wine log

---------------------------------------------------------------
CloudB Realm startup at 2019-07-21 10:32:46.668
---------------------------------------------------------------
10:32:46.668  ------------------------------------------------------
10:32:46.668  2019-07-21 10:32:46
10:32:46.668  Diablo II Game Server running under Windows XP (Version 5.010)
10:32:46.668  Vendor:  Intel
10:32:46.668  Version: Pentium III (no brand) (Type 0, Family 6, Model F, Stepping 1, Brand 0)
10:32:46.677  Speed: Approx. 2499 MHz
10:32:46.677  Total Physical Memory: 985.38MB
10:32:46.677  Application Path: C:\d2gs
10:32:46.678  Local IP: 172.31.218.168
10:32:46.678  Computer name: CloudB
10:32:46.678  ------------------------------------------------------
10:32:46.678  
10:32:46.679  imagehlp.dll loaded for better stack crawls.

turns out my Wine running with its own internal ip, is that the cause of this?  Do I have to setup a ip translation? how to do that?

Added: 21.07.2019 06:41

batmanReturns wrote:
rogercj wrote:
batmanReturns wrote:

Can you tell how are ports configured in VPS firewall? (Inbound/outbound) TCP/UDP.

Inbound configuration
6112, 6113, 6114, 4000 allowed

outbound is allowed all traffic by default, it's not likely to be vps firewall problem, since I have tested with firewall disabled, and the miracle didn't happen.

Please indicate if TCP or UDP, so I can compare with my firewall rules.

I have opened all TCP UDP at all ports while testing and got no luck, so I dont think the root cause is firewall.

rogercj's Website

9 Reply by hehpe (edited by hehpe 21.07.2019 07:18)

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

What version of wine and ubuntu do you use?
Did you compile your own version with sock patch and did you run d2gs.reg after you installed d2gs?

wine regedit /home/path to your d2gs.reg

does it still show no realm available because that's not d2gs related. Check your internal and public addresses if they are different you'll have to use address_translatio.conf

Show me your iptable rules too

10 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

hehpe wrote:

Did you compile your own version with sock patch and did you run d2gs.reg after you installed d2gs?
What version of wine and ubuntu do you use?

wine regedit /home/path to your d2gs.reg

does it still show no realm available because that's not d2gs related. Check your internal and public addresses if they are different you'll have to use address_translatio.conf

Show me your iptable rules too

Yes, I compiled my own with sock patch, d2gs.reg is installed.

Now I got d2cs log error,  seems it couldnt bind to my external ip, 

Jul 21 11:15:06 [info ] s2s_create: try make s2s connection to 47.52.141.109:6112
Jul 21 11:15:06 [info ] s2s_create: connection to s2s server 47.52.141.109:6112 is in progress
Jul 21 11:15:06 [info ] d2cs_conn_create: created session=1 socket=2 (1 current connections)
Jul 21 11:15:06 [error] net_listen: error bind listen socket
Jul 21 11:15:06 [error] server_listen: error listen socket
Jul 21 11:15:06 [error] d2cs_server_process: failed to setup listen socket
Jul 21 11:15:06 [error] main: failed to run server

my Wine internal address and public address seems different, Wine internal IP seems to be 172.31.218.168

Wine output is this 

10:32:46.668  Diablo II Game Server running under Windows XP (Version 5.010)
10:32:46.668  Vendor:  Intel
10:32:46.668  Version: Pentium III (no brand) (Type 0, Family 6, Model F, Stepping 1, Brand 0)
10:32:46.677  Speed: Approx. 2499 MHz
10:32:46.677  Total Physical Memory: 985.38MB
10:32:46.677  Application Path: C:\d2gs
10:32:46.678  Local IP: 172.31.218.168
10:32:46.678  Computer name: CloudB

How to make translation? I have less knowledge about ip translation. please help, thank you

rogercj's Website

11 Reply by hehpe (edited by hehpe 21.07.2019 07:26)

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

Open the terminal type this

ip addr show

and show me the output.
You didn't answer me about your wine version iptables rules etc.

12 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

hehpe wrote:

Open the terminal type this

ip addr show

and show me the output.
You didn't answer me about your wine version iptables rules etc.

hostname -i shows an internal ip, 

172.31.218.168 172.31.218.168

Is that the culprit? should i change it to my external ip?

Wine version is 2.0.1, I got it from forum, and ubuntu is 18.04


https://forums.pvpgn.pro/uploads/images/2019/07/21/111.png

rogercj's Website

13 Reply by hehpe (edited by hehpe 21.07.2019 07:35)

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

Here is your address_translation.conf

NOTE: use 172.31.218.168 in bnet,d2cs,d2dbs,gs,realm conf



########################################################################################################
#------------------------------------------------------------------------------------------------------#
# Address Translation table                                                                            #
#----------------------------------------------------------------------------
#
# DO NOT, I REPEAT, DO NOT TOUCH THIS FILE UNLESS YOU RUN THE SERVER ON A 
# COMPUTER INSIDE A LAN AND YOU NEED TO HAVE PLAYERS FROM "OUTSIDE" YOUR LAN
#
# This is a list of ip:port addresses that get translated
# EVERYTHING AFTER A "#" IS IGNORED (ie COMMENTED)
#
# The entries are broken into four parts:
#
# * the IP address w/port to be translated (what pvpgn wants to send initially)
# * the output IP address w/port (what pvpgn WILL send after translation)
# * comma delimited list of networks to be excluded from translation
# * comma delimited list of networks to be included in translation
#
# Each line must contain all four parts or the entire entry will be rejected
# There are no default ports, make sure input and output include the port number
#
# The entries are searched in the order listed in this file
# Exclude networks are searched before include networks
# Only the first matching line is used
# Lines begining with '#' are ignored
#
# If no match is found, the input ip will be returned.
#
# Network specification can be either NONE, ANY or x.y.z.t/bitlen:
# - NONE = no neworks (same as 0.0.0.0/32)
# - ANY = All networks (same as 0.0.0.0/0)
# x.y.z.t/bitlen : means matching the first bitlen bits from the x.y.z.t value
# Example: if you have the network 192.168.0.x (where x is from 1 to 255) to 
# match any IP in it you use "192.168.0.0/24" meaning the first 24 bits of 
# 192.168.0.0 HAVE TO match (the first 24 bits means the first 3 digits)
#
#################################################################################

################################################################################
# w3route server ip translation
#
# Here you can translate the IP/port of the w3route IP/port as sent by pvpgn
# to the WAR3 clients. You need this ONLY if you want to have external W3 
# players that will play PlayGame/ArrangedTeam games.
# Set exclude to the range of clients you want to recieve the input address
#    instead of the output address
# Set include to the range of clients you want to recieve the output address
#
# input (ip:port)   output (ip:port)   exclude (ip/netmask)    include (ip/netmask)
#----------------- ------------------ ----------------------  ----------------------

# Example, if you left w3route = 0.0.0.0:6200 as it is by default in bnetd.conf
# AND you have the external IP 1.2.3.4 AND you want to exclude from translation 
# the internal W3 clients (those with IPs 192.168.0.x) AND you port forward 
# port 6200 TCP from your router to the pvpgn server port 6200 then here put:

# 0.0.0.0:6200      1.2.3.4:6200      192.168.0.0/24           ANY


###############################################################################
# Game Translations for clients/games (client data ports)
#
# You need this ONLY if you will have internal players that want to play with 
# external ones.
#
# This setting is NOT NEEDED for D2 closed realm clients (they connect to d2gs 
# to play games not to eachover).
#
# Set input address to the client to be translated 
# Set output address to the address to be sent to the other clients 
# Set exclude to the range of clients you want to recieve the input address 
#    instead of the output address 
# Set include to the range of clients you want to recieve the output address 
#
# input (ip:port)    output (ip:port)    exclude (ip/netmask)    include (ip/netmask)
#-----------------  ------------------  ----------------------  ----------------------

# Example, if you have an internal client on IP 192.168.1.10 AND you have the 
# external IP 1.2.3.4 AND you want to exclude from translation the internal 
# clients (those with IPs 192.168.1.x and 10.x.y.z) AND you port forward 
# port 6118 TCP AND UDP from your router to the client IP and port 6112 then 
# here put:

172.31.218.168:6112   47.52.141.109:6118      192.168.1.0/24,10.0.0.0/8  ANY



################################################################################
# Diablo II Character Server translation (d2cs)
#
# You need this ONLY if you run a d2cs (ie ONLY if you will host a Diablo2 
# closed realm).
#
# Set input address to the ip of d2cs (same as the ip in the realm.conf)
# Set output address to the address to be sent to the clients
# Set exclude to the range of clients you want to recieve the input address
#    instead of the output address
# Set include to the range of client you want to recieve the output address
#
# input (ip:port)    output (ip:port)    exclude (ip/netmask)    include (ip/netmask)
#-----------------  ------------------  ----------------------  ----------------------

# Example, if you run a d2cs on IP 192.168.1.10 port 6113 and you have put the 
# same IP/port in realm.conf AND you have the external IP 1.2.3.4 AND you want 
# to exclude from translation the internal clients (those with IPs 192.168.1.x) 
# AND you port forward port 6113 TCP from your router to the machine running 
# d2cs and port 6113 then here put:

172.31.218.168:6113  47.52.141.109:6113       192.168.1.0/24          ANY



################################################################################
# Diablo II Game Server Translation (d2gs)
#
# Set input address to the ip of d2gs (same as the gameservlist in d2cs.conf)
# Set output address to the address to be sent to the clients
# Set exclude to the range of clients you want to recieve the input address
#    instead of the output address
# Set include to the range of client you want to recieve the output address
#
# input (ip:port)    output (ip:port)    exclude (ip/netmask)    include (ip/netmask)
#-----------------  ------------------  ----------------------  ----------------------

# Example, if you run a d2gs on IP 192.168.1.100 (and port 4000, d2gs cannot 
# listen on other port, it will automatically listen on port 4000) and you have 
# put the same IP in d2cs.conf and d2dbs.conf gameservlist setting AND you have 
# the external IP 1.2.3.4 AND you dont want to exclude from translation anyone 
# AND you port forward port 4000 TCP from your router to the machine running 
# d2gs and port 4000 then here put:

172.31.218.168:4000  47.52.141.109:4000       192.168.1.0/24                    ANY



################################################################################
# Westwood Online Game Server Translation (wwol)
#
#
# input (ip:port)    output (ip:port)    exclude (ip/netmask)    include (ip/netmask)
#-----------------  ------------------  ----------------------  ----------------------

#192.168.1.10:4005   1.2.3.4:4005       192.168.1.0/24          ANY

14 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

Thank you, Hehpe,

Do I have to modify d2cs.conf and d2dbs.conf servadd back to 0.0.0.0:611x ?

rogercj's Website

15 Reply by hehpe (edited by hehpe 21.07.2019 08:05)

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

rogercj wrote:

Thank you, Hehpe,

Do I have to modify d2cs.conf and d2dbs.conf servadd back to 0.0.0.0:611x ?

they need to be 172.31.218.168:611x as I said you should change it in every conf file.
Bnetd,cs,dbs,realm

16 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

hehpe wrote:
rogercj wrote:

Thank you, Hehpe,

Do I have to modify d2cs.conf and d2dbs.conf servadd back to 0.0.0.0:611x ?

they need to be 172.31.218.168:611x

OMG!!!

Finally solved!!!

I have been completely in dark for 3 days and dawn came!!

You are my savior!!!! Hehpe, thank you so much!!!

rogercj's Website

17 Reply by hehpe (edited by hehpe 21.07.2019 08:07)

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

You're welcome dude.. and next time use the search because I have the feeling that I am explaining this every week big_smile
I think I should make complete linux guide or something.

18 Reply by rogercj (edited by rogercj 21.07.2019 11:22)

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

hehpe wrote:

You're welcome dude.. and next time use the search because I have the feeling that I am explaining this every week big_smile
I think I should make complete linux guide or something.

Yeh, a comprehensive linux guide could really be handy,  i'm really grateful for what you have done for the community.

Hopefully I could give my share of help to the community.

rogercj's Website

19 Reply by batmanReturns

  • batmanReturns
  • newbie
  • Offline
  • Registered: 08.07.2019
  • Posts: 17

Re: Server is running but unable to see any realm

Never use 127.0.0.1 nor 0.0.0.0
Always use ststic IP address AND only 1 NiC.

20 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

https://forums.pvpgn.pro/uploads/images/2019/07/22/desk4.png

So far my server is running flawlessly. had 2 friends playing on it and it's perfect.

rogercj's Website

21 Reply by hehpe (edited by hehpe 22.07.2019 18:40)

  • hehpe
  • hehpe
  • newbie++
  • Offline
  • Registered: 16.05.2017
  • Posts: 80

Re: Server is running but unable to see any realm

rogercj wrote:

So far my server is running flawlessly. had 2 friends playing on it and it's perfect.

Good! Did you change the gs default password from abcd123?

set more than 50 games and users

maxgame 200
maxuser 1000

22 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

hehpe wrote:
rogercj wrote:

So far my server is running flawlessly. had 2 friends playing on it and it's perfect.

Good! Did you change the gs default password from abcd123?

set more than 50 games and users

maxgame 200
maxuser 1000

Yes, I have changed psw before gs went online,  though I did forget to change maxgame, however, i dont think it would be running more than 50 game simultaneously since I never promote my server to public, it's only for me, my wife and few friend to entertaining ourself.

rogercj's Website

23 Reply by rogercj

  • rogercj
  • newbie
  • Offline
  • Registered: 20.07.2019
  • Posts: 13

Re: Server is running but unable to see any realm

https://forums.pvpgn.pro/uploads/images/2019/07/29/servergs.png

I have setup 4 bots running on my server days and nights non-stop, it's fun to login my main and jump on my bots game to see how they trying to fight against me.

rogercj's Website

Posts: 23

Pages 1

You must login or register to post a reply

Who now at forum

Currently view post: 0 guests, 0 registered users

forums.pvpgn.pro → [EN] Diablo → Server is running but unable to see any realm