LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [lvs-users] Issues configuring real server VIP lo:0 address on Ubunt

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [lvs-users] Issues configuring real server VIP lo:0 address on Ubuntu 18.04 with netplan/systemd-networkd
From: Kartik Subbarao <subbarao@xxxxxxxxxxxx>
Date: Fri, 18 May 2018 15:45:03 -0400
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. Problem solved :-)

     -Kartik

On 05/18/2018 02:14 PM, Kartik Subbarao wrote:
> Has anyone been successful with configuring real server VIP addresses 
> (lo:0) on Ubuntu 18.04?
>
> Previously, I configured the loopback address 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?
>
> Thanks,
>
>     -Kartik
>


_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
<Prev in Thread] Current Thread [Next in Thread>