How to configure IPVS loopback address with netplan in Ubuntu 18.04?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
Previously, I configured IPVS loopback addresses in /etc/network/interfaces
like this:
auto lo:0
iface lo:0 inet static
address 12.34.56.78
netmask 255.255.255.255
pre-up sysctl -q -p
On 18.04, I tried adding this section to the netplan config:
network:
ethernets:
lo:
addresses:
- 12.34.56.78/32
And then ran netplan apply
. systemd-networkd logs the following:
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 12.34.56.78/32 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 127.0.0.1/8 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: rtnl: received address with invalid family 129, ignoring
But it doesn't seem to have any effect (ifconfig
doesn't list lo:0
). Not sure what the invalid family 129 refers to. The actual address (it's not 12.34.56.78 :-) ) works fine when I manually use ifconfig to set it up.
I also tried using lo:0
as the YAML key name, but then I get this error:
May 18 10:00:06 [...] systemd-networkd[3736]: /run/systemd/network/10-netplan-lo:0.network:2: Interface name is not valid or too long, ignoring assignment: (null)
Looks like systemd-networkd doesn't like lo:0
as an interface name. Any suggestions?
networking server 18.04 netplan
add a comment |Â
up vote
0
down vote
favorite
Previously, I configured IPVS loopback addresses in /etc/network/interfaces
like this:
auto lo:0
iface lo:0 inet static
address 12.34.56.78
netmask 255.255.255.255
pre-up sysctl -q -p
On 18.04, I tried adding this section to the netplan config:
network:
ethernets:
lo:
addresses:
- 12.34.56.78/32
And then ran netplan apply
. systemd-networkd logs the following:
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 12.34.56.78/32 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 127.0.0.1/8 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: rtnl: received address with invalid family 129, ignoring
But it doesn't seem to have any effect (ifconfig
doesn't list lo:0
). Not sure what the invalid family 129 refers to. The actual address (it's not 12.34.56.78 :-) ) works fine when I manually use ifconfig to set it up.
I also tried using lo:0
as the YAML key name, but then I get this error:
May 18 10:00:06 [...] systemd-networkd[3736]: /run/systemd/network/10-netplan-lo:0.network:2: Interface name is not valid or too long, ignoring assignment: (null)
Looks like systemd-networkd doesn't like lo:0
as an interface name. Any suggestions?
networking server 18.04 netplan
See my answer in this post, I think that is what you are looking for: askubuntu.com/questions/1033403/â¦
â user822833
May 18 at 17:02
@MikaelSchultz This seems very close to I want to do (lo:0 instead of lo:1). I tried explicitly specifyingrenderer
andmatch
, but that didn't seem to have any effect. Also FYI -- I updated the question with some more info from the logs. I wonder what I'm missing.
â kartik_subbarao
May 18 at 17:14
Turns out that my netplan config was actually working, butifconfig
could not display the additional loopback address assigned tolo
. Problem solved :-)
â kartik_subbarao
May 18 at 19:42
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Previously, I configured IPVS loopback addresses in /etc/network/interfaces
like this:
auto lo:0
iface lo:0 inet static
address 12.34.56.78
netmask 255.255.255.255
pre-up sysctl -q -p
On 18.04, I tried adding this section to the netplan config:
network:
ethernets:
lo:
addresses:
- 12.34.56.78/32
And then ran netplan apply
. systemd-networkd logs the following:
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 12.34.56.78/32 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 127.0.0.1/8 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: rtnl: received address with invalid family 129, ignoring
But it doesn't seem to have any effect (ifconfig
doesn't list lo:0
). Not sure what the invalid family 129 refers to. The actual address (it's not 12.34.56.78 :-) ) works fine when I manually use ifconfig to set it up.
I also tried using lo:0
as the YAML key name, but then I get this error:
May 18 10:00:06 [...] systemd-networkd[3736]: /run/systemd/network/10-netplan-lo:0.network:2: Interface name is not valid or too long, ignoring assignment: (null)
Looks like systemd-networkd doesn't like lo:0
as an interface name. Any suggestions?
networking server 18.04 netplan
Previously, I configured IPVS loopback addresses in /etc/network/interfaces
like this:
auto lo:0
iface lo:0 inet static
address 12.34.56.78
netmask 255.255.255.255
pre-up sysctl -q -p
On 18.04, I tried adding this section to the netplan config:
network:
ethernets:
lo:
addresses:
- 12.34.56.78/32
And then ran netplan apply
. systemd-networkd logs the following:
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 12.34.56.78/32 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: lo: Adding address: 127.0.0.1/8 (valid forever)
May 18 10:01:55 [...] systemd-networkd[3820]: rtnl: received address with invalid family 129, ignoring
But it doesn't seem to have any effect (ifconfig
doesn't list lo:0
). Not sure what the invalid family 129 refers to. The actual address (it's not 12.34.56.78 :-) ) works fine when I manually use ifconfig to set it up.
I also tried using lo:0
as the YAML key name, but then I get this error:
May 18 10:00:06 [...] systemd-networkd[3736]: /run/systemd/network/10-netplan-lo:0.network:2: Interface name is not valid or too long, ignoring assignment: (null)
Looks like systemd-networkd doesn't like lo:0
as an interface name. Any suggestions?
networking server 18.04 netplan
edited May 18 at 18:12
asked May 18 at 16:54
kartik_subbarao
1267
1267
See my answer in this post, I think that is what you are looking for: askubuntu.com/questions/1033403/â¦
â user822833
May 18 at 17:02
@MikaelSchultz This seems very close to I want to do (lo:0 instead of lo:1). I tried explicitly specifyingrenderer
andmatch
, but that didn't seem to have any effect. Also FYI -- I updated the question with some more info from the logs. I wonder what I'm missing.
â kartik_subbarao
May 18 at 17:14
Turns out that my netplan config was actually working, butifconfig
could not display the additional loopback address assigned tolo
. Problem solved :-)
â kartik_subbarao
May 18 at 19:42
add a comment |Â
See my answer in this post, I think that is what you are looking for: askubuntu.com/questions/1033403/â¦
â user822833
May 18 at 17:02
@MikaelSchultz This seems very close to I want to do (lo:0 instead of lo:1). I tried explicitly specifyingrenderer
andmatch
, but that didn't seem to have any effect. Also FYI -- I updated the question with some more info from the logs. I wonder what I'm missing.
â kartik_subbarao
May 18 at 17:14
Turns out that my netplan config was actually working, butifconfig
could not display the additional loopback address assigned tolo
. Problem solved :-)
â kartik_subbarao
May 18 at 19:42
See my answer in this post, I think that is what you are looking for: askubuntu.com/questions/1033403/â¦
â user822833
May 18 at 17:02
See my answer in this post, I think that is what you are looking for: askubuntu.com/questions/1033403/â¦
â user822833
May 18 at 17:02
@MikaelSchultz This seems very close to I want to do (lo:0 instead of lo:1). I tried explicitly specifying
renderer
and match
, but that didn't seem to have any effect. Also FYI -- I updated the question with some more info from the logs. I wonder what I'm missing.â kartik_subbarao
May 18 at 17:14
@MikaelSchultz This seems very close to I want to do (lo:0 instead of lo:1). I tried explicitly specifying
renderer
and match
, but that didn't seem to have any effect. Also FYI -- I updated the question with some more info from the logs. I wonder what I'm missing.â kartik_subbarao
May 18 at 17:14
Turns out that my netplan config was actually working, but
ifconfig
could not display the additional loopback address assigned to lo
. Problem solved :-)â kartik_subbarao
May 18 at 19:42
Turns out that my netplan config was actually working, but
ifconfig
could not display the additional loopback address assigned to lo
. Problem solved :-)â kartik_subbarao
May 18 at 19:42
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
It turns out that the netplan configuration did assign the additional loopback address to lo, but ifconfig
couldn't display it, which was misleading me. When I manually ran ifconfig lo:0 12.34.56.78 netmask 255.255.255.255
it displayed lo:0
just fine. But netplan assigned the address to lo
, not lo:0
. Running ip addr
revealed the additional IP address on lo
.
Upon further reading, I found that ifconfig
(net-tools) has long been deprecated in favor of ip
(iproute): https://serverfault.com/questions/633087/where-is-the-statement-of-deprecation-of-ifconfig-on-linux
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It turns out that the netplan configuration did assign the additional loopback address to lo, but ifconfig
couldn't display it, which was misleading me. When I manually ran ifconfig lo:0 12.34.56.78 netmask 255.255.255.255
it displayed lo:0
just fine. But netplan assigned the address to lo
, not lo:0
. Running ip addr
revealed the additional IP address on lo
.
Upon further reading, I found that ifconfig
(net-tools) has long been deprecated in favor of ip
(iproute): https://serverfault.com/questions/633087/where-is-the-statement-of-deprecation-of-ifconfig-on-linux
add a comment |Â
up vote
1
down vote
accepted
It turns out that the netplan configuration did assign the additional loopback address to lo, but ifconfig
couldn't display it, which was misleading me. When I manually ran ifconfig lo:0 12.34.56.78 netmask 255.255.255.255
it displayed lo:0
just fine. But netplan assigned the address to lo
, not lo:0
. Running ip addr
revealed the additional IP address on lo
.
Upon further reading, I found that ifconfig
(net-tools) has long been deprecated in favor of ip
(iproute): https://serverfault.com/questions/633087/where-is-the-statement-of-deprecation-of-ifconfig-on-linux
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It turns out that the netplan configuration did assign the additional loopback address to lo, but ifconfig
couldn't display it, which was misleading me. When I manually ran ifconfig lo:0 12.34.56.78 netmask 255.255.255.255
it displayed lo:0
just fine. But netplan assigned the address to lo
, not lo:0
. Running ip addr
revealed the additional IP address on lo
.
Upon further reading, I found that ifconfig
(net-tools) has long been deprecated in favor of ip
(iproute): https://serverfault.com/questions/633087/where-is-the-statement-of-deprecation-of-ifconfig-on-linux
It turns out that the netplan configuration did assign the additional loopback address to lo, but ifconfig
couldn't display it, which was misleading me. When I manually ran ifconfig lo:0 12.34.56.78 netmask 255.255.255.255
it displayed lo:0
just fine. But netplan assigned the address to lo
, not lo:0
. Running ip addr
revealed the additional IP address on lo
.
Upon further reading, I found that ifconfig
(net-tools) has long been deprecated in favor of ip
(iproute): https://serverfault.com/questions/633087/where-is-the-statement-of-deprecation-of-ifconfig-on-linux
answered May 18 at 19:40
kartik_subbarao
1267
1267
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1037834%2fhow-to-configure-ipvs-loopback-address-with-netplan-in-ubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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
See my answer in this post, I think that is what you are looking for: askubuntu.com/questions/1033403/â¦
â user822833
May 18 at 17:02
@MikaelSchultz This seems very close to I want to do (lo:0 instead of lo:1). I tried explicitly specifying
renderer
andmatch
, but that didn't seem to have any effect. Also FYI -- I updated the question with some more info from the logs. I wonder what I'm missing.â kartik_subbarao
May 18 at 17:14
Turns out that my netplan config was actually working, but
ifconfig
could not display the additional loopback address assigned tolo
. Problem solved :-)â kartik_subbarao
May 18 at 19:42