Kenu
-
Posts
2325 -
Joined
-
Last visited
-
Days Won
161
Content Type
Forums
Events
News
News in Russian
GCL News
SCL News
CSCL
Frequently Asked Questions (FAQ)
Blogs
Profiles
Store
Gallery
Posts posted by Kenu
-
-
Hey Classic Style - welcome to the ECL! :)
-
Hey Unstoppable Warriors - welcome to the ECL! :)
-
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
-
-
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 * * *
-
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?
-
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.
-
6 hours ago, MovaaN said:
User tabs on top right corner are slightly covered
Thanks for the feedback - I noticed this too! We'll fix that for sure. :)
-
Hey No Guts No Glory - welcome to the ECL!
-
Very cool to get to know a little about you @Asche! Welcome to the community! :)
-
Hi Everyone,
I have updated the community software during the night.
If you run into any problems, please try logging out and in and doing a hard refresh (http://wiki.scratch.mit.edu/wiki/Hard_Refresh)
If that doesn't help, please let us know your issue in this thread.
-
Welcome to the ECL, Vilppiveikot!
-
Welcome to the ECL, Freddie Mercury Institute!
-
1
-
-
Hey Beniserna! Welcome to the ECL!
-
Welcome to the ECL, Tiger Of Sweden!
-
Welcome to the ECL VEK!
-
1
-
-
There you go.
We can add more players later right? Didn't have all players PSN-names in my head right now.
Thanks - absolutely!
-
I agree the US fix shouldn't work for the EU-players. On the contrary, I think we need to rout through Ireland.
-
Good ol' Finnish Roosters! I've missed you!
Welcome to the ECL!
And thanks @Jorma Parola - let's not forget to thank @Lurkins for his valuable work as well.
-
1
-
-
Welcome to the ECL, TIKI TALK!
-
Im not gonna be captain no matter what, allready having shitty connections and "stuck in the mud" feeling allmost in every game, so i will not take any more delay even it would be minimal.
I dont see any logic on that goalie would not lagg. It will be fucking disaster if goalies need to host every time. You are not gonna see that delay that well because you are not moving that much as other players. I dont see any point if there will be some rule about "who need to be captain" Im just suggest that, anyone can be the host and if its lagg, you can start over with different captain/host. Every team should have enough time for couple of restart if needed..Don't worry OODAP, we are simply testing every angle we can think of,
@Jiihooo86: Please try the different things I listed above, such as exiting the session after inviting everyone else and being re-invited.
-
Happy to have you as a member of the community @MovaaN!
A great example of a good presentation of oneself - just what this New Arrivals category is for.
-
Welcome to the ECL, Sunny Side!
-
Would two teams or 12 people be kind enough to test this for a few games? As they are unranked, you can quit games and start new ones to see if you have different results regarding lag in the different games.
Things to test:
- When playing in a private lobby, is it laggy for 1 player or for more players?
- If only one, is it the one creating the room?
- If yes, try creating the room and inviting everyone, then dropping out yourself and ask to be invited back.
- Is it still lagging? Who is having the most issues?
- If yes, try creating the room and inviting everyone, then dropping out yourself and ask to be invited back.
- If only one, is it the one creating the room?
- Please have all 12 players write down (even just one word from the scale: GREAT, GOOD, ACCEPTABLE, BAD, TERRIBLE) and it would be good to start (and play long enough so everyone has an opinion) at least 10 games, so we can get an ok sample-size.
(Please feel free to come up with things to add to the list of things to try)
Who's in?
Either let everyone know that you have a full team that would like to participate or let us know that you want to join as one person. Thanks!
- When playing in a private lobby, is it laggy for 1 player or for more players?
-
Oh yes! The legendary Mestarit Areenalla! You've been around forever - good to see you again! Welcome to the ECL!
(To the other teams: don't get discouraged if I don't write all of you such a fantastic welcome - I just have years of experience playing against this team )
ECL Registration - Nordic Stars
in ECL - Season 1 (Archive)
Posted
Please don't write if your only intent is to provoke other people.