Windows 7 Network Awareness: How Windows knows it has an Internet connection
blog.superuser.com
blog.superuser.com
Would this mean that DNS poisoning msftncsi.com would prevent Win7 machines from accessing the internet? Or would this merely cause the 'no internet access' error to be displayed despite your connection working anyway?
(now called iOS 3.0)
- iOS app developer who was there when Apple explained it
It would periodically awaken, see if the wifi is connected, if it is is there connectivity, if there is, go back to sleep, if there is not, turn the wifi off.
I've also wanted to build for Android the same piece of code, but if for 2 or 5 urls it gets back the same page with a checkbox, it checks off the box and sends it back off.
But I am curious, do all those wifi dns terms and agreements hijacking pages break any sort of RFC?
And is there any solution in ip6?
Or is there a real fix possible in ip4?
IPv[46] have nothing to do with it. "Captive portal" pages are meant to prevent you from getting to the larger Internet, until you do whatever magic is required to dismiss them.
That's interesting. How does it detect it's at Google's servers?
I've often had occasions on my non-rooted, gingerbread, nexus one, where the phone believes it is on the net, on wifi, and shunts all activity to wifi, and yet, it's really stuck on one of those captive portal pages.
It even happens if I am just driving down the road.
I had thought that perhaps a small bit of technology would fix that, perhaps by turning the wifi off, or by automatically checking in on starbuck's router, but I am beginning to see I may just have a sick-making sense of entitlement.
Without being terribly cognizant of the RFCs I am surprised these portal captures are within spec.
How is my wanting to either turn my wifi off, or automatically checking a terms and conditions box at a starbucks, or library, or school, or courtroom, or hospital router demonstrating a sick making sense of entitlement?
I would think many people would want such behavior from their phones, but I can see that you and whomeever voted my original question down are genuinely disturbed I would want this.
Annoying? Sure, a little. A "violation of spec" or something to get overly pissed about? Eh, there are far bigger fish to fry.
It's easy to say that when it isn't your responsibility to deal with rightfully frustrated & confused end users that simply want to be able to use this WiFi network like they use every other WiFi network. Connect and forget.
I also have a never-ending hate for WiFi networks that use portals as they break tons of functionality and always have caveats & problems like the ones parent described.
The worst part? Acting very arrogant about it is the standard IT response, and it blatantly and demonstrably decreases security. Users keep splitters, ethernet cables & routers in their offices, in their laptop bags and around the building.
So go ahead, take this attitude towards the end users of your network. Just don't be surprised if the next IT crisis is caused by someone who "just didn't want to deal with the WiFi hassle".
So I go somewhere, flick on my WiFi, and then get frustrated because various tools (say, my native-code Google Reader app) can't communicate. It can't talk to the network because HTTP is trapped.
The thing is, HTTP is the de facto transport for everything. But these authentication/confirmation pages assume that a human will be reading them.
It seems to me that a mechanism that detects the presence of such a trap, and pops up that response page in a browser window for the user to react to, would solve everyone's problem (if inelegantly).
I don't believe the nexus one will connect by itself to any open wap, it will just tell you one is available.
It seems absurd for anyone to think I need to check off the terms and agreements every single time I connect to the open wap, everyone's suspicion of course is that no one ever reads through the terms and agreements, we just check the box to make some lawyer or IT dude happy and continue.
I do understand the desire and even the need for some form of authentication, or notice you are on someone else's network and ought to read what the terms are.
But the behavior of how that is implemented today is totally obnoxious, especially since for the most part, the terms and agreements are boilerplate intended to satisfy some lawyer, and functionally get in the way of why the vendor or site provided the wifi access in the first place.
Netcraft says: F5 Big-IP Microsoft-IIS/7.0 213.199.181.90
But I am curious as to what the real details of the setup are.