Why has IPv6 mngtmpaddr stopped responding?Diskless Boot with IPv6Get dynamic and static IPv6 addressFirewall problem using autofs with NFS-exported mountsIPv6 not working for Ubuntu in AWS EC2 instances
How to delete a game file?
Were there ever 12-, 24-, 48-, etc bit processors?
Can Veil of Summer force an opponent to target their own creatures with Swift End when Lucky Clover is on the battlefield?
How do I evolve Leafeon or Glaceon?
If a photon truly goes through both slits (at the same time), then why can't we detect it at both slits (at the same time)?
Python's .split() implemented in C
Is it acceptable the secretariat to have full access to our entire Outlook agenda?
What is the correct way for pilots to say the time?
Stack data structure in python 3
Is there way to randomly distribute points within a circle on the surface of a sphere?
Are conjugate vectors unique?
What should I do about spammy backlinks from suspect websites reported in Search Engine Console?
Car no longer starts, behaved weird before giving up
How can I convince my child to write?
Why does Darth Sidious fear Luke Skywalker?
How big could a meteor crater be without causing significant secondary effects?
What does Yoda's species eat?
Why would one use "enter the name of the project to confirm"?
Can I use the Cleric spell Light and a magnifying glass to light a fire?
Why countdef, dimendef, and alike require custom-named register to be empty before assignment?
Is "montäglich" commonly used?
Beautiful planar geometry theorems not encountered in high school
GLPK: meaning of the "marginal' column in the solution output
Make me speak L33T
Why has IPv6 mngtmpaddr stopped responding?
Diskless Boot with IPv6Get dynamic and static IPv6 addressFirewall problem using autofs with NFS-exported mountsIPv6 not working for Ubuntu in AWS EC2 instances
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
19.04
I have been using IPv6 on my LAN for a few weeks now. Ping, SSH, NFS -- all fine. Three 19.04 machines, all good.
Yesterday, after an update, the IPv6 stopped working. Processing a request to an IPv6 address on the LAN the system hangs. I say 'after an update' because I did do an update and some hours later I noticed the problem; so I'm not saying the update caused it, just noting the coincidence.
I had been using the mngtmpaddr
address as reported by the ip a command. On a try I switched to using the other IPv6 address (the /128 address) and now that one works.
This is not only a curiousity. There's an issue for me because I have been using my NFS server's IPv6 address to mount its shares when I'm away from the LAN. Previously I had to change my /etc/fstab
whenever I was away from home. So :
So what is going on?
- What is the difference between these two addresses?
- Why would the
mngtmpaddr
stop working? - Will this change still work from outside the LAN?
ssh nfs ipv6
add a comment
|
19.04
I have been using IPv6 on my LAN for a few weeks now. Ping, SSH, NFS -- all fine. Three 19.04 machines, all good.
Yesterday, after an update, the IPv6 stopped working. Processing a request to an IPv6 address on the LAN the system hangs. I say 'after an update' because I did do an update and some hours later I noticed the problem; so I'm not saying the update caused it, just noting the coincidence.
I had been using the mngtmpaddr
address as reported by the ip a command. On a try I switched to using the other IPv6 address (the /128 address) and now that one works.
This is not only a curiousity. There's an issue for me because I have been using my NFS server's IPv6 address to mount its shares when I'm away from the LAN. Previously I had to change my /etc/fstab
whenever I was away from home. So :
So what is going on?
- What is the difference between these two addresses?
- Why would the
mngtmpaddr
stop working? - Will this change still work from outside the LAN?
ssh nfs ipv6
add a comment
|
19.04
I have been using IPv6 on my LAN for a few weeks now. Ping, SSH, NFS -- all fine. Three 19.04 machines, all good.
Yesterday, after an update, the IPv6 stopped working. Processing a request to an IPv6 address on the LAN the system hangs. I say 'after an update' because I did do an update and some hours later I noticed the problem; so I'm not saying the update caused it, just noting the coincidence.
I had been using the mngtmpaddr
address as reported by the ip a command. On a try I switched to using the other IPv6 address (the /128 address) and now that one works.
This is not only a curiousity. There's an issue for me because I have been using my NFS server's IPv6 address to mount its shares when I'm away from the LAN. Previously I had to change my /etc/fstab
whenever I was away from home. So :
So what is going on?
- What is the difference between these two addresses?
- Why would the
mngtmpaddr
stop working? - Will this change still work from outside the LAN?
ssh nfs ipv6
19.04
I have been using IPv6 on my LAN for a few weeks now. Ping, SSH, NFS -- all fine. Three 19.04 machines, all good.
Yesterday, after an update, the IPv6 stopped working. Processing a request to an IPv6 address on the LAN the system hangs. I say 'after an update' because I did do an update and some hours later I noticed the problem; so I'm not saying the update caused it, just noting the coincidence.
I had been using the mngtmpaddr
address as reported by the ip a command. On a try I switched to using the other IPv6 address (the /128 address) and now that one works.
This is not only a curiousity. There's an issue for me because I have been using my NFS server's IPv6 address to mount its shares when I'm away from the LAN. Previously I had to change my /etc/fstab
whenever I was away from home. So :
So what is going on?
- What is the difference between these two addresses?
- Why would the
mngtmpaddr
stop working? - Will this change still work from outside the LAN?
ssh nfs ipv6
ssh nfs ipv6
edited Sep 11 at 20:32
Stephen Boston
asked Sep 9 at 23:08
Stephen BostonStephen Boston
1,8433 gold badges11 silver badges24 bronze badges
1,8433 gold badges11 silver badges24 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
After some research I see that the IPv6 addresses expire -- unless assigned otherwise. This default is, I believe, to protect the privacy of clients. This concern however is at odds with the requirement that servers have a consistent address.
So that's why the IPv6 addresses stopped working.
To acquire a 'static' - permanent - IPv6 I have added a IPv6 address to the netplan configuration.
renderer: networkd
wifis:
wlp3s0:
dhcp4: yes -- set through DHCP reservation
dhcp6: no
addresses: [10.0.0.120/24,"-:-:-:-::-/128"]
Where I took the IPv6 address from the current dynamically assigned IPv6 address, and the gateway from the default
route of the ip -6 r
command. (I found I had to reboot the machine to apply. A simple netplan apply
or networking restart
did not suffice.)
This assigns a forever
lifetime to the IPv6 address and creates another temporary IPv6.
One of my three machines (all fully updated 19.04) resists creating a forever
lifetime. I have fixed this with
ip a change <device IPv6 address> dev <device id> preferred_lft forever
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/4.0/"u003ecc by-sa 4.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%2f1172048%2fwhy-has-ipv6-mngtmpaddr-stopped-responding%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
After some research I see that the IPv6 addresses expire -- unless assigned otherwise. This default is, I believe, to protect the privacy of clients. This concern however is at odds with the requirement that servers have a consistent address.
So that's why the IPv6 addresses stopped working.
To acquire a 'static' - permanent - IPv6 I have added a IPv6 address to the netplan configuration.
renderer: networkd
wifis:
wlp3s0:
dhcp4: yes -- set through DHCP reservation
dhcp6: no
addresses: [10.0.0.120/24,"-:-:-:-::-/128"]
Where I took the IPv6 address from the current dynamically assigned IPv6 address, and the gateway from the default
route of the ip -6 r
command. (I found I had to reboot the machine to apply. A simple netplan apply
or networking restart
did not suffice.)
This assigns a forever
lifetime to the IPv6 address and creates another temporary IPv6.
One of my three machines (all fully updated 19.04) resists creating a forever
lifetime. I have fixed this with
ip a change <device IPv6 address> dev <device id> preferred_lft forever
add a comment
|
After some research I see that the IPv6 addresses expire -- unless assigned otherwise. This default is, I believe, to protect the privacy of clients. This concern however is at odds with the requirement that servers have a consistent address.
So that's why the IPv6 addresses stopped working.
To acquire a 'static' - permanent - IPv6 I have added a IPv6 address to the netplan configuration.
renderer: networkd
wifis:
wlp3s0:
dhcp4: yes -- set through DHCP reservation
dhcp6: no
addresses: [10.0.0.120/24,"-:-:-:-::-/128"]
Where I took the IPv6 address from the current dynamically assigned IPv6 address, and the gateway from the default
route of the ip -6 r
command. (I found I had to reboot the machine to apply. A simple netplan apply
or networking restart
did not suffice.)
This assigns a forever
lifetime to the IPv6 address and creates another temporary IPv6.
One of my three machines (all fully updated 19.04) resists creating a forever
lifetime. I have fixed this with
ip a change <device IPv6 address> dev <device id> preferred_lft forever
add a comment
|
After some research I see that the IPv6 addresses expire -- unless assigned otherwise. This default is, I believe, to protect the privacy of clients. This concern however is at odds with the requirement that servers have a consistent address.
So that's why the IPv6 addresses stopped working.
To acquire a 'static' - permanent - IPv6 I have added a IPv6 address to the netplan configuration.
renderer: networkd
wifis:
wlp3s0:
dhcp4: yes -- set through DHCP reservation
dhcp6: no
addresses: [10.0.0.120/24,"-:-:-:-::-/128"]
Where I took the IPv6 address from the current dynamically assigned IPv6 address, and the gateway from the default
route of the ip -6 r
command. (I found I had to reboot the machine to apply. A simple netplan apply
or networking restart
did not suffice.)
This assigns a forever
lifetime to the IPv6 address and creates another temporary IPv6.
One of my three machines (all fully updated 19.04) resists creating a forever
lifetime. I have fixed this with
ip a change <device IPv6 address> dev <device id> preferred_lft forever
After some research I see that the IPv6 addresses expire -- unless assigned otherwise. This default is, I believe, to protect the privacy of clients. This concern however is at odds with the requirement that servers have a consistent address.
So that's why the IPv6 addresses stopped working.
To acquire a 'static' - permanent - IPv6 I have added a IPv6 address to the netplan configuration.
renderer: networkd
wifis:
wlp3s0:
dhcp4: yes -- set through DHCP reservation
dhcp6: no
addresses: [10.0.0.120/24,"-:-:-:-::-/128"]
Where I took the IPv6 address from the current dynamically assigned IPv6 address, and the gateway from the default
route of the ip -6 r
command. (I found I had to reboot the machine to apply. A simple netplan apply
or networking restart
did not suffice.)
This assigns a forever
lifetime to the IPv6 address and creates another temporary IPv6.
One of my three machines (all fully updated 19.04) resists creating a forever
lifetime. I have fixed this with
ip a change <device IPv6 address> dev <device id> preferred_lft forever
edited Sep 29 at 15:04
answered Sep 10 at 23:55
Stephen BostonStephen Boston
1,8433 gold badges11 silver badges24 bronze badges
1,8433 gold badges11 silver badges24 bronze badges
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.
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%2f1172048%2fwhy-has-ipv6-mngtmpaddr-stopped-responding%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