View Single Post
Old 10-08-2013, 09:25 PM   #4
Thane1
Connoisseur
Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.Thane1 knows how to set a laser printer to stun.
 
Thane1's Avatar
 
Posts: 73
Karma: 95862
Join Date: Jan 2013
Device: Kobo Touch, Kobo Mini
Quote:
Originally Posted by Rev. Bob View Post
On a related note - I'd really love to be able to connect my Glo to a WiFi LAN that isn't connected to the internet.
It must "dial" home after it makes a connection to the network. I wonder if using a packet analyzer would allow you to find out what the reader is trying to connect with. Knowing still doesn't address your issue but perhaps the guys in the developer area could use it to look for whatever part of the code is responsible for making the call. If Kobo doesn't change the behaviour in the firmware you might be able to, or redirect the readers request to something on your private network which simulates a response the reader finds acceptable.
Thane1 is offline   Reply With Quote