I'm not a networking guy (hate it to be honest), but my understand that according to RFC's, 192.168.x.x was reserved for private IP only, no public addressing. There's no way a ISP would make a private IP range available publically. I suck @ netmasks, so all I can remember is /24 being a standard 256 range. I don't think I've ever seen a /16 or /8 before, but then, I'm not the network guy @ work, that's Tony's role (or the bosses). They frig with the routers etc. I do the web hosting and hosted exchange and complex DNS
Dave
edit: for those curious on netmasks etc:
http://krow.net/dict/subnet.html
Quote:
Originally Posted by mithrandir
I presume you used that address for illustration. 192.168.0.0/16 can not have originated further away from you that your ISP. If it came from anywhere else it would have been dropped. 10.0.0.0/8 172.12.0.0/12 and 192.168.0.0/16 are prohibited outside private networks.
"whois" is the tool of choice as suggested earlier. There are web sites that will run it for you if you don't have a "whois" on your system. Depending on the delegation, you might get some useful information, but you might not.
The other one to try is "traceroute" (or "tracert" for the M$ inclined). The list of routers in the output may help you cut down the possibilities.
|