Does Ubuntu 14.04 support advertisement of more specific routes?
I have an IPv6-only network where I am now trying to add a NAT64 gateway. The NAT64 is not on my default gateway because it's intended to use a different ISP than the default gateway.
The default gateway is advertised using radvd
and IPv6 connection is working. However the NAT64 provided by the ISP is unreliable and thus I want to configure my own NAT64.
On the machine where my NAT64 is running I have created this radvd
configuration:
interface enp4s0
{
AdvSendAdvert on;
AdvDefaultPreference low;
route 64:ff9b::/96 {
AdvRoutePreference high;
};
};
But it is not working. On the client machines I only see the default
route and not the 64:ff9b::/96
route to the NAT64 gateway.
14.04 networking routing ipv6 radvd
add a comment |
I have an IPv6-only network where I am now trying to add a NAT64 gateway. The NAT64 is not on my default gateway because it's intended to use a different ISP than the default gateway.
The default gateway is advertised using radvd
and IPv6 connection is working. However the NAT64 provided by the ISP is unreliable and thus I want to configure my own NAT64.
On the machine where my NAT64 is running I have created this radvd
configuration:
interface enp4s0
{
AdvSendAdvert on;
AdvDefaultPreference low;
route 64:ff9b::/96 {
AdvRoutePreference high;
};
};
But it is not working. On the client machines I only see the default
route and not the 64:ff9b::/96
route to the NAT64 gateway.
14.04 networking routing ipv6 radvd
add a comment |
I have an IPv6-only network where I am now trying to add a NAT64 gateway. The NAT64 is not on my default gateway because it's intended to use a different ISP than the default gateway.
The default gateway is advertised using radvd
and IPv6 connection is working. However the NAT64 provided by the ISP is unreliable and thus I want to configure my own NAT64.
On the machine where my NAT64 is running I have created this radvd
configuration:
interface enp4s0
{
AdvSendAdvert on;
AdvDefaultPreference low;
route 64:ff9b::/96 {
AdvRoutePreference high;
};
};
But it is not working. On the client machines I only see the default
route and not the 64:ff9b::/96
route to the NAT64 gateway.
14.04 networking routing ipv6 radvd
I have an IPv6-only network where I am now trying to add a NAT64 gateway. The NAT64 is not on my default gateway because it's intended to use a different ISP than the default gateway.
The default gateway is advertised using radvd
and IPv6 connection is working. However the NAT64 provided by the ISP is unreliable and thus I want to configure my own NAT64.
On the machine where my NAT64 is running I have created this radvd
configuration:
interface enp4s0
{
AdvSendAdvert on;
AdvDefaultPreference low;
route 64:ff9b::/96 {
AdvRoutePreference high;
};
};
But it is not working. On the client machines I only see the default
route and not the 64:ff9b::/96
route to the NAT64 gateway.
14.04 networking routing ipv6 radvd
14.04 networking routing ipv6 radvd
edited Dec 16 at 23:22
asked Dec 15 at 19:06
kasperd
9541732
9541732
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That radvd
configuration does work, but Ubuntu 14.04 act as what RFC 4191 call a type B host.
The types defined in RFC 4191 are as follows:
- Type A - no support for preferences or more specific routes
- Type B - support for preferences but not more specific routes
- Type C - support for both preferences and more specific routes
The radvd
version on Ubuntu 14.04 can be configured to send both preferences and more specific routes. But when Ubuntu 14.04 receives such routes it will ignore the more specific routes and only pay attention to the preference.
One way to solve this is to upgrade the hosts to Ubuntu 16.04 (or later) which will act as type C host with full support for advertisements of more specific routes.
For backward compatibility with type A and type B hosts RFC 4191 recommends the use of redirect messages. If all IPv6 routers on your network have the full routing table they can send redirect messages when a host on the network use the wrong gateway for a packet.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2faskubuntu.com%2fquestions%2f1102154%2fdoes-ubuntu-14-04-support-advertisement-of-more-specific-routes%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That radvd
configuration does work, but Ubuntu 14.04 act as what RFC 4191 call a type B host.
The types defined in RFC 4191 are as follows:
- Type A - no support for preferences or more specific routes
- Type B - support for preferences but not more specific routes
- Type C - support for both preferences and more specific routes
The radvd
version on Ubuntu 14.04 can be configured to send both preferences and more specific routes. But when Ubuntu 14.04 receives such routes it will ignore the more specific routes and only pay attention to the preference.
One way to solve this is to upgrade the hosts to Ubuntu 16.04 (or later) which will act as type C host with full support for advertisements of more specific routes.
For backward compatibility with type A and type B hosts RFC 4191 recommends the use of redirect messages. If all IPv6 routers on your network have the full routing table they can send redirect messages when a host on the network use the wrong gateway for a packet.
add a comment |
That radvd
configuration does work, but Ubuntu 14.04 act as what RFC 4191 call a type B host.
The types defined in RFC 4191 are as follows:
- Type A - no support for preferences or more specific routes
- Type B - support for preferences but not more specific routes
- Type C - support for both preferences and more specific routes
The radvd
version on Ubuntu 14.04 can be configured to send both preferences and more specific routes. But when Ubuntu 14.04 receives such routes it will ignore the more specific routes and only pay attention to the preference.
One way to solve this is to upgrade the hosts to Ubuntu 16.04 (or later) which will act as type C host with full support for advertisements of more specific routes.
For backward compatibility with type A and type B hosts RFC 4191 recommends the use of redirect messages. If all IPv6 routers on your network have the full routing table they can send redirect messages when a host on the network use the wrong gateway for a packet.
add a comment |
That radvd
configuration does work, but Ubuntu 14.04 act as what RFC 4191 call a type B host.
The types defined in RFC 4191 are as follows:
- Type A - no support for preferences or more specific routes
- Type B - support for preferences but not more specific routes
- Type C - support for both preferences and more specific routes
The radvd
version on Ubuntu 14.04 can be configured to send both preferences and more specific routes. But when Ubuntu 14.04 receives such routes it will ignore the more specific routes and only pay attention to the preference.
One way to solve this is to upgrade the hosts to Ubuntu 16.04 (or later) which will act as type C host with full support for advertisements of more specific routes.
For backward compatibility with type A and type B hosts RFC 4191 recommends the use of redirect messages. If all IPv6 routers on your network have the full routing table they can send redirect messages when a host on the network use the wrong gateway for a packet.
That radvd
configuration does work, but Ubuntu 14.04 act as what RFC 4191 call a type B host.
The types defined in RFC 4191 are as follows:
- Type A - no support for preferences or more specific routes
- Type B - support for preferences but not more specific routes
- Type C - support for both preferences and more specific routes
The radvd
version on Ubuntu 14.04 can be configured to send both preferences and more specific routes. But when Ubuntu 14.04 receives such routes it will ignore the more specific routes and only pay attention to the preference.
One way to solve this is to upgrade the hosts to Ubuntu 16.04 (or later) which will act as type C host with full support for advertisements of more specific routes.
For backward compatibility with type A and type B hosts RFC 4191 recommends the use of redirect messages. If all IPv6 routers on your network have the full routing table they can send redirect messages when a host on the network use the wrong gateway for a packet.
answered Dec 15 at 19:06
kasperd
9541732
9541732
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2faskubuntu.com%2fquestions%2f1102154%2fdoes-ubuntu-14-04-support-advertisement-of-more-specific-routes%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