![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
Guest
Posts: n/a
|
Roland Perry <roland@perry.co.uk> wrote >In message <slrnj6igkt.eo5.catwheezel@ID-107770.user.individual.net>, at >23:33:01 on Thu, 8 Sep 2011, Whiskers <catwheezel@operamail.com> >remarked: >>> A smart thing to do would be to test connectivity to a known site >>> (e.g. apple.com) but it evidently doesn't do that... >> >>To do that it would have to have successfully nogotiated an IP number with >>the access point first; it's the attempts to do that which which are >>wasting energy and time on smartphones. > >There are simpler ways to test for connectivity than looking for a >website. Trying a DNS server for example. On my laptop the first >application (by far) to notice that a connection has been made is my >VoIP, which is presumably looking for a particular SIP server. However, doesn't DNS get through a lot of the commercial sites? Hence we have e.g. http://thomer.com/howtos/nstx.html ![]() Maybe UDP would be even better but a) only a VPN work work over that and b) surely the commercial wifi APs block UDP... it would be such an obvious workaround. No DHCP required, etc. Also, don't the "pay by the hour" commercial sites use the client MAC # to control access by? |
|
| Copyright ©2007-2008 MacShock.com. |
Powered by vBulletin Copyright ©2000 - 2012, Jelsoft Enterprises Ltd. |