View Single Post
Old 02-26-2014, 07:34 PM   #37
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by ploum View Post
I don't have the FritzBox. I've tested with several completely unrelated routers and I can reproduce the problem on more than half of them.
But, the number of chipsets used by these routers is a lot less than the number router brands. And some of the router manufacturers use the basic firmware with very few modifications. If there is a common chipset for the routers it doesn't work with, that could explain it.
Quote:
The fact that a reboot of the kobo fixes the issue is the proof that there's something wrong in the Kobo itself.
Probably. But, because it works OK with some routers, it probably means that something the failing routers sends or expects from the Kobo on a reconnect is different from the other routers. Finding out that difference is what is needed.
davidfor is offline   Reply With Quote