Originally Posted by tomsem
It's really unfortunate this is the case - I cannot think of any reason except that Amazon thinks the user experience is 'simpler' somehow. Looks like another subject for firstname.lastname@example.org
Not really. The Kindle isn't designed to be used as a interface to your own private network. It is more likely that a user ends up accidentally connecting to a private WiFi network when they wanted internet than aruangra's usage.
In one of the diagnostic info pages, you'll see that it checks whether it can access several different kinds of Kindle servers. One of those checks must determine whether it routes over the WiFi connection or not. As I previously mentioned, the Kindle 3G+WiFi still has a 3G connection even if WiFi is enabled so in these cases, it will just ignore the WiFi connection.
For the intended purpose of a Kindle, the way they've done it is correct. If WiFi has no internet connectivity then fallback to 3G. If you've got a WiFi only Kindle then you can't connect to Amazon anyway.
If you can find out what servers the Kindle is checking against then you may be able to fake it enough that it will think that you've got an internet connection. If it actually talks to the server and does some form of negotiation then this might not be practical however. If it just wants to ping it or maybe connect to see if something is there but doesn't care whether it receives a reply then it'll be fine.