Re: "Microsoft Location Finder" - how is it supposed to work ?

On Tue, 25 Oct 2005 20:02:06 -0500, ibuprofin@xxxxxxxxxxxxxxxxxxxxxx
(Moe Trin) wrote:

>In the Usenet newsgroup alt.internet.wireless, in article
><djjpuv$cua$1@xxxxxxxxxxxxxx>, dold@xxxxxxxxxxxxxxxxxxxxxxxx wrote:
>
>>Jeff Liebermann <jeffl@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>>> At this time, yes. The assumption is that you're located somewhat
>>> near your ISP. Of course my home DSL points to my ISP located 12
>>> miles away in another zip code. My office DSL is off by 50 miles.
>>> More work is needed to do this reliably, but it's a start.

>According to ARIN - I'm in New York, but the last identifiable IP
>you see in a traceroute is near San Jose, California, and I'm actually
>near Phoenix, AZ. For more giggles, the subnet below me is in France,
>and the one above me is near Los Angeles. I can guess this based on
>the hostname, but those hostnames don't resolve (or are reachable)
>from the Internet. Seems that some people don't want everyone knowing
>the "company secrets".

ICMP traceroute echoes can easily be forged. I had my office inside
network returning that it was routed through an assortment of RFC1918
non-routable IP addresses for a while. Kinda slowed down the attacks
from the internet for a while. TCI/Comcast was doing the same thing,
although probably not intentionally.

>>The RFC for extending DHCP allows for entering GPS coordinates that would
>>be delivered from a DHCP server to a "port". The grand scheme is to be
>>able to locate an IP phone within a building for E911.

>That might eventually work for DHCP settings - but not static.

http://www.faqs.org/rfcs/rfc3825.html
It's a fair assumption that VoIP phones and PDA's do not use static IP
addressing. One local ISP was having problems with users inventing
their own IP addresses, so they just convinced the RADIUS server to
not authenticate anyone that did not use their DHCP assigned address.

>I also
>wonder how this will fly when IPv6 eventually gets here.

It shouldn't be a problem. The LCI is just another DHCP data type and
does not affect the underlying protocols.

>The earlier attempt at adding location information to DNS (RFC1712)
>made it as far as "Experimental" status. I suppose that's better
>than a draft - but I've not seen many people using it.

The intent of RFC1712 was not to provide VoIP phone locations for 911.
Using DNS for that is ridiculous. Large system may have only one or
two DNS servers located almost anywhere on the planet. Caching DNS
servers will repeat stale location info for days. Short expiry used
to flush and update local caches will increase traffic un-necessarily.
I'm not sure why anyone would even want to know the location of a DNS
server.

However, RFC3825 is quite different. It's designed to provide E911
information sufficient to locate the user in the event of an
emergency. Since the data is stored on the client device (VoIP
phone), the release of that information to NENA is under the control
of the client, as with GPS cell phone location info.


--
Jeff Liebermann jeffl@xxxxxxxxxxxxxxxxxxxxxx
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
.

Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: Domain controllers
    ... other DNS was still on the zones transferred to the new domain controller. ... Both DHCP and WINS databases CAN be move -- there are KB ... from one server to another -- search Googgle against Microsoft ...
    (microsoft.public.win2000.active_directory)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... All you need to do is make sure there are no other DHCP servers running on ... The only time I have seen the connectcomputer error you mentioned about DNS ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: Sending hostname with DHCP
    ... default route and the default dns host. ... Below is my /etc/resolv.conf created by the dhcp client. ... > This seems to depend on the client as much as the server. ...
    (Fedora)
  • Re: An error occured when configuring networking settings. See your network administrator." While tr
    ... The server is not enabled for DHCP so only the router is doing DHCP, ... so I have hard coded the DNS address from the server on the workstation NIC. ... LAN and WAN NICs on your SBS. ...
    (microsoft.public.windows.server.sbs)