Obviously a local IP, but what are its functions/purpose?

Thanks for educating the uneducated.

In article <MPG.18bf7ade16e851cb989680@news.grc.com>, shr@p.com says...
> 
> 
> Obviously a local IP, but what are its functions/purpose?
> 
> Thanks for educating the uneducated.
> 
Any available adapter - i.e. not bound to specific IP address.
-- 
Bloated Elvis

In article <MPG.18bf7ade16e851cb989680@news.grc.com>, shr@p.com says...
> 
> 
> Obviously a local IP, but what are its functions/purpose?
> 
> Thanks for educating the uneducated.

To elaborate on P.E.s response, if you have multiple adapters, 0.0.0.0 
means any one of them. If I dial out to Compuserve, I wind up with three 
adapters; 172.29.61.1, 192.168.123.103, and 216.192.x.x. I am not trying to 
mask that CompuServe address, it is dynamically assigned, and will vary 
from call to call. I haven't really explored the tricks to mapping these 
addresses in a routing table, though. But the 0.0.0.0 would simply mean the 
process will bind to whichever adapter is appropriate to move the packets 
from point to point; as compared with identifying a specific adapter 
address.

-- 
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

> To elaborate on P.E.s response, if you have multiple adapters, 0.0.0.0
> means any one of them. If I dial out to Compuserve, I wind up with three
> adapters; 172.29.61.1, 192.168.123.103, and 216.192.x.x. I am not trying
to
> mask that CompuServe address, it is dynamically assigned, and will vary
> from call to call. I haven't really explored the tricks to mapping these
> addresses in a routing table, though. But the 0.0.0.0 would simply mean
the
> process will bind to whichever adapter is appropriate to move the packets
> from point to point; as compared with identifying a specific adapter
> address.

Well, from a routing point of view a route of 0.0.0.0 with a mask of 0.0.0.0
and a *defined* gateway address means ... route all the packets which
don't have a specific matching route in the routing table to this gateway

In article <b34o5u$2e4b$1@news.grc.com>, anzenNO-SPAM@gmx.net says...
> > To elaborate on P.E.s response, if you have multiple adapters, 0.0.0.0
> > means any one of them. If I dial out to Compuserve, I wind up with three
> > adapters; 172.29.61.1, 192.168.123.103, and 216.192.x.x. I am not trying
> to
> > mask that CompuServe address, it is dynamically assigned, and will vary
> > from call to call. I haven't really explored the tricks to mapping these
> > addresses in a routing table, though. But the 0.0.0.0 would simply mean
> the
> > process will bind to whichever adapter is appropriate to move the packets
> > from point to point; as compared with identifying a specific adapter
> > address.
> 
> Well, from a routing point of view a route of 0.0.0.0 with a mask of 0.0.0.0
> and a *defined* gateway address means ... route all the packets which
> don't have a specific matching route in the routing table to this gateway
> 
> 
> 
> 


Thanks for clearing that up folks. Appreciate the help.

 0.0.0.0 refers to a localhost address ie your computer. You can make use of
this by opening up your hosts file in the windows folder using =
WORDPAD to open it with and putting in for example the following entry.
0.0.0.0   yahoo.com
This will cause your computer (which accesses the Hosts file first  before
calling on a DNS server) to call only to your computer to access  yahoo.com
and your computer will never access that site. I use this  method for
filtering out known tracking sites. You can download a Hosts  file which is
already configured at the following site.
  http://accs-net.com/hosts/

In article <b45e03$1g1v$1@news.grc.com>, tesseract1@earthlink.net 
says...
>  0.0.0.0 refers to a localhost address ie your computer. 

No, it doesn't.

127.0.0.1 refers to the loopback interface ie your computer.

0.0.0.0 refers to *any* listening interface.

<>

-- 
Bloated Elvis

"Tesseract" <tesseract1@earthlink.net> wrote in message
news:b45e03$1g1v$1@news.grc.com...
> 0.0.0.0 refers to a localhost address ie your computer. You can
make use of

0.0.0.0 is a wildcard. It means that the source of traffic will
be identified by the netmask. Typically, 255.255.255.255 for
outside and 255.255.255.0 for inside the LAN.

Localhost is usually 127.0.0.x

It seems their site uses ad.doubleclick.net as a third party site for the
storage of information or at least information filters through that site
before reaching my computer from my webmail account. Specifically the click
down box that is labeled 'Move To Folder' where I determine where to send
mail to from my INBOX. This is an example of what's probably happening on
your computer. With that site filtered out through Hosts I cannot see the
names of the folders in the list, although there are 16 blanks there where
the names are supposed to be. To me this is indication that they may well be
at least redirecting the names of these folders through their site... and
possibly everything I send to those same folders. However, with
ad.doubleclick.net filtered out I canot send mail to these same folders.
Hmmmmm.

In article <b4838o$14fe$1@news.grc.com>, rj@nowhere.com says...
> "Tesseract" <tesseract1@earthlink.net> wrote in message
> news:b45e03$1g1v$1@news.grc.com...
> > 0.0.0.0 refers to a localhost address ie your computer. You can
> make use of
> 
> 0.0.0.0 is a wildcard. It means that the source of traffic will
> be identified by the netmask. Typically, 255.255.255.255 for
> outside and 255.255.255.0 for inside the LAN.
> 
> Localhost is usually 127.0.0.x
> 
Where do you people come up with this stuff ?

Please, I'd love to know where you found/acquired/read that 0.0.0.0 is a 
wildcard for traffic identified by the netmask.

-- 
Bloated Elvis

In article <b4838o$14fe$1@news.grc.com>, rj@nowhere.com says...
> "Tesseract" <tesseract1@earthlink.net> wrote in message
> news:b45e03$1g1v$1@news.grc.com...
> > 0.0.0.0 refers to a localhost address ie your computer. You can
> make use of
> 
> 0.0.0.0 is a wildcard. It means that the source of traffic will
> be identified by the netmask. Typically, 255.255.255.255 for
> outside and 255.255.255.0 for inside the LAN.
> 
> Localhost is usually 127.0.0.x

bloated elvis has the right answer; and his explanation was clearer than 
mine; though I think I understand it. Netmask has nothing to do with 
0.0.0.0, that I can see. It simply means, as b.e. stated, "any listening 
adapter". Some of us even have multiple adapters defined.

-- 
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

The point is that as far as Hosts is concerned an entry using 0.0.0.0 works
as effectively as one that uses 127.0.0.1 as far as filtering is concerned,
and in some instances faster. It filters out a website if you put in an
entry '0.0.0.0   ad.doubleclick.net' for example. Try it and you'll see that
your computer simply will not access that site or any site that you use
after that entry. The Hosts file simply doesn't care what your technical
explanation is. IT SIMPLY WORKS.

On Mon, 10 Mar 2003 12:59:03 -0500, Tesseract wrote:

> The point is that as far as Hosts is concerned

"The point is" that as far as the original question is concerned, your
description of 0.0.0.0 in the hosts file had nothing to do with the
original question.  The point also is that when you attempted to answer
the question ("0.0.0.0 refers to a localhost address ie your computer")
you were flat-out wrong.

*snip*
> The Hosts file simply doesn't care what your technical explanation is.

I think it'd be safe to assume that the original poster did, thus the
question "what are its functions/purpose?"

> IT SIMPLY WORKS.

Yippee.  Too bad you're providing the answer to the question no one asked.

-- 
Powered by Pan - Now with cream-filled score file goodness!

This post has been scanned by AVG, so any vir--er, I mean, attachments--
are deemed safe!  So feel free to run them willy-nilly!

In article <b4838o$14fe$1@news.grc.com>, rj@nowhere.com says...
> "Tesseract" <tesseract1@earthlink.net> wrote in message
> news:b45e03$1g1v$1@news.grc.com...
> > 0.0.0.0 refers to a localhost address ie your computer. You can
> make use of
>
> 0.0.0.0 is a wildcard. It means that the source of traffic will
> be identified by the netmask. Typically, 255.255.255.255 for
> outside and 255.255.255.0 for inside the LAN.
>
> Localhost is usually 127.0.0.x
>
Where do you people come up with this stuff ?

Please, I'd love to know where you found/acquired/read that 0.0.0.0 is a
wildcard for traffic identified by the netmask.

The posting I put in to that effect was a technical mistake which I
acknowledge but the following post sidetracked the issue that as far as
Hosts is concerned it works and Hosts doesn't make the distinction as far as
filtering is concerned. You could as well put in the IP address for Yahoo
followed by ad.doubleclick.net and would still not access ad.doubleclick.net
because your Hosts file gives an IP address that isn't ad.doubleclick.net
and that's the first place your computer queries before sending a query to a
DNS server. If an entry for that site is found in Hosts the computer simply
will not look further.

On Mon, 10 Mar 2003 15:06:13 -0500, Tesseract wrote:

*snip*
> If an entry for that site is found in Hosts the computer simply will not
> look further.

Yes, that is correct.

-- 
Powered by Pan - Now with cream-filled score file goodness!

This post has been scanned by AVG, so any vir--er, I mean, attachments--
are deemed safe!  So feel free to run them willy-nilly!

Personally...
(after reading ALL the meaningless responses in this silly thread...)
You ALL need to spend some time reading documents at:
http://www.iana.org/   (Internet Authority for Assigned Names and Numbers)

Specifically:
http://www.rfc-editor.org/rfc/rfc3330.txt

RFC3330 - Informational RFC on Special-Use IPv4 Addresses

   0.0.0.0/8 - Addresses in this block refer to source hosts on "this"
   network.  Address 0.0.0.0/32 may be used as a source address for this
   host on this network; other addresses within 0.0.0.0/8 may be used to
   refer to specified hosts on this network [RFC1700, page 4].

   127.0.0.0/8 - This block is assigned for use as the Internet host
   loopback address.  A datagram sent by a higher level protocol to an
   address anywhere within this block should loop back inside the host.
   This is ordinarily implemented using only 127.0.0.1/32 for loopback,
   but no addresses within this block should ever appear on any network
   anywhere [RFC1700, page 5].

All the "Reserved Special IPs" are listed, including 255.255.255.255
(Broadcast)

Have Fun,
Spend SOME time actually learning... maybe you guys will do LESS
bickering!!!

PCNetGuy





"shrap" <shr@p.com> wrote in message
news:MPG.18bf7ade16e851cb989680@news.grc.com...
>
>
> Obviously a local IP, but what are its functions/purpose?
>
> Thanks for educating the uneducated.
>
>

"BlueJAMC" <idontwantemail@127.0.0.1> wrote in message
news:pan.2003.03.10.20.21.19.179312@invalid.domain.to.use.as.a.filter.org...


> > If an entry for that site is found in Hosts the computer simply will not
> > look further.
>
> Yes, that is correct.

provided the lookup table and ttl's are set to default...
the order is often changed for lan use...by admins
(order is in registry sorted by a priority field (number))

for 0.0...  I would hesitate to use that in hosts files..
it does_not always work that way, and 127 may not either.
(remember...enterprise lan admins are in here too...so
 what works or doesn't on stand-alones...can be a bane)

'Seek and ye shall find'
NT Canuck

> for 0.0...  I would hesitate to use that in hosts files..
> it does_not always work that way, and 127 may not either.
> (remember...enterprise lan admins are in here too...so
>  what works or doesn't on stand-alones...can be a bane)

Well, the problem with 127.. is that .. if you're blocking
web servers and if the local machine *has* a running
webserver (e.g. IIS) all the "blocked" requests will go
straight to the local IIS and this is not so good; worst
if you have a local proxy running on port 80 using the
127.0.0.1 may even cause deadlocks; so I often use
addresses like 127.0.0.254 or the like :-)