Quote:
Originally Posted by Uleat
I would post your config files with any login/WAN info redacted.
It almost looks like your zone launcher is connecting through localhost instead of your LAN address.
I run exclusively on localhost..so, I can't verify that atm.
|
Code:
[eq@eq-emu server]$ cat eqemu_config.xml
<?xml version="1.0"?>
<server>
<world>
<shortname>floppie</shortname>
<longname>Floppie's Server</longname>
<!-- Only specify these two if you really think you need to. (read: You don't) -->
<!-- <address>some.server.com</address> -->
<!-- <localaddress>192.168.0.5</localaddress> -->
<!-- Loginserver information. Defaults shown -->
<loginserver>
<host>login.eqemulator.net</host>
<port>5998</port>
<account></account>
<password></password>
</loginserver>
<!-- Server status. Default is unlocked -->
<locked />
<!-- Sets the ip/port for the tcp connections. Both zones and console (if enabled). Defaults are shown -->
<tcp ip="127.0.0.1" port="33000" telnet="disable" />
<!-- Sets the shared key used by zone/launcher to connect to world -->
<key>REDACTED</key>
<!-- Enable and set the port for the HTTP service. Defaults are shown -->
<http port="33080" enabled="true" mimefile="mime.types" />
</world>
<!-- Chatserver (channels) information. Defaults shown -->
<chatserver>
<host>channels.eqemulator.net</host>
<port>7778</port>
</chatserver>
<!-- Mailserver (in-game mail) information. Defaults shown -->
<mailserver>
<host>channels.eqemulator.net</host>
<port>7778</port>
</mailserver>
<zones>
<defaultstatus>20</defaultstatus>
<!-- Sets port range for world to use to auto configure zones -->
<ports low="33100" high="33200" />
</zones>
<!-- Database configuration, replaces db.ini. Defaults shown -->
<database>
<host>127.0.0.1</host>
<port>3306</port>
<username>REDACTED</username>
<password>REDACTED</password>
<db>REDACTED</db>
</database>
<qsdatabase>
<host>127.0.0.1</host>
<port>3306</port>
<username>REDACTED</username>
<password>REDACTED</password>
<db>REDACTED</db>
</qsdatabase>
<!-- Launcher Configuration -->
<launcher>
<logprefix>logs/zone-</logprefix>
<logsuffix>.log</logsuffix>
<exe>./zone</exe>
<timers initial="20000" interval="2000" restart="10000" reterminate="10000" />
</launcher>
<!-- File locations. Defaults shown -->
<files>
<!-- <spells>spells_us.txt</spells> -->
<!-- <opcodes>opcodes.conf</opcodes> -->
<!-- <logsettings>log.ini</logsettings> -->
<!-- <eqtime>eqtime.cfg</eqtime> -->
</files>
<!-- Directory locations. Defaults shown -->
<directories>
<!-- <maps>Maps</maps> -->
<!-- <quests>quests</quests> -->
<!-- <plugins>plugins</plugins> -->
</directories>
</server>
It is worth noting that world
does still appear to be listening on UDP9000 (in addition to TCP33000 and TCP33080), but I've got that forwarded on my router as well.
Code:
[eq@eq-emu server]$ ss -l4pn | grep 'world\|zone'
udp UNCONN 0 0 *:9000 *:* users:(("world",32532,9))
udp UNCONN 0 0 *:33100 *:* users:(("zone",32585,13))
udp UNCONN 0 0 *:33101 *:* users:(("zone",32595,13))
udp UNCONN 0 0 *:33102 *:* users:(("zone",32601,13))
udp UNCONN 0 0 *:33103 *:* users:(("zone",32609,13))
udp UNCONN 0 0 *:33104 *:* users:(("zone",32615,13))
tcp LISTEN 0 0 *:33000 *:* users:(("world",32532,6))
tcp LISTEN 0 0 *:33080 *:* users:(("world",32532,5))
Everything that's listening is doing it on all interfaces, though. If the zone daemon(s) are talking to world over loopback, is that a problem or would it be fine? I'd think fine as long as it's talking out to the client over the real interface, which it seems to be based on a wireshark screenshot I can't seem to upload to imgur haha...but maybe I'm crazy and that is indeed a problem?