hmmm, could this be right..?
D:\>ping 11010001001111011011101011110001
Pinging 160.86.104.113 with 32 bytes of data:
Reply from 209.44.32.146: Destination net unreachable.
Reply from 209.44.32.146: Destination net unreachable.
Request timed out.
Request timed out.
Ping statistics for 160.86.104.113:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Why would I get a reply from 209.44.32.146 when the example below states
that 11010001001111011011101011110001 = 209.61.186.121?
How do you find the binary for 3510483697? I know how to find the binary
from 209.61.186.121 - do you need a special tool to find the binary from
3510483697? or do you simply extend the 124-64-32-16 etc table up..?
And another thought, is it possible to filter on this level (3510483697)?
A very interesting thread!
Eve
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Smith, Steve
Sent: 23. april 2001 19:38
To: [EMAIL PROTECTED]
Subject: RE: [OT] Who can explain this address scheme?
Covert the large number to binary:
3510483697 --> 11010001001111011011101011110001
Break the binary up in 8 bit boundaries:
11010001 00111101 10111010 11110001
Convert each octet back into decimal:
11010001 --> 209
00111101 --> 61
10111010 --> 186
11110001 --> 121
Reassemble the individual octets into familar quad-dot addresses:
11010001001111011011101011110001 --> 209.61.186.121
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
