Linux assigns an fe80::/64 address to an interface. Shouldn't that be fe80::/10?
up vote
8
down vote
favorite
Per the IPv6 standard, Linux assigns IPv6 link local addresses to interfaces. These interfaces are always assigned /64 addresses. Is this correct? I would think they should be /10. Why are they assigned /64 addresses?
linux networking network-interface ipv6
asked Jan 30 at 22:03
Omnifarious
895616
add a comment |
up vote
8
down vote
favorite
Per the IPv6 standard, Linux assigns IPv6 link local addresses to interfaces. These interfaces are always assigned /64 addresses. Is this correct? I would think they should be /10. Why are they assigned /64 addresses?
linux networking network-interface ipv6
asked Jan 30 at 22:03
Omnifarious
895616
1
This related question may be of interest as well: networkengineering.stackexchange.com/q/130/5842
– kasperd
Feb 10 at 14:35
@kasperd - Indeed it is, thank you.
– Omnifarious
Feb 13 at 1:11
add a comment |
up vote
8
down vote
favorite
up vote
8
down vote
favorite
Per the IPv6 standard, Linux assigns IPv6 link local addresses to interfaces. These interfaces are always assigned /64 addresses. Is this correct? I would think they should be /10. Why are they assigned /64 addresses?
linux networking network-interface ipv6
asked Jan 30 at 22:03
Omnifarious
895616
Per the IPv6 standard, Linux assigns IPv6 link local addresses to interfaces. These interfaces are always assigned /64 addresses. Is this correct? I would think they should be /10. Why are they assigned /64 addresses?
linux networking network-interface ipv6
linux networking network-interface ipv6
asked Jan 30 at 22:03
Omnifarious
895616
asked Jan 30 at 22:03
Omnifarious
895616
edited Jan 30 at 22:42
asked Jan 30 at 22:03
Omnifarious
895616
asked Jan 30 at 22:03
Omnifarious
895616
asked Jan 30 at 22:03
Omnifarious
895616
895616
1
This related question may be of interest as well: networkengineering.stackexchange.com/q/130/5842
– kasperd
Feb 10 at 14:35
@kasperd - Indeed it is, thank you.
– Omnifarious
Feb 13 at 1:11
add a comment |
1
This related question may be of interest as well: networkengineering.stackexchange.com/q/130/5842
– kasperd
Feb 10 at 14:35
@kasperd - Indeed it is, thank you.
– Omnifarious
Feb 13 at 1:11
1
1
This related question may be of interest as well: networkengineering.stackexchange.com/q/130/5842
– kasperd
Feb 10 at 14:35
This related question may be of interest as well: networkengineering.stackexchange.com/q/130/5842
– kasperd
Feb 10 at 14:35
@kasperd - Indeed it is, thank you.
– Omnifarious
Feb 13 at 1:11
@kasperd - Indeed it is, thank you.
– Omnifarious
Feb 13 at 1:11
add a comment |
2 Answers
2
active
oldest
votes
up vote
11
down vote
accepted
The address space allocated to link-local addresses is fe80::/10, but the next 54 bits are defined to be all zeroes, so the effective range is fe80::/64. Which puts it in line with the usual custom for IPv6 addresses.
RFC 4291:
2.5.6. Link-Local IPv6 Unicast Addresses
Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
answered Jan 30 at 22:23
ilkkachu
54k782147
add a comment |
up vote
0
down vote
FE80::/64 includes 2^48 Ethernet addresses and some other link-level derived combinations, but not necessarily all types. The /10 allows for future expansion of new types not yet defined.
answered Nov 23 at 14:59
MR.X
1
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
11
down vote
accepted
The address space allocated to link-local addresses is fe80::/10, but the next 54 bits are defined to be all zeroes, so the effective range is fe80::/64. Which puts it in line with the usual custom for IPv6 addresses.
RFC 4291:
2.5.6. Link-Local IPv6 Unicast Addresses
Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
answered Jan 30 at 22:23
ilkkachu
54k782147
add a comment |
up vote
11
down vote
accepted
The address space allocated to link-local addresses is fe80::/10, but the next 54 bits are defined to be all zeroes, so the effective range is fe80::/64. Which puts it in line with the usual custom for IPv6 addresses.
RFC 4291:
2.5.6. Link-Local IPv6 Unicast Addresses
Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
answered Jan 30 at 22:23
ilkkachu
54k782147
add a comment |
up vote
11
down vote
accepted
up vote
11
down vote
accepted
The address space allocated to link-local addresses is fe80::/10, but the next 54 bits are defined to be all zeroes, so the effective range is fe80::/64. Which puts it in line with the usual custom for IPv6 addresses.
RFC 4291:
2.5.6. Link-Local IPv6 Unicast Addresses
Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
answered Jan 30 at 22:23
ilkkachu
54k782147
The address space allocated to link-local addresses is fe80::/10, but the next 54 bits are defined to be all zeroes, so the effective range is fe80::/64. Which puts it in line with the usual custom for IPv6 addresses.
RFC 4291:
2.5.6. Link-Local IPv6 Unicast Addresses
Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
| 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
answered Jan 30 at 22:23
ilkkachu
54k782147
answered Jan 30 at 22:23
ilkkachu
54k782147
answered Jan 30 at 22:23
ilkkachu
54k782147
answered Jan 30 at 22:23
ilkkachu
54k782147
54k782147
add a comment |
add a comment |
up vote
0
down vote
FE80::/64 includes 2^48 Ethernet addresses and some other link-level derived combinations, but not necessarily all types. The /10 allows for future expansion of new types not yet defined.
answered Nov 23 at 14:59
MR.X
1
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
FE80::/64 includes 2^48 Ethernet addresses and some other link-level derived combinations, but not necessarily all types. The /10 allows for future expansion of new types not yet defined.
answered Nov 23 at 14:59
MR.X
1
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
FE80::/64 includes 2^48 Ethernet addresses and some other link-level derived combinations, but not necessarily all types. The /10 allows for future expansion of new types not yet defined.
answered Nov 23 at 14:59
MR.X
1
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
FE80::/64 includes 2^48 Ethernet addresses and some other link-level derived combinations, but not necessarily all types. The /10 allows for future expansion of new types not yet defined.
answered Nov 23 at 14:59
MR.X
1
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 14:59
MR.X
1
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 23 at 14:59
MR.X
1
answered Nov 23 at 14:59
MR.X
1
1
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
MR.X is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f420814%2flinux-assigns-an-fe80-64-address-to-an-interface-shouldnt-that-be-fe80-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This related question may be of interest as well: networkengineering.stackexchange.com/q/130/5842
– kasperd
Feb 10 at 14:35
@kasperd - Indeed it is, thank you.
– Omnifarious
Feb 13 at 1:11