Server 18.04: netplan and link-local addressing

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I have begun experimenting with Ubuntu Server 18.04 and I ran into a problem with configuring the network. I have a PC with two network ports and one of those two ports has to get an IPv4 link-local address. In the desktop version I can achieve this by going into NetworkManager and then choose the link-local option. But with Server I have to use that new netplan program. However, the manual and other online resources make it not at all clear to me on how to achieve this. There's stuff to be found on setting up DHCP and static address but nothing on using Avahi (which Desktop uses) or other means of obtaining a 169.254.x.y address.



So: how can I write a yaml configuration that instructs netplan to set up link-local addressing on an interface?







share|improve this question




















  • This is not an answer to the question, because currently it's not supported at all in netplan yaml; but I've filed a bug about adding support for this: bugs.launchpad.net/netplan/+bug/1771704
    – slangasek
    May 17 at 0:08










  • Thanks for filing the report. At least it's good to know that netplan has no support for this yet.
    – Nathilion
    May 18 at 5:00














up vote
0
down vote

favorite












I have begun experimenting with Ubuntu Server 18.04 and I ran into a problem with configuring the network. I have a PC with two network ports and one of those two ports has to get an IPv4 link-local address. In the desktop version I can achieve this by going into NetworkManager and then choose the link-local option. But with Server I have to use that new netplan program. However, the manual and other online resources make it not at all clear to me on how to achieve this. There's stuff to be found on setting up DHCP and static address but nothing on using Avahi (which Desktop uses) or other means of obtaining a 169.254.x.y address.



So: how can I write a yaml configuration that instructs netplan to set up link-local addressing on an interface?







share|improve this question




















  • This is not an answer to the question, because currently it's not supported at all in netplan yaml; but I've filed a bug about adding support for this: bugs.launchpad.net/netplan/+bug/1771704
    – slangasek
    May 17 at 0:08










  • Thanks for filing the report. At least it's good to know that netplan has no support for this yet.
    – Nathilion
    May 18 at 5:00












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have begun experimenting with Ubuntu Server 18.04 and I ran into a problem with configuring the network. I have a PC with two network ports and one of those two ports has to get an IPv4 link-local address. In the desktop version I can achieve this by going into NetworkManager and then choose the link-local option. But with Server I have to use that new netplan program. However, the manual and other online resources make it not at all clear to me on how to achieve this. There's stuff to be found on setting up DHCP and static address but nothing on using Avahi (which Desktop uses) or other means of obtaining a 169.254.x.y address.



So: how can I write a yaml configuration that instructs netplan to set up link-local addressing on an interface?







share|improve this question












I have begun experimenting with Ubuntu Server 18.04 and I ran into a problem with configuring the network. I have a PC with two network ports and one of those two ports has to get an IPv4 link-local address. In the desktop version I can achieve this by going into NetworkManager and then choose the link-local option. But with Server I have to use that new netplan program. However, the manual and other online resources make it not at all clear to me on how to achieve this. There's stuff to be found on setting up DHCP and static address but nothing on using Avahi (which Desktop uses) or other means of obtaining a 169.254.x.y address.



So: how can I write a yaml configuration that instructs netplan to set up link-local addressing on an interface?









share|improve this question











share|improve this question




share|improve this question










asked May 11 at 5:09









Nathilion

63




63











  • This is not an answer to the question, because currently it's not supported at all in netplan yaml; but I've filed a bug about adding support for this: bugs.launchpad.net/netplan/+bug/1771704
    – slangasek
    May 17 at 0:08










  • Thanks for filing the report. At least it's good to know that netplan has no support for this yet.
    – Nathilion
    May 18 at 5:00
















  • This is not an answer to the question, because currently it's not supported at all in netplan yaml; but I've filed a bug about adding support for this: bugs.launchpad.net/netplan/+bug/1771704
    – slangasek
    May 17 at 0:08










  • Thanks for filing the report. At least it's good to know that netplan has no support for this yet.
    – Nathilion
    May 18 at 5:00















This is not an answer to the question, because currently it's not supported at all in netplan yaml; but I've filed a bug about adding support for this: bugs.launchpad.net/netplan/+bug/1771704
– slangasek
May 17 at 0:08




This is not an answer to the question, because currently it's not supported at all in netplan yaml; but I've filed a bug about adding support for this: bugs.launchpad.net/netplan/+bug/1771704
– slangasek
May 17 at 0:08












Thanks for filing the report. At least it's good to know that netplan has no support for this yet.
– Nathilion
May 18 at 5:00




Thanks for filing the report. At least it's good to know that netplan has no support for this yet.
– Nathilion
May 18 at 5:00















active

oldest

votes











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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034762%2fserver-18-04-netplan-and-link-local-addressing%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1034762%2fserver-18-04-netplan-and-link-local-addressing%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

GRUB: Fatal! inconsistent data read from (0x84) 0+xxxxxx

`kcmshell` modules relation with `/usr/share/applications`

How to enroll fingerprints to Ubuntu 17.10 with VFS491