Bug #8393: IPAlias VIPs on localhost are not applied at boot. - pfSense - pfSense bugtracker

Actions

Copy link

Bug #8393

closed

IPAlias VIPs on localhost are not applied at boot.

Added by Steve Wheeler over 6 years ago. Updated over 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Luiz Souza

Category:

Virtual IP Addresses

Target version:

2.4.3-p1

Start date:

03/29/2018

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.4.3

Affected Architecture:

All

Description

An VIP configured like:

<vip>
    <mode>ipalias</mode>
    <interface>lo0</interface>
    <uniqid>5abd4e7832f51</uniqid>
    <descr><![CDATA[Test on lo0]]></descr>
    <type>single</type>
    <subnet_bits>32</subnet_bits>
    <subnet>192.168.0.1</subnet>
</vip>

Is not present after booting:

[2.4.3-RELEASE][admin@apu.stevew.lan]/root: ifconfig lo0
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
    inet6 ::1 prefixlen 128 
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 
    inet 127.0.0.1 netmask 0xff000000 
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
    groups: lo

But after resaving the VIP via the GUI is added:

[2.4.3-RELEASE][admin@apu.stevew.lan]/root: ifconfig lo0
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
    inet6 ::1 prefixlen 128 
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 
    inet 127.0.0.1 netmask 0xff000000 
    inet 192.168.0.1 netmask 0xffffffff 
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
    groups: lo

It does not affect other real interfaces.

Actions

Copy link

Updated by Pi Ba over 6 years ago

I've noticed that to, can you try the patch?: https://github.com/pfsense/pfsense/pull/3920

Actions

Copy link

Updated by Anonymous over 6 years ago

We're testing the patch now.

Patch resolves the issue.

Actions

Copy link

Updated by Steve Wheeler over 6 years ago

That works here.

Actions

Copy link

Updated by Andy Kniveton over 6 years ago

Works fine for me too, no need to go back into the VIPs and resave.

Actions

Copy link

Updated by Anonymous over 6 years ago

Status changed from New to Assigned
Assignee set to Luiz Souza

Actions

Copy link

Updated by Jim Pingle over 6 years ago

Status changed from Assigned to Feedback

Actions

Copy link

Updated by Pi Ba over 6 years ago

Seems now a IPalias under a CARP parent is not applied.?

Actions

Copy link

Updated by Luiz Souza over 6 years ago

Can you please elaborate PiBa ?

Actions

Copy link

Updated by Pi Ba over 6 years ago

Hi Luiz,

To have multiple highly available IP's on 1 interface its possible to configure a vip of type "alias" and choose as the interface a vip that has the type "CARP" while that CARP ip is for example on the interface LAN.

        <vip>
            <mode>ipalias</mode>
            <interface>_vip57e6821202aca</interface>
            <uniqid>57e68233b6130</uniqid>
            <descr><![CDATA[This is a IPalias with a CARP parent]]></descr>
            <type>single</type>
            <subnet_bits>24</subnet_bits>
            <subnet>192.168.0.202</subnet>
        </vip>

Actions

Copy link

#10