MovaaN Posted October 29, 2015 Report Share Posted October 29, 2015 (edited) Check this! 19.11.2015 http://nhlgamer.com/community/topic/126-ea-poll-about-lag/#comment-623 First off, this ISN'T a fix for everyone and probably won't work for everybody. Secondly this mainly reference on everything that people know at this time. Okay. There is couple of things that may help on home captain and home team lag issues. Always make sure that your lobby leader isn't team captain at class selection screen! So far I've had and seen massive 1-3s input delays on captain if the player was lobby leader too. Try to change lobby leader as someone else than the player who usually has team captaincy too. This is the technical side of this "fix". Try to block with either block URL/IP or Parental control on your ROUTER. I know that there lot of different routers out there and some do have ability to block and others have only parental control. This may or may not help you but this doesn't either do no harm for you. Sidebar: Your NAT type may drop from 1 to 2 if you use bridged mode on router. Mine did, but connections have been good. If you lose connections all together on you system, then probably you did something wrong. Block these: 159.153.95.65 and/or gosprodfeapp0474.ea.com Example from my router: I can't block IP's or URL's, so I use Parental control. I have put both IP and URL on blocked lists of Keywords and Blocked Domains. I also use Time of Day rule that is on everyday and all day. I feel that this has helped little bit though I didn't have lot of problem even before. It did drop my NAT from 1 to 2 but still overall feel is good. Q: How do I do this on my router? A: I don't know, I've learned to use my router (Cisco EPC3828D) by googling and reading user's manual. And just as a reminder This isn't permanent fix and won't probably work on everyone. But this is a gather from lot of forums and there has been lot of positive results. EA is still working on this whole problem but there is no ETA on the fix. I try to update everytime there is something new on the matter or maybe some tips. Otherwise it seems that we just have to be patient. Please spread word on this! @Kenu maybe pin this topic so people can easily find it? edit: And of course if none of these help and like changing NAT from 1 to 2 makes games more laggy et cetera then you should reverse all changes ^^ edit: as @gzell60 said that their best connection comes at home when a specific player is lobby leader and team captain too. People you can use your own brains to figure things out, these are tips from majority. Update from EA forums: UPDATE [11/06] * Dev and QA teams investigated multiple leads but nothing conclusive pointing to the root cause of this issue thus far. * Our senior engineers have also looked at the IP blocking workaround that was circulating the community and it doesn't look like it would specifically fix the captain lag issue. Also, for some users it could block their ability to play altogether. * While we have reached out directly to several members of the community, we are unable to identify a pattern of behaviour to help establish the conditions to reproduce the issue. * We need more info but we will continue to dedicate time and resources to this. The team is in the process of preparing a detailed survey questionnaire (will post link here) to get more focused input and feedback. Edited November 19, 2015 by MovaaN EA forum update 1 Quote Link to comment Share on other sites More sharing options...
eyebiz Posted October 29, 2015 Report Share Posted October 29, 2015 Block these: 159.153.95.65 and/or gosprodfeapp0474.ea.74The DNS is actually gosprodfeapp0474.ea.com but I'm sure that's just a typo. Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 29, 2015 Author Report Share Posted October 29, 2015 yup Quote Link to comment Share on other sites More sharing options...
gzell60 Posted October 29, 2015 Report Share Posted October 29, 2015 (edited) Always make sure that your lobby leader isn't team captain at class selection screen! So far I've had and seen massive 1-3s input delays on captain if the player was lobby leader too. Try to change lobby leader as someone else than the player who usually has team captaincy too.There is one guy in our team who ends up being captain in both lobbies most of the time, and if that is the case the connection is great in 9 out of 10 cases. Not sure if this is a 'fix' you should recommend.Also, what is your source on blocking those 2 IP's? I think I saw people on Reddit talk about this so I'd like to know where this is coming from.EDIT: I found the source myself:http://leaguegaming.com/forums/index.php?threads/here-is-the-fix-for-input-delay-posted-on-pg-1-initial-post-also-includes-past-posts.223931/ Edited October 29, 2015 by gzell60 Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 29, 2015 Author Report Share Posted October 29, 2015 There is one guy in our team who ends up being captain in both lobbies most of the time, and if that is the case the connection is great in 9 out of 10 cases. Not sure if this is a 'fix' you should recommend.Also, what is your source on blocking those 2 IP's? I think I saw people on Reddit talk about this so I'd like to know where this is coming from.EDIT: I found the source myself:http://leaguegaming.com/forums/index.php?threads/here-is-the-fix-for-input-delay-posted-on-pg-1-initial-post-also-includes-past-posts.223931/Of course if this is good in your case, then you of course use it but most of the people I've talked to has had that both lobby captaincy problem. That is why recommend this. People ofc should use their own brains Quote Link to comment Share on other sites More sharing options...
gzell60 Posted October 29, 2015 Report Share Posted October 29, 2015 Of course if this is good in your case, then you of course use it but most of the people I've talked to has had that both lobby captaincy problem. That is why recommend this. People ofc should use their own brains The latest edit in your opening post is a bit misleading though. It really just works if this one specific guy is captain in both lobbies. Whenever I am captain in both lobbies we normally experience horrible amounts of lag. Maybe you want to add that, tell people to try different hosts. Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 29, 2015 Author Report Share Posted October 29, 2015 (edited) This is all about at this point of trial and error, one thing may work on one, others for some and third for some. I've just pointed and given the tips that has been successful for lot of players. Edited October 29, 2015 by MovaaN Quote Link to comment Share on other sites More sharing options...
gzell60 Posted October 30, 2015 Report Share Posted October 30, 2015 Yesterday I used my router's parental controls to block the IP / host name, and the first 2 games were running smooth (we were 5 players). Afterwards a 6th player joined us, and I experienced the delay again. Not convinced about how effective that method is, but I'll keep an eye on it. Maybe everyone of us needs to block those addresses though one player within the lineup should be sufficient (at least in theory). Quote Link to comment Share on other sites More sharing options...
eBasstian Posted October 30, 2015 Report Share Posted October 30, 2015 Two days ago my connection was awesome both home and away when I was cap. Yesterday we played two games home there I was the cap, and that was the worst connection I have had except when I was on a bad internet and downloaded something. EA FIX THIS ASAP. Quote Link to comment Share on other sites More sharing options...
imosi Posted October 30, 2015 Report Share Posted October 30, 2015 So, if I did all those things. (blocked url and IP) and I still can ping to both. It didn't work? Quote Link to comment Share on other sites More sharing options...
gzell60 Posted October 30, 2015 Report Share Posted October 30, 2015 (edited) 41 minutes ago, imosi said: So, if I did all those things. (blocked url and IP) and I still can ping to both. It didn't work? You should be able to ping them, but a tracert should end with 'unreachable'. Don't quote me on that, though. Edited October 30, 2015 by gzell60 Quote Link to comment Share on other sites More sharing options...
imosi Posted October 30, 2015 Report Share Posted October 30, 2015 (edited) Anyone? Edit: I still manage to traceroute the IP and url.. When I block the IP through my routers firewall (asus rt-n66u) it asks for a port range? I dont know what to put in that slot. Edited October 30, 2015 by imosi Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 30, 2015 Author Report Share Posted October 30, 2015 57 minutes ago, imosi said: Anyone? Edit: I still manage to traceroute the IP and url.. When I block the IP through my routers firewall (asus rt-n66u) it asks for a port range? I dont know what to put in that slot. try 1-65535, that is all I can you with that :) Quote Link to comment Share on other sites More sharing options...
gzell60 Posted October 30, 2015 Report Share Posted October 30, 2015 1 hour ago, imosi said: Anyone? Edit: I still manage to traceroute the IP and url.. When I block the IP through my routers firewall (asus rt-n66u) it asks for a port range? I dont know what to put in that slot. If you go to Firewall -> URL Filter, you can block the host name without a port range as far as I can tell from a video. Quote Link to comment Share on other sites More sharing options...
XelsFIN Posted October 30, 2015 Report Share Posted October 30, 2015 If anybody is using any of the Buffalo wrt-line routers go to Administration -> Commands paste these, and click run commands button: iptables -I OUTPUT -d 159.153.95.65 -j logdropiptables -I FORWARD -d 159.153.95.65 -j DROP now you should have no way of accessing that server, cant ping or trace. If you reboot the router then you have to this again, i don't advise using the write to firewall option in commands section as iptables command writes directly to Linux kernel running on your router. 1 Quote Link to comment Share on other sites More sharing options...
Administrators Kenu Posted October 31, 2015 Administrators Report Share Posted October 31, 2015 I moved this topic to the NHL 16-section, as I see that is more fitting. Has anyone blocked the IP using a Cisco router? I'm using the Cisco EPC3825 router (provided by DNA) and I can't seem to get it working. I tried using the IP-filtering page for this in the router settings, but adding that IP gives me an "Invalid IP address" error. Is it better to connect to the router some other way than through the browser interface? I don't see any command options on my router, similar to what @XelsFIN mentioned about his Buffalo. Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 31, 2015 Author Report Share Posted October 31, 2015 (edited) Yeah the IP filtering on it is to block local area network IPs to connect to internet. And that cisco is very similar to mine. I think only way might be parental block if that works: Manual Edited October 31, 2015 by MovaaN 1 Quote Link to comment Share on other sites More sharing options...
XelsFIN Posted October 31, 2015 Report Share Posted October 31, 2015 12 minutes ago, Kenu said: I moved this topic to the NHL 16-section, as I see that is more fitting. Has anyone blocked the IP using a Cisco router? I'm using the Cisco EPC3825 router (provided by DNA) and I can't seem to get it working. I tried using the IP-filtering page for this in the router settings, but adding that IP gives me an "Invalid IP address" error. Is it better to connect to the router some other way than through the browser interface? I don't see any command options on my router, similar to what @XelsFIN mentioned about his Buffalo. The web interface should suffice, if there is no option in the webinterface then i highly doubt it´s possible to do with said router. Here is what mine looks like, quite basic router model, Buffalo Nfiniti WZR-HP-G300NH2EU: 1 Quote Link to comment Share on other sites More sharing options...
Administrators Kenu Posted October 31, 2015 Administrators Report Share Posted October 31, 2015 19 minutes ago, MovaaN said: Yeah the IP filtering on it is to block local area network IPs to connect to internet. And that cisco is very similar to mine. I think only way might be parental block if that works: Manual Thanks. I did that, but I am still able to ping both the IP and the url. Aren't you? Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 31, 2015 Author Report Share Posted October 31, 2015 (edited) Yes I'm, try running at cmd and write there tracert 159.153.95.65. It isn't abnormal to be able ping it but try to look using that command, does it allow you to route your traffic there Edited October 31, 2015 by MovaaN Quote Link to comment Share on other sites More sharing options...
Administrators Kenu Posted October 31, 2015 Administrators Report Share Posted October 31, 2015 8 minutes ago, MovaaN said: Yes I'm, try running at cmd and write there tracert 159.153.95.65. It isn't abnormal to be able ping it but try to look using that command, does it allow you to route your traffic there I guess it doesn't? traceroute to 159.153.95.65 (159.153.95.65), 64 hops max, 52 byte packets 1 192.168.0.1 (192.168.0.1) 0.500 ms 0.228 ms 0.184 ms 2 0.0.0.0 (0.0.0.0) 6.357 ms 7.756 ms 6.280 ms 3 hel5-sr4.dnaip.fi (62.78.106.176) 7.880 ms 7.780 ms 7.994 ms 4 esp2-tr2.dnaip.fi (62.78.107.114) 8.059 ms 7.830 ms 7.906 ms 5 hel5-tr3.dnaip.fi (62.78.107.113) 16.969 ms hel5-tr3.dnaip.fi (62.78.107.40) 16.402 ms rai1-tr2.dnaip.fi (62.78.107.4) 15.412 ms 6 rai1-tr1.dnaip.fi (62.78.107.13) 16.139 ms 16.196 ms rai1-tr1.dnaip.fi (62.78.107.68) 16.006 ms 7 tuk2-sr1.dnaip.fi (62.78.107.174) 15.520 ms 16.039 ms 15.769 ms 8 te0-7-0-2.ccr21.sto01.atlas.cogentco.com (149.6.168.129) 16.822 ms te0-0-0-7.ccr21.sto01.atlas.cogentco.com (149.6.168.13) 15.608 ms te0-7-0-2.ccr21.sto01.atlas.cogentco.com (149.6.168.129) 17.203 ms 9 be2397.ccr22.sto03.atlas.cogentco.com (130.117.50.129) 16.648 ms 17.175 ms be2396.ccr21.sto03.atlas.cogentco.com (130.117.50.121) 17.554 ms 10 be2282.ccr42.ham01.atlas.cogentco.com (154.54.72.105) 37.045 ms be2281.ccr41.ham01.atlas.cogentco.com (154.54.63.1) 35.047 ms be2282.ccr42.ham01.atlas.cogentco.com (154.54.72.105) 35.967 ms 11 be2257.ccr41.fra03.atlas.cogentco.com (130.117.49.29) 43.703 ms be2268.ccr42.fra03.atlas.cogentco.com (130.117.50.181) 43.708 ms be2257.ccr41.fra03.atlas.cogentco.com (130.117.49.29) 46.776 ms 12 be2184.agr21.fra03.atlas.cogentco.com (130.117.48.69) 44.264 ms be2188.agr21.fra03.atlas.cogentco.com (130.117.48.113) 48.415 ms be2184.agr21.fra03.atlas.cogentco.com (130.117.48.69) 44.355 ms 13 telia.fra03.atlas.cogentco.com (130.117.14.214) 43.119 ms 45.300 ms 41.536 ms 14 ae8.mpr1.fra3.de.zip.zayo.com (64.125.26.233) 47.167 ms 44.624 ms 47.949 ms 15 ae4.cr1.ams5.nl.zip.zayo.com (64.125.32.106) 41.965 ms 46.196 ms 42.361 ms 16 ae0.cr1.ams10.nl.zip.zayo.com (64.125.27.62) 46.790 ms 42.363 ms 46.722 ms 17 ae7.cr2.dca2.us.zip.zayo.com (64.125.27.33) 131.163 ms 134.062 ms 135.085 ms 18 ae1.er2.iad10.us.zip.zayo.com (64.125.20.122) 129.565 ms 131.294 ms 134.133 ms 19 64.125.199.190.t00673-02.above.net (64.125.199.190) 133.241 ms 130.559 ms 135.846 ms 20 * * * 21 * * * 22 * * * 23 * * * Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 31, 2015 Author Report Share Posted October 31, 2015 I think it doesn't reach it, maybe people with better knowledge can confirm this :) Quote Link to comment Share on other sites More sharing options...
Administrators Kenu Posted October 31, 2015 Administrators Report Share Posted October 31, 2015 18 minutes ago, Kenu said: I guess it doesn't? traceroute to 159.153.95.65 (159.153.95.65), 64 hops max, 52 byte packets 1 192.168.0.1 (192.168.0.1) 0.500 ms 0.228 ms 0.184 ms 2 0.0.0.0 (0.0.0.0) 6.357 ms 7.756 ms 6.280 ms 3 hel5-sr4.dnaip.fi (62.78.106.176) 7.880 ms 7.780 ms 7.994 ms 4 esp2-tr2.dnaip.fi (62.78.107.114) 8.059 ms 7.830 ms 7.906 ms 5 hel5-tr3.dnaip.fi (62.78.107.113) 16.969 ms hel5-tr3.dnaip.fi (62.78.107.40) 16.402 ms rai1-tr2.dnaip.fi (62.78.107.4) 15.412 ms 6 rai1-tr1.dnaip.fi (62.78.107.13) 16.139 ms 16.196 ms rai1-tr1.dnaip.fi (62.78.107.68) 16.006 ms 7 tuk2-sr1.dnaip.fi (62.78.107.174) 15.520 ms 16.039 ms 15.769 ms 8 te0-7-0-2.ccr21.sto01.atlas.cogentco.com (149.6.168.129) 16.822 ms te0-0-0-7.ccr21.sto01.atlas.cogentco.com (149.6.168.13) 15.608 ms te0-7-0-2.ccr21.sto01.atlas.cogentco.com (149.6.168.129) 17.203 ms 9 be2397.ccr22.sto03.atlas.cogentco.com (130.117.50.129) 16.648 ms 17.175 ms be2396.ccr21.sto03.atlas.cogentco.com (130.117.50.121) 17.554 ms 10 be2282.ccr42.ham01.atlas.cogentco.com (154.54.72.105) 37.045 ms be2281.ccr41.ham01.atlas.cogentco.com (154.54.63.1) 35.047 ms be2282.ccr42.ham01.atlas.cogentco.com (154.54.72.105) 35.967 ms 11 be2257.ccr41.fra03.atlas.cogentco.com (130.117.49.29) 43.703 ms be2268.ccr42.fra03.atlas.cogentco.com (130.117.50.181) 43.708 ms be2257.ccr41.fra03.atlas.cogentco.com (130.117.49.29) 46.776 ms 12 be2184.agr21.fra03.atlas.cogentco.com (130.117.48.69) 44.264 ms be2188.agr21.fra03.atlas.cogentco.com (130.117.48.113) 48.415 ms be2184.agr21.fra03.atlas.cogentco.com (130.117.48.69) 44.355 ms 13 telia.fra03.atlas.cogentco.com (130.117.14.214) 43.119 ms 45.300 ms 41.536 ms 14 ae8.mpr1.fra3.de.zip.zayo.com (64.125.26.233) 47.167 ms 44.624 ms 47.949 ms 15 ae4.cr1.ams5.nl.zip.zayo.com (64.125.32.106) 41.965 ms 46.196 ms 42.361 ms 16 ae0.cr1.ams10.nl.zip.zayo.com (64.125.27.62) 46.790 ms 42.363 ms 46.722 ms 17 ae7.cr2.dca2.us.zip.zayo.com (64.125.27.33) 131.163 ms 134.062 ms 135.085 ms 18 ae1.er2.iad10.us.zip.zayo.com (64.125.20.122) 129.565 ms 131.294 ms 134.133 ms 19 64.125.199.190.t00673-02.above.net (64.125.199.190) 133.241 ms 130.559 ms 135.846 ms 20 * * * 21 * * * 22 * * * 23 * * * Result with parental control turned off (and device rebooted): traceroute to 159.153.95.65 (159.153.95.65), 64 hops max, 52 byte packets 1 192.168.0.1 (192.168.0.1) 0.454 ms 0.289 ms 0.188 ms 2 0.0.0.0 (0.0.0.0) 7.876 ms 8.016 ms 7.795 ms 3 hel5-sr4.dnaip.fi (62.78.106.176) 16.639 ms 7.161 ms 7.294 ms 4 esp2-tr2.dnaip.fi (62.78.107.114) 8.791 ms 7.483 ms 7.748 ms 5 hel5-tr3.dnaip.fi (62.78.107.40) 16.398 ms hel5-tr3.dnaip.fi (62.78.107.113) 16.015 ms 16.417 ms 6 rai1-tr1.dnaip.fi (62.78.107.13) 15.642 ms rai1-tr1.dnaip.fi (62.78.107.42) 17.954 ms 16.022 ms 7 tuk2-sr1.dnaip.fi (62.78.107.174) 16.178 ms 14.656 ms 17.132 ms 8 te0-7-0-2.ccr21.sto01.atlas.cogentco.com (149.6.168.129) 15.358 ms 16.458 ms te0-0-0-7.ccr21.sto01.atlas.cogentco.com (149.6.168.13) 16.536 ms 9 be2397.ccr22.sto03.atlas.cogentco.com (130.117.50.129) 17.058 ms 16.533 ms be2396.ccr21.sto03.atlas.cogentco.com (130.117.50.121) 16.122 ms 10 be2282.ccr42.ham01.atlas.cogentco.com (154.54.72.105) 37.881 ms be2281.ccr41.ham01.atlas.cogentco.com (154.54.63.1) 32.566 ms be2282.ccr42.ham01.atlas.cogentco.com (154.54.72.105) 38.926 ms 11 be2257.ccr41.fra03.atlas.cogentco.com (130.117.49.29) 41.592 ms be2268.ccr42.fra03.atlas.cogentco.com (130.117.50.181) 47.346 ms be2257.ccr41.fra03.atlas.cogentco.com (130.117.49.29) 44.486 ms 12 be2184.agr21.fra03.atlas.cogentco.com (130.117.48.69) 54.459 ms be2188.agr21.fra03.atlas.cogentco.com (130.117.48.113) 522.978 ms be2184.agr21.fra03.atlas.cogentco.com (130.117.48.69) 549.065 ms 13 telia.fra03.atlas.cogentco.com (130.117.14.214) 39.355 ms 39.708 ms 43.958 ms 14 ae8.mpr1.fra3.de.zip.zayo.com (64.125.26.233) 43.593 ms 50.673 ms 47.145 ms 15 ae4.cr1.ams5.nl.zip.zayo.com (64.125.32.106) 45.058 ms 41.427 ms 45.458 ms 16 ae0.cr1.ams10.nl.zip.zayo.com (64.125.27.62) 40.980 ms 45.576 ms 44.343 ms 17 ae7.cr2.dca2.us.zip.zayo.com (64.125.27.33) 134.550 ms 130.464 ms 134.098 ms 18 ae1.er2.iad10.us.zip.zayo.com (64.125.20.122) 129.619 ms 134.271 ms 133.524 ms 19 64.125.199.190.t00673-02.above.net (64.125.199.190) 130.649 ms 134.134 ms 130.189 ms 20 * * * 21 * * * 22 * * I don't know if it's random or not, but the two bolded lines have a much higher value than with parental control. I have run it again and the one that ends with .113 is significantly lower now, but the .69 is between 333-550ms. I will try to reapply the parental control and see how that impacts the result. EDIT: Never over 100ms on the bolded ip's with the parental control on. I'm no expert, but it would seem to be helping. 1 Quote Link to comment Share on other sites More sharing options...
MovaaN Posted October 31, 2015 Author Report Share Posted October 31, 2015 It would seem so, tell how it worked after playing games :) Quote Link to comment Share on other sites More sharing options...
gzell60 Posted November 3, 2015 Report Share Posted November 3, 2015 This is definitely not working for me, unfortunately. I tested it for quite a few days now but the delay persists. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.