PoTski |
Mardi 13 Janvier 2015 à 20:15
|
PoTski
|
Just an FYI.
If you have issues logging in with connection Error: connection failure its probably this fix.
The reason:
Riot changed IPs on 11.01.2015, or they actually changed frontend infrastructure and are now running protection so they can prevent an attack that uses different timestamps on multiple packets for the same sequence number.
solution put by MetaphysicalDrama on WineHQ:
"From yesterday evening seems like some (or all) linux users can't login on EUW servers (PBE was working fine, i honestly don't know about other servers)
After some investigations today i found the problem were TCP timestamps
These can be disabled in /proc/sys/net/ipv4/tcp_timestamps
Just run from root:
# echo 0 > /proc/sys/net/ipv4/tcp_timestamps
Just thought i should post it here as ppl tend to check this forum first.
Have a nice one.
Regads,
PoTski
|
Lavayo |
Mercredi 14 Janvier 2015 à 8:10
|
Lavayo
|
Lol still shows Connection Error.
|
PoTski |
Mercredi 14 Janvier 2015 à 12:17
|
PoTski
|
Lol still shows Connection Error.
Edité par PoTski
|
Alienzapper |
Mercredi 14 Janvier 2015 à 17:17
|
Alienzapper
|
I have those retrying 1,2 and 3 connection error? Do you know any fix for this ?
edit: its back to the "normal" connection error now...
Edité par Alienzapper
|
PoTski |
Mercredi 14 Janvier 2015 à 19:14
|
PoTski
|
I have those retrying 1,2 and 3 connection error? Do you know any fix for this ?
edit: its back to the "normal" connection error now...
|
PoTski |
Mercredi 14 Janvier 2015 à 19:20
|
PoTski
|
if your on ubuntu you want to make it permanent. nano or vi the rc.local file
nano /etc/rc.local
and add:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
before the exit 0 part. Should look like this:
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
exit 0
Edité par PoTski
|
petch |
Mercredi 14 Janvier 2015 à 22:19
|
petch
|
Or better yet add net.ipv4.tcp_timestamps=0 line to /etc/sysctl.conf, that's what it's for
|
osbon |
Mercredi 14 Janvier 2015 à 22:28
|
osbon
|
Just an FYI.
If you have issues logging in with connection Error: connection failure its probably this fix.
The reason:
Riot changed IPs on 11.01.2015, or they actually changed frontend infrastructure and are now running protection so they can prevent an attack that uses different timestamps on multiple packets for the same sequence number.
solution put by MetaphysicalDrama on WineHQ:
After some investigations today i found the problem were TCP timestamps
These can be disabled in /proc/sys/net/ipv4/tcp_timestamps
Just run from root:
# echo 0 > /proc/sys/net/ipv4/tcp_timestamps
Hi potski im running ubuntu and im playing lol over wine and playonlinux.
sorry that im new with ubuntu and dont undestand all what u write. I also have the connection error since the new lol patch. So are there a solution for it ? can u tell me how to fix it like what i have to write down in terminal or what i should open and do ? cauz all these codes u write there i do not understand em ;(
so #echo 0> /proc/sys/net/ipv4/tcp-timestamps where do i have to write it ?
thanks for helping me and sry that im new on ubuntu hope i can play lol again soon (btw im on EUW)
|
osbon |
Mercredi 14 Janvier 2015 à 22:30
|
osbon
|
Just an FYI.
If you have issues logging in with connection Error: connection failure its probably this fix.
The reason:
Riot changed IPs on 11.01.2015, or they actually changed frontend infrastructure and are now running protection so they can prevent an attack that uses different timestamps on multiple packets for the same sequence number.
solution put by MetaphysicalDrama on WineHQ:
After some investigations today i found the problem were TCP timestamps
These can be disabled in /proc/sys/net/ipv4/tcp_timestamps
Just run from root:
# echo 0 > /proc/sys/net/ipv4/tcp_timestamps
Hi potski im running ubuntu and im playing lol over wine and playonlinux.
sorry that im new with ubuntu and dont undestand all what u write. I also have the connection error since the new lol patch. So are there a solution for it ? can u tell me how to fix it like what i have to write down in terminal or what i should open and do ? cauz all these codes u write there i do not understand em ;(
so #echo 0> /proc/sys/net/ipv4/tcp-timestamps where do i have to write it ?
thanks for helping me and sry that im new on ubuntu hope i can play lol again soon (btw im on EUW)
|
PoTski |
Jeudi 15 Janvier 2015 à 17:09
|
PoTski
|
Just an FYI.
If you have issues logging in with connection Error: connection failure its probably this fix.
The reason:
Riot changed IPs on 11.01.2015, or they actually changed frontend infrastructure and are now running protection so they can prevent an attack that uses different timestamps on multiple packets for the same sequence number.
solution put by MetaphysicalDrama on WineHQ:
After some investigations today i found the problem were TCP timestamps
These can be disabled in /proc/sys/net/ipv4/tcp_timestamps
Just run from root:
# echo 0 > /proc/sys/net/ipv4/tcp_timestamps
Hi potski im running ubuntu and im playing lol over wine and playonlinux.
sorry that im new with ubuntu and dont undestand all what u write. I also have the connection error since the new lol patch. So are there a solution for it ? can u tell me how to fix it like what i have to write down in terminal or what i should open and do ? cauz all these codes u write there i do not understand em ;(
so #echo 0> /proc/sys/net/ipv4/tcp-timestamps where do i have to write it ?
thanks for helping me and sry that im new on ubuntu hope i can play lol again soon (btw im on EUW)
|
PoTski |
Jeudi 15 Janvier 2015 à 17:10
|
PoTski
|
Or better yet add net.ipv4.tcp_timestamps=0 line to /etc/sysctl.conf, that's what it's for
|
petch |
Jeudi 15 Janvier 2015 à 19:22
|
petch
|
won't work, because the output redirection is done by the user shell, before sudo is even launched.
Eventually you can recommend
echo 0 | sudo tee /proc/sys/net/ipv4/tcp_timestamps
that will work because it doesn't use redirections, just tee talking an output filename parameter
|
alemaaltevinden |
Jeudi 15 Janvier 2015 à 22:19
|
alemaaltevinden
|
|
asenruskiq |
Samedi 17 Janvier 2015 à 15:37
|
asenruskiq
|
Hi Pottsky i am werry new in Ubuntu and i dont know anything about programming.Can you make a short youtube video hov to do this.
Or better yet add net.ipv4.tcp_timestamps=0 line to /etc/sysctl.conf, that's what it's for
|
sxw |
Jeudi 26 Février 2015 à 11:13
|
sxw
|
I've seen some posts lately about LoL working on Linux and stuff. So I thought I try once again to set everything up. The installation worked fine using the PoL-script, but I end up with this "did not receive a response from server; retrying"-1-2-3-connection error followed up by the error message "The login server did not respond. You may have a connection issue that is not related to the League of Legends server. [...]".
Setting net.ipv4.tcp_timestamps=0 did not work. I did it as root, so petchs comment does not apply.
The wine version installed is "1.7.33-LeagueOfLegends2". Debugging output does not say anything and the only error in console output is "playonlinux/lib/scripts.lib: line 957: lsb_release: command not found."
Do you have any other idea how to resolve this issue?
Hardware: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, NVIDIA Corporation GF114M [GeForce GTX 570M], 8Gb RAM
System: Debian testing (jessie, 8.0), amd64; nvidia driver version 340.65; PoL 4.2.5; KDE 4.14.2
|
Hohomaster |
Jeudi 26 Février 2015 à 15:58
|
Hohomaster
|
How do i root what does it mean?
I have been trying to play league for the past 2 weeks and it doesnt seem to work. It always stop and either 80% or when the Kbs reaches 0. Please tell me if there is anything i can do becuase I'm bored out of my mind and need something fun to do.
|
sxw |
Vendredi 27 Février 2015 à 12:40
|
sxw
|
If you don't know, what root is you should probably read some basic Linux guide. Regarding your 80% problem:
I had the same issue a few times. Retrying worked for me once. If you have a working copy of LoL on a Windows partition, you can copy this folder over your Linux folder and restart the client. This worked for me every time.
Edité par sxw
Hardware: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, NVIDIA Corporation GF114M [GeForce GTX 570M], 8Gb RAM
System: Debian testing (jessie, 8.0), amd64; nvidia driver version 340.65; PoL 4.2.5; KDE 4.14.2
|