On 01/03/11 21:02, John R Pierce wrote:
On 03/01/11 11:51 AM, Always Learning wrote:
4 hex digits vs. 1-3 decimal digits provides adequate disambiguation.
1:2:3:4 or 1.2.3.4 ? Each segment of the former is a valid 'decimal'
number and also a valid 'hexadecimal' number. Each segment of the
centos-boun...@centos.org wrote:
On Sat, 2011-02-26 at 12:24 -0800, John R Pierce wrote:
http://21DA:00D3::00FF:FE28:8080
is that...
http://[21DA:00D3::::00FF:FE28:8080]
or
http://[21DA:00D3:::::00FF:FE28]:8080
What separator would you
On Tue, 2011-03-01 at 14:20 -0500, Brunner, Brian T. wrote:
centos-boun...@centos.org wrote:
On Sat, 2011-02-26 at 12:24 -0800, John R Pierce wrote:
http://21DA:00D3::00FF:FE28:8080
is that...
http://[21DA:00D3::::00FF:FE28:8080]
or
On 03/01/11 11:51 AM, Always Learning wrote:
4 hex digits vs. 1-3 decimal digits provides adequate disambiguation.
1:2:3:4 or 1.2.3.4 ? Each segment of the former is a valid 'decimal'
number and also a valid 'hexadecimal' number. Each segment of the later
is a valid decimal number.
except
On 28/02/2011, at 10:30 AM, Les Mikesell wrote:
On 2/27/11 12:50 PM, John R Pierce wrote:
On 02/27/11 9:16 AM, Les Mikesell wrote:
Is there any difference in efficiency in how well the NIC hardware filters
the
assigned addresses?
Yes, as mentioned below, the NIC is given a list of
On 27/02/11 06:46, Always Learning wrote:
Octets
Thanks for pointing-out my misunderstanding.
I'll remember 2 octets are really 2 characters (IBM's bytes) = 2 digits,
4 octal numbers or 4 hexadecimal numbers.
This is a confusing summary.
3 bits = 1 octal number (values 0-7)
4 bits = 1
On Sun, 2011-02-27 at 00:38 -0600, Larry Vaden wrote:
On Sat, Feb 26, 2011 at 2:12 PM, Always Learning cen...@g7.u22.net wrote:
Today I received an allocation of IP6 addresses for some servers. I can
'play' with the last 2 of the 8 IP6 address segments.
I guess Will Rogers was correct
On Sun, Feb 27, 2011 at 3:44 PM, Always Learning cen...@g7.u22.net wrote:
I was actually wrong. I can 'play' with not 2 but 4 groups of the IP6
allocation. Golly, what can I do with 64 x 64 x 64 x 64 address
combinations? Hire then out? Have a different IP6 address for every
hour of the
On Sun, Feb 27, 2011 at 01:44:17PM +, Always Learning wrote:
I was actually wrong. I can 'play' with not 2 but 4 groups of the IP6
allocation. Golly, what can I do with 64 x 64 x 64 x 64 address
That's an odd combination. 64 is 6 bits, which has nothing to do
with an IPv6 group.
Many
On 27/02/11 14:44, Always Learning wrote:
I was actually wrong. I can 'play' with not 2 but 4 groups of the IP6
allocation. Golly, what can I do with 64 x 64 x 64 x 64 address
combinations? Hire then out? Have a different IP6 address for every
hour of the year?
If you got allocated a /48
On 2/27/11 8:00 AM, Rudi Ahlers wrote:
On Sun, Feb 27, 2011 at 3:44 PM, Always Learningcen...@g7.u22.net wrote:
I was actually wrong. I can 'play' with not 2 but 4 groups of the IP6
allocation. Golly, what can I do with 64 x 64 x 64 x 64 address
combinations? Hire then out? Have a
On 2/27/11 9:38 AM, David Sommerseth wrote:
Yes, IPv6 gives every site a lot of more possibilities. And in IPv6 each NIC
can have multiple IPv6 addresses, without using aliasing which is needed for
IPv4. If you want to allocate 30 IPv6 addresses to one adapter, you may do so
very easily.
On 02/27/11 9:16 AM, Les Mikesell wrote:
Is there any difference in efficiency in how well the NIC hardware filters the
assigned addresses?
NIC's work in MAC addresses, not IP.
___
CentOS mailing list
CentOS@centos.org
On 2/27/11 12:50 PM, John R Pierce wrote:
On 02/27/11 9:16 AM, Les Mikesell wrote:
Is there any difference in efficiency in how well the NIC hardware filters
the
assigned addresses?
NIC's work in MAC addresses, not IP.
Sort-of. Most NICs know enough about IPv4 multicast to at least help
Today I received an allocation of IP6 addresses for some servers. I can
'play' with the last 2 of the 8 IP6 address segments.
I always thought, mistakenly, IP6 was 6 segments, because it was IP6.
IP4 had 4 segments. However IP6 is actually IP version 6 and it has 8
segments. The other
On 02/26/11 12:12 PM, Always Learning wrote:
Because : is sometimes used in an address to indicate the start of a
port number, examplehttp://www.anyonejunk.com:1234, the IP6 address can
be enclosed within [ ] with the port number remaining outside the square
brackets.
Thats, MUST be enclosed
Am 26.02.2011 um 21:24 schrieb John R Pierce:
On 02/26/11 12:12 PM, Always Learning wrote:
Because : is sometimes used in an address to indicate the start of a
port number, examplehttp://www.anyonejunk.com:1234, the IP6 address
can
be enclosed within [ ] with the port number remaining
On Sat, 2011-02-26 at 12:24 -0800, John R Pierce wrote:
On 02/26/11 12:12 PM, Always Learning wrote:
Because : is sometimes used in an address to indicate the start of a
port number, example http://www.anyonejunk.com:1234, the IP6 address can
be enclosed within [ ] with the port number
On Sat, 2011-02-26 at 21:33 +0100, Rainer Duffner wrote:
With IPV6, you don't need to run it on a different port.
Just bind it to a different IP in the same prefix ;-)
So, that port-8080 stuff will be gone pretty soon.
Very interesting point.
In a year or two.
Cough-cough.
That long?
On 02/26/11 12:33 PM, Rainer Duffner wrote:
With IPV6, you don't need to run it on a different port.
Just bind it to a different IP in the same prefix ;-)
So, that port-8080 stuff will be gone pretty soon.
In a year or two.
Cough-cough.
when I first saw the spec for IPv6 I mistakenly thought
Always learning wrote:
I always thought, mistakenly, IP6 was 6 segments, because it was IP6. IP4
had 4 segments. However IP6 is actually IP version 6 and it has 8 segments.
I don't think I ever heard IP6, but always IPv6. Counting segments might not be
as meaningful. IPv6 has twice (8)
On Sat, 2011-02-26 at 12:41 -0800, John R Pierce wrote:
On 02/26/11 12:33 PM, Rainer Duffner wrote:
With IPV6, you don't need to run it on a different port.
Just bind it to a different IP in the same prefix ;-)
So, that port-8080 stuff will be gone pretty soon.
In a year or two.
On Sat, 2011-02-26 at 20:58 +, sheraz...@yahoo.com wrote:
IPv6 has twice (8) segments compared to IPv4 however each segment
is 2 octets making IPv6 address space 4 times (128 bits) compared
to IPv4 (32 bits).
Oct... means 8.
Each segment of an IP6 segment can contain 4 hexadecimal
2 hex digits is 1 octet (or byte).
On Feb 26, 2011, at 3:04 PM, Always Learning wrote:
On Sat, 2011-02-26 at 20:58 +, sheraz...@yahoo.com wrote:
IPv6 has twice (8) segments compared to IPv4 however each segment
is 2 octets making IPv6 address space 4 times (128 bits) compared
to IPv4
Creating lots of dummy IP6 addresses to confuse hackers is not an ideal
solution.
scanning ports on an IP vs scanning IPs. whatever.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
IPv6 has twice (8) segments compared to IPv4 however each segment
is 2 octets making IPv6 address space 4 times (128 bits) compared
to IPv4 (32 bits).
Oct... means 8.
Each segment of an IP6 segment can contain 4 hexadecimal digits.
Hexadecimal means 0 to F.
Are you sure 'octets' is
Octets
Thanks for pointing-out my misunderstanding.
I'll remember 2 octets are really 2 characters (IBM's bytes) = 2 digits,
4 octal numbers or 4 hexadecimal numbers.
--
With best regards,
Paul.
England,
EU.
___
CentOS mailing list
On 02/26/11 9:46 PM, Always Learning wrote:
Octets
Thanks for pointing-out my misunderstanding.
I'll remember 2 octets are really 2 characters (IBM's bytes) = 2 digits,
4 octal numbers or 4 hexadecimal numbers.
4 octal (base 8) digits only represents 12 bits. byte oriented
computers
28 matches
Mail list logo
