Welcome, Guest. Please login or register.
Did you miss your activation email?
October 01, 2024, 11:34:21 pm *

Login with username, password and session length
Pages: [1]
Print
Author Topic: Port Forwarding? WRT54G2 - linksys  (Read 5911 times)
Nijjin
Newbie
*
Posts: 28


View Profile
« on: July 17, 2013, 12:57:50 pm »

Hello all, I have a WRT54G2 Linksys router and I have had tons of issues playing games like Diablo 3 or Ez Server, Now I was able to correct this issue with Diablo 3 by opening some ports using the port forwarding tool on my router setup.  Does anyone know of any ports that is used for EZ server that i can try to open up to improve latency issue?  I'm at a constant 250ms+ and was using diablo 3, but with port forwarding im down to 99-110ms in diablo 3.....was hoping i could improve my connection.

Thanks,

Nijjin
Logged
hateborne
Legend
*******
Posts: 2282


Don't nerf me bro!


View Profile
« Reply #1 on: July 17, 2013, 01:31:29 pm »

Hello all, I have a WRT54G2 Linksys router and I have had tons of issues playing games like Diablo 3 or Ez Server, Now I was able to correct this issue with Diablo 3 by opening some ports using the port forwarding tool on my router setup.  Does anyone know of any ports that is used for EZ server that i can try to open up to improve latency issue?  I'm at a constant 250ms+ and was using diablo 3, but with port forwarding im down to 99-110ms in diablo 3.....was hoping i could improve my connection.

Thanks,

Nijjin

I have nothing forwarded and have no issues. It depends on where you live too. EZ Server shows up as possibly Indiana for me.

If you were to forward ports, 5998 TCP and 5999 TCP would be the only ones that I could think of to forward.


-Hate
Logged

I'm so sorry Hunter, I tried...
Nijjin
Newbie
*
Posts: 28


View Profile
« Reply #2 on: July 17, 2013, 01:34:24 pm »

Appreciate the Response Hate  Grin I just did a firmware update also, hopefully this will correct the issues I am seeing.
Logged
hateborne
Legend
*******
Posts: 2282


Don't nerf me bro!


View Profile
« Reply #3 on: July 17, 2013, 01:41:32 pm »

Appreciate the Response Hate  Grin I just did a firmware update also, hopefully this will correct the issues I am seeing.

Keep in mind also that EZ Server is run off of consumer internet with a moderate single server. Diablo 3 is running off of a server farm with MANY MANY open internet access pipes.


-Hate
Logged

I'm so sorry Hunter, I tried...
red2
Full Member
***
Posts: 140


View Profile
« Reply #4 on: July 17, 2013, 03:57:40 pm »

not that i recommend this, as i do not believe it is needed ..
here is a post on how to do it
http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/Everquest.htm
here is the relevant kb article from sony on the specific ports
http://help.soe.com/app/answers/detail/a_id/1668/kw/ports/p/1
Please note that EverQuest opens a random UDP data port from the player's PC every time EverQuest is run. Thus, the need to have all ports >1023 available.

In general, you can set up "Port Triggering" to allow our games to connect. To do so, you need to set up the start and port of the Trigger range to be 7000, and for the Triggered range, use the start port 1023 and the end port 65535. This is for both TCP and UDP packets. A good source of information on Port Triggering is http://www.portforward.com but you may want to contact the router manufacturer or your ISP for more specific information.

also it may be a good idea to open port 5999
http://www.eqemulator.org/wiki/wikka.php?wakka=PlayGuide

this is an especially old router. they are know for slowly dying. it is HIGHLY recommended you get a new one to fix this problem.
Logged
hateborne
Legend
*******
Posts: 2282


Don't nerf me bro!


View Profile
« Reply #5 on: July 17, 2013, 04:21:49 pm »

not that i recommend this, as i do not believe it is needed ..
here is a post on how to do it
http://portforward.com/english/routers/port_forwarding/Linksys/WRT54G/Everquest.htm
here is the relevant kb article from sony on the specific ports
http://help.soe.com/app/answers/detail/a_id/1668/kw/ports/p/1
Please note that EverQuest opens a random UDP data port from the player's PC every time EverQuest is run. Thus, the need to have all ports >1023 available.

In general, you can set up "Port Triggering" to allow our games to connect. To do so, you need to set up the start and port of the Trigger range to be 7000, and for the Triggered range, use the start port 1023 and the end port 65535. This is for both TCP and UDP packets. A good source of information on Port Triggering is http://www.portforward.com but you may want to contact the router manufacturer or your ISP for more specific information.

also it may be a good idea to open port 5999
http://www.eqemulator.org/wiki/wikka.php?wakka=PlayGuide

this is an especially old router. they are know for slowly dying. it is HIGHLY recommended you get a new one to fix this problem.

I cannot advice you to open ALL ports 1024-65535 UDP. That's an extremely huge risk to simply lower your latency. The random ports are opened using standard communication procedures and should NOT be required to be opened. Damn near every relatively recent network ready device should be able to automatically create/open/close the source ports without causing hell or needing to open every port.

I do agree that upgrading the router might be the best choice. In the US, a comparable Cisco/Linksys device will be $39-59 with Netgear below that.


-Hate
Logged

I'm so sorry Hunter, I tried...
lerxst2112
Hero Member
*****
Posts: 724


View Profile
« Reply #6 on: July 17, 2013, 04:34:38 pm »


You shouldn't need any port forwarding to play EQ.  Make sure you have QoS turned off in your router as it can affect latency if you have other traffic, like torrents/streaming going at the same time
Logged
Pages: [1]
Print
Jump to:  

Recent

Stats

Members
  • Total Members: 6149
  • Latest: Acaelis
Stats
  • Total Posts: 65081
  • Total Topics: 5061
  • Online Today: 240
  • Online Ever: 8678
  • (December 19, 2022, 02:32:09 pm)
Users Online
Users: 0
Guests: 173
Total: 173
TinyPortal v1.0 beta 4 © Bloc