I've now done everything I'm capable of thinking of... hehe
Yes, I did comment out the line in question, then added the rest of the snip minus -snip- underneath it. Compiled fine. Others can still log into my server from the outside world.
Using the eqemud file to start the server - I have tried using both of these lines for zone loading, and either way, the outside world is able to connect to my machine.
My linux machine is 192.168.1.1 and also carries the public IP addy resolved by the dyndns (which is indeed getting the correct ip address - tested by pinging)
PUB_IP=dominare.homelinux.com
./zone '.' $PUB_IP $2 $PUB_IP > $1.log 2> $1.errors &
-or-
./zone '.' $PUB_IP $2 127.0.0.1 > $1.log 2> $1.errors &
Here is my LoginServer.ini file:
[LoginServer]
loginserver=eqlogin1.eqemu.net
loginserver2=eqlogin2.eqemu.net
loginport=5999
loginport2=5999
worldname=The Dominare
locked=false
account=
password=
worldaddress=dominare.homelinux.com
[WorldServer]
Defaultstatus=
Unavailzone=
[LoginConfig]
ServerMode=Standalone
ServerPort=5999
UplinkAddress=
UplinkPort=
UplinkAccount=
UplinkPassword=
enablestats=
Also with this, I have tried both setting my windows HOSTS file to read: 192.168.1.1 dominare.homelinux.com, and tried it without.
world.log reads:
...
Error: could not resolve world address
Listening on INADDR_ANY
World server listening on: port 9000
Connected to LoginServer: eqlogin2.eqemu.net:5999
And sees the zoneservers boot themselves and connect.
When I go to log in, it spams the world.log file with:
80824 New client from ip: 192.168.1.2 port: 2029
Logged in: LS#7160: tamarae
Logged in: LS#7160: tamarae
Logged in: LS#7160: tamarae
(...ad nauseum) until it drops me and the client tells me I've lost connectivity.
What have I missed out in doing? Thanks for the help - I do appreciate it. You guys really seem to know what you're talking about after having read most of the forums last night.
Hybrid Mode
