• April 25, 2024, 11:14:42 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Pages: 1 [2] 3 4

Author Topic: Port Forwarding and Triggering  (Read 33801 times)

Mogres

  • Level 1 Member
  • *
  • Posts: 17
Re: Port Forwarding and Triggering
« Reply #15 on: February 02, 2012, 01:07:29 PM »

idk if the pm got to you or not

and how will i know your on?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding and Triggering
« Reply #16 on: February 02, 2012, 05:14:02 PM »

Got 4500 on to Modems DMZ. Need to get Mine Craft Server configured now.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

XS

  • Level 4 Member
  • ****
  • Posts: 390
Re: Port Forwarding and Triggering
« Reply #17 on: February 03, 2012, 05:52:01 AM »

Is port triggering safe to use under application rules?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding and Triggering
« Reply #18 on: February 03, 2012, 07:14:57 AM »

I would presume it's as safe as any other feature. Just need to figure out what is needed for it to be used is all. I would not recommend it for gaming. I would presume that PT might not have the performance capabilities to keep up with that kind of operation. I presume that applications that only need some form of intermittent connection would PT be a good option. I haven't used it much if at all. QoS seems to handle my needs.  ;D
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

XS

  • Level 4 Member
  • ****
  • Posts: 390
Re: Port Forwarding and Triggering
« Reply #19 on: February 03, 2012, 08:27:23 AM »

Thanks for the reply Fur, the reason I was wondering because I decided to try out port triggering for my two Xbox's on ports 3074 (both) and port 88UDP the other day. 
I only have been able to get a few games in so far and I have to say those games have been some of the best connection games I have edxperienced in MW3.  My son has alos noticed a difference for the better.  However it is too soon to tell and could be coincedence.  Anyway I just don't want to leave my self opened to get hacked.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding and Triggering
« Reply #20 on: February 03, 2012, 08:30:47 AM »

Let us know how that does. Might be a good alternative to test out for xbox. Game consoles aren't generally known for getting hacked. It's the accounts that get hacked.  >:( I had mine hacked last year.  >:(
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

XS

  • Level 4 Member
  • ****
  • Posts: 390
Re: Port Forwarding and Triggering
« Reply #21 on: February 03, 2012, 08:44:41 AM »

Ugh, no good man!  I hate hackers.  Anyway, if what I read how port triggering works on multiple consoles is that you have to open the ports listed for everything on your network since there is no entry for a specific IP address under "special applications".  Does this sound correct?
FYI, I am still using game fuel too.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding and Triggering
« Reply #22 on: February 03, 2012, 09:36:09 AM »

Yes thats right. Maybe you can post a screen capture of how you have that set up?  ::)
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

XS

  • Level 4 Member
  • ****
  • Posts: 390
Re: Port Forwarding and Triggering
« Reply #23 on: February 03, 2012, 09:58:51 AM »

Yeah no problem but it may be awhile to get the screen shot, I am at work.
Anyway here are the links that got me thinking and how to do it.

http://www.pcwintech.com/node/681

And this post but I kept your settings for game fuel and only added ports 3074 and 88 since from what I have read the other ports do not need any type of port forwading/triggering.

http://forums.xbox-scene.com/index.php?showtopic=713469

Anyway, just trying new things out.  I have never had any NAT issues what so ever with this router, I am just tired of lagging in MW3.  :D
« Last Edit: February 03, 2012, 10:04:47 AM by XS »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding and Triggering
« Reply #24 on: February 03, 2012, 10:28:04 AM »

I know and even though we can try to eliminate as much lag on these routers, there will always be some form of LAG as others we play with are probably not generally setting up there routers or doing any tweeking to make sure they are working well as we do.

I would like or you to test with out port 88. Thats not a high bandwidth or high priority port and is only intermittently used. Just 3074 seems to be the most important one. Let us know what the results are. I'll give this a try this weekend and see.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

XS

  • Level 4 Member
  • ****
  • Posts: 390
Re: Port Forwarding and Triggering
« Reply #25 on: February 03, 2012, 11:14:51 AM »

Will do man, Yeah I think port 88 is only for voice however MS recommends you forward this port if you are having NAT issues and my NAT is always open.

Hopefully I will be able to get some game time in this weekend to know for sure.  I am sure my son will so I could always ask him if he still notices a difference.

Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding and Triggering
« Reply #26 on: February 03, 2012, 11:23:37 AM »

WE should SIR.  ::)
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

XS

  • Level 4 Member
  • ****
  • Posts: 390
Re: Port Forwarding and Triggering
« Reply #27 on: February 07, 2012, 09:00:36 PM »

Okay, sorry for the delay, but here are the screen shots.  I also added my screen shot of Game fuel since I have been playing around with priority settings too, since I thought priority 1 was too high so I went back to Furry original settings (close to).

Furry, have you tried out port triggering yet? If so any feedback?  Do you or anyone else know what port 53 (DNS) is used for?


Anyway, I definitely notice a difference since making these changes with lag and hit detection, even my son noticed it and said "Dad, I don't know why am I doing so good lately." lol.
Both of our KDR has gone up slightly in TDM over the weekend so I happy with the results so far. ;D



Gamefuel


Can everyone see the screenshots?  If not let me know.
« Last Edit: February 08, 2012, 06:08:31 AM by XS »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Port Forwarding and Triggering
« Reply #28 on: February 08, 2012, 07:53:22 AM »

I did get a chance to test it out for one night. Not sure if I saw any changes and however conditions that night seemed laggy, possibly due to other users. I noticed at one point I had one red bar in MW3.  :o then it all came back. I haven't had a chance to continue as I've changed routers for testing.  ::) I'll come back to this though and let you know as I do want to see if PT will help out more. If so then we'll update the sticky.  ;D
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

XS

  • Level 4 Member
  • ****
  • Posts: 390
Re: Port Forwarding and Triggering
« Reply #29 on: February 08, 2012, 11:06:50 AM »

Hmm, I may have spoke to soon about PT, I decided to pull actual real data using the COD Elite website.  I know its not 100% accurate but at least its something.  I could only go back to 1/31 and I turned on PT on 2/1.
Anyway, I pulled my sons and my combat record and compared stats pre and post PT.  His KDR went up +.073 and mine actually went down -.061.

I am thinking the improvement I saw has more to do with the changes I made to the Gamefuel rules.  I added ports 88 and 80 to the list, changed port 3074 priority from a 1 to 30 and port 53 from a 1 to 40.
I made these changes to GF a day or two before enabling port triggering so I may have confused the two.

Anyway, just wanted to share more accurate feedback and I think I may disable port triggering and see there are any changes in game play.  This time I will be more diligent on actual data instead of going off of feelings.
Logged
Pages: 1 [2] 3 4