Two stupid ip questions;

[bob.cat@juno.com]

The IP addresses of the cluster are irrelevant so long as the head system
does not route packets.  If you do need to route packets, you will need
to use network address translation anyway.

The 192.168.x.x and other reserved addresses are there to protect against
someone putting a previously private network onto the Internet.  Since
the net is not supposed to route reserved addresses (SUPPOSED not to),
when you plug your 192.168.x.x network in, it just doesn't work for you,
rather than possibly screwing up the network whose addresses you used.

> http://3626046468/ maps to www.angelfire.com (216.33.20.4)
>Any ideas why people decided on a decimal IP address notation 
>http://3626046468/
>http://d8211404/
>instead of a much more natural hexadecimal one?

There IS no *natural* way to express a number.

That notation doesn't work everywhere: WIN98 IE5.0 needs:

http://0xd8211404/    or

http://0xd8.0x21.0x14.0x04/

And it does like octal (leading 0 indicating octal):

http://033010212004   etc., etc...

There are many ways to express an IP address, and this is not OS
dependent.

>And won't it be just horrible typing monstrosities like
>http://1.2.4.8.16.32.64.128.1.2.4.8.16.32.64.128/
>in IPv6? Hexadecimal notation would seem definitely more compact 
>here...
>http://d8211404d8211404d8211404d8211404/
>
>Still, quite difficult to memorize, unless you're an idiot savant,
>that is.

Simply convert the address to base(2^128) and you'll just have one number
to remember!


:ßobÇat.Bat 1.0 >^^<   Stop me before I hack again!
Echo f b800:0000 fff 32 00 e1 09 6f 0f 62 0f 80 04 61 0f 74 0f 32 00 >
Bob.Cat
Echo q >> Bob.Cat
DeBug < Bob.Cat > Nul
@Erase Bob.Cat > Nul