I did post an explanation a while back, but I don't know in which thread. The rule is only on Thomson / rebranded routers because they're the only ones that decided to implement it, and as to what it is supposed to do, who knows. It intercepts connections made on UDP ports 27010-11, and the reason it breaks after 60 seconds is because there is a 60 second timeout on the rule - any connections made in this time via this rule time out. You can increase the timeout period, again only using telnet, and it will then break after the new length of time that is put in there. The reason why the rule affects KF, and in general any game that uses Steam master servers including TF2, L4D and the other Valve games, is that the ports used to communicate with these master servers is UDP 27010 and 27011. When the games grab the server list initially (which is set through Steam rather than the games) it uses these ports, which is why if you join through your Friends list or through the Favourites section of the game it avoids the problem.
Some people did say that if you have an application rule part on the web router's interface and added the preset Steam rule then it worked, but from some of the feedback I think it was somewhat of a placebo effect.
If you ever played Company of Heroes, it also has a different issue with that, at least on the v1 Home Hub, where the type of NAT it uses, the most basic one, doesn't work. You can change that to use a different form of NAT too, another simple 1-line command, but they still thought it would be a good idea to not sort that out either. The big problem for consumers is that obviously you need to be somewhat tech-savvy to sort it out, and it took me long enough to work out what was going on, but they will also blame the game developers rather than their own faulty router. Thomson don't want to fix it, BT won't fix it, and o2 won't want to fix it either. The even worse thing is that with the ISPs often locking telnet access out, people in a lot of cases can't fix it either. I was only able to do it on my updated v1 Home Hub by first flashing an old firmware which had access, before they updated it and removed it.
Anyway, thanks again for doing the video guide, I hope it helps a few people out.
Some people did say that if you have an application rule part on the web router's interface and added the preset Steam rule then it worked, but from some of the feedback I think it was somewhat of a placebo effect.
If you ever played Company of Heroes, it also has a different issue with that, at least on the v1 Home Hub, where the type of NAT it uses, the most basic one, doesn't work. You can change that to use a different form of NAT too, another simple 1-line command, but they still thought it would be a good idea to not sort that out either. The big problem for consumers is that obviously you need to be somewhat tech-savvy to sort it out, and it took me long enough to work out what was going on, but they will also blame the game developers rather than their own faulty router. Thomson don't want to fix it, BT won't fix it, and o2 won't want to fix it either. The even worse thing is that with the ISPs often locking telnet access out, people in a lot of cases can't fix it either. I was only able to do it on my updated v1 Home Hub by first flashing an old firmware which had access, before they updated it and removed it.
Anyway, thanks again for doing the video guide, I hope it helps a few people out.
Upvote
0