Project

General

Profile

Actions

Bug #8393

closed

IPAlias VIPs on localhost are not applied at boot.

Added by Steve Wheeler over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Virtual IP Addresses
Target version:
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 #1

Updated by Pi Ba over 3 years ago

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

Actions #2

Updated by Anonymous over 3 years ago

We're testing the patch now.

Patch resolves the issue.

Actions #3

Updated by Steve Wheeler over 3 years ago

That works here.

Actions #4

Updated by Andy Kniveton over 3 years ago

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

Actions #5

Updated by Anonymous over 3 years ago

  • Status changed from New to Assigned
  • Assignee set to Luiz Souza
Actions #6

Updated by Jim Pingle over 3 years ago

  • Status changed from Assigned to Feedback
Actions #7

Updated by Pi Ba over 3 years ago

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

Actions #8

Updated by Luiz Souza over 3 years ago

Can you please elaborate PiBa ?

Actions #9

Updated by Pi Ba over 3 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 #10

Updated by Luiz Souza over 3 years ago

I forgot about these, I had the 'CARP isn't a interface anymore' thinking in my head.

Should be fixed now.

Thanks!

Actions #11

Updated by Pi Ba over 3 years ago

Works for me. Thanks Luiz!

Actions #12

Updated by Luiz Souza over 3 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100
Actions #13

Updated by Jim Pingle about 3 years ago

  • Target version changed from 2.4.4 to 2.4.3-p1
Actions

Also available in: Atom PDF