You are correct. I went back with JavaScript turned off and they did not mention anything about being able to detect my internal IP. Thanks for the tip.
Tim > On Tue, Dec 28, 2004 at 02:41:24PM -0700, Tim Hogan wrote: >> Hello all, >> >> In an attempt to verify that only what I wanted to get through was >> getting >> through I went to http://www.auditmypc.com/ and there I received the >> surprise message that my internal IP address of 10.1.1.10 was exposed. >> I >> am guessing that my rule set is fine because the scan only showed what I >> expected but what is going on with NAT showing my internal address and >> how >> do I fix it? > > I haven't looked at their site in depth; however, given that it's > browser driven, it may not be anything to do with NAT, but with it > being able to use Javascript and/or Java to retrieve information about > your client system's settings. In this case, there's nothing wrong > with your NAT/IPF configuration, but you might want to disable > Javascript/Java in your browser to avoid leaking information. > > -- Clifton > > -- > Clifton Royston -- [EMAIL PROTECTED] > Tiki Technologies Lead Programmer/Software Architect > Did you ever fly a kite in bed? Did you ever walk with ten cats on your > head? > Did you ever milk this kind of cow? Well we can do it. We know how. > If you never did, you should. These things are fun, and fun is good. > -- Dr. > Seuss >
