Client unable to connect to loginserver

[ctuso]

My loginserver appears to be experiencing some issues. It will start, the world will connect to it but my clients can not ever connect (times out). I can see traffic routing through the firewall and the requests hitting the appropriate port (5998 ) on the servers interface via tcpdump when starting the client.

However, the loginserver does not appear to be responding to these packets. I have also noted there are no logs for the loginserver which is what I'm pretty sure is a result of me messing up something somewhere along the line.

My goal is a server accessible via LAN for my boys and I with maybe a friend or two joining remotely.

Current LAN has two Windows 10 machines going through a router with the following ports forwarded (7000:9000, 9081, 5998:5999). Dynamic Dns has been setup to provide an fqdn for the network as well.

Machine is a Centos 7.3.1611 VM running on a QNAP NAS.

eqemu_config.xml

<?xml version="1.0">
<server>
        <world>
                <shortname>2s0 PEQ</shortname>
                <longname>2s0 Project EverQuest Server</longname>

                <address>my.address.com</address>
                <localaddress>192.168.1.2</localaddress>

                <loginserver1>
                        <host>192.168.1.2</host>
                        <port>5998</port>
                        <account>MyAdminAccount</account>
                        <password>MyAdminPassword/password>
                </loginserver1>

                <tcp ip="127.0.0.1" port="9000" telnet="enable"/>

                <key>MyHashKeyWasRemovedToProtectTheGuilty</key>

                <http port="9080" enabled="true" mimefile="mime.types" />
        </world>

        <chatserver>
                <host></host>
                <port>7500</port>
        </chatserver>

        <mailserver>
                <host></host>
                <port>7500</port>
        </mailserver>

        <zones>
        <defaultstatus>0</defaultstatus>

        <ports low="7000" high="7400"/>
        </zones>

        <database>
           <host>localhost</host>
           <port>3306</port>
           <username>DBUsername</username>
           <password>DBPassword</password>
           <db>EQEmuDb</db>
        </database>

        <qsdatabase>
           <host>localhost</host>
           <port>3306</port>
           <username>DBUsername</username>
           <password>DBPassword</password>
           <db>EQEmuDb</db>
        </qsdatabase>

        <webinterface>
                <port>9081</port>
        </webinterface>

        <launcher>
        </launcher>

        <files>
        </files>
        <directories>
        </directories>
</server>

login.ini

[database]
host = localhost
port = 3306
db = EQEmuDb
user = DBUsername
password = DBPassword
subsystem = MySQL

[options]
unregistered_allowed = TRUE
reject_duplicate_servers = FALSE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5998
local_network = 192.168.1.

[security]
plugin = EQEmuAuthCrypto
mode = 5

[Titanium]
port = 5998
opcodes = login_opcodes.conf

[SoD]
port = 5999
opcodes = login_opcodes_sod.conf

[schema]
account_table = tblLoginServerAccounts
world_registration_table = tblWorldServerRegistration
world_admin_registration_table = tblServerAdminRegistration
world_server_type_table = tblServerListType

Output from loginserver with world connected:

server $ ./loginserver
[Login Server] Logging System Init.
[Login Server] Config System Init.
[Login Server] MySQL Database Init.
[Login Server] Server Manager Initialize.
[Login Server] ServerManager listening on port 5998
[Login Server] Client Manager Initialize.
[Login Server] ClientManager listening on Titanium stream.
[Login Server] ClientManager listening on SoD stream.
[Login Server] Server Started.
[Login Server] New world server connection from 192.168.1.2:57430
[World Server] Server 2s0 Project EverQuest Server(2s0 PEQ) successfully logged in.

Client provides the usual, "A connection to the server could not be reached" message. It never progresses to the server list. Packet Dump from the server for port 5998 shows the requests from the client arriving.

$ tcpdump -n port 5998 and '(tcp-syn|tcp-ack)!=0'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
15:59:57.340912 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
15:59:58.358047 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
15:59:59.383262 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:00.401177 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:01.420101 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:02.437638 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:03.456441 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:04.474185 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:05.477279 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:06.501659 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14
16:00:07.519760 IP 192.168.1.5.56723 > 192.168.1.2.5998: UDP, length 14

Any assistance you can provide would be much appreciated!

I just realized this is my first post in the forums even though I've been a member since 2010. It's about time! I made an account and successfully set up a server in 2010. Thanks again for producing something for us all to enjoy. Your hard work is greatly appreciated!!!

[ctuso]

Sigh... some idiot checked to ensure iptables and ipchains were not active, but forgot about firewalld... it's amazing what happens when communication is actually allowed to/from the server lol. Needless to say, logged in

[ctuso]

Still no logs for the loginserver though, which is a bit odd.