Port Triggering
 

anyone have any guidance on setting up port triggering for routers when hosting an EQEMU server?

my router (tp-link) can only port forward single ports. not looking to add 400 entries.

so far I have port 9000, 5999, and 7000 forwarded.

port triggering requires a trigger start 7001, trigger end 7400. External Port Start: ??? 7001 doesn't seen to allow connections here
External End Port: ??? 7400 doesn't seen to work here.

Not sure if this will help, or if you saw this page ? Also, doesn't 5998 have to be in there as well ?
http://int-help.com/en/port-triggeri...p-link-router/

AFAIK the client start the first connect to the zones and not the zones to the client. So you need Port Forwarding, not Port Triggering. You need one forward for each zone. If you have 30 dynamic zones then you need Forwarding for 7000-7030.

i thought 5998 was only for titanium clients. was using ROF2.

i think my hang up is not knowing what port the client is using to try and connect to 7000-7400 range.
do I also need a trigger range for 1024-65535?

Trigger Start: 7001
Trigger End: 7500
External Start Port: 7001
External Start End: 7500
Protocol: BOTH

If i connect locally i don't have an issue. so the server itself isn't blocking via firewall.

I'll try this. thanks

I just assumed your server was going to be connecting to the public EQEmu login server ?
In your config: (this has nothing to do with clients)
<host>login.eqemulator.net</host>
<port>5998</port>

i have two entries in my config.
one for the local IP
and another that is a dns address that maps to my public ip (like dyndns).
outside of my network they are using dyndns 5999, internally is using the local IP.

So you're setting up for a dual login, one being a private login,
(to allow outside connections) ?

that's right. and they (public connections) can get to login and create an account. they cannot get to character creation or beyond.

Ok, so whatever port your private loginserver is listening on, (usually 5998 )
That listening port has nothing to do with client versions. See below login.ini

got it. will add that back into the router as a forwarded port.

Just as an added note : In the login.ini - whatever IP you are using, leave out that
last octet number, keeping the period though. Or you may have client connect probs.
Example:
local_network = 192.168.10.

yeah i ran into that before. thanks. i can only forward a total of 30 ports on this router. so hopefully 22 entries is enough as I'm using 8 for other things. may be time to get a new router...

It's been a long time since I run into a router without port range forwarding, but I can't imagine
what it would be like with a project like this. I'd probably just to hell with it and DMZ, haha
Hackers are all busy with politicians anyway :P

got past this issue. by replacing the router.

i am now having an issue with zone.exe running the start script it defaults to 127.0.0.1: <random port>

this causes me issues. players outside of my LAN cannot connect to port 7000. yet if i map that port to forward to say 3389. they can of course connect to it.

so it's not a forwarding issue. I expect its a problem that zone.exe isn't starting up with 0.0.0.0 or my actual IP address. is there a config way that I can change this? or am I looking at

when I messed around with a private server a year or so ago this wasn't an issue. sadly that build is gone and I'm on the most recent stable release. did something change?