Project

General

Profile

Bug #10661

pfSense configures fe80::1:1 on lan interface without track6

Added by Viktor Gurov 5 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Category:
Interfaces
Target version:
Start date:
06/13/2020
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.5-p1
Affected Architecture:

Description

While creating CARP IPv6 VIP interface on clean pfSense CE 2.4.5-p1 install,
I noticed that both nodes have fe80::1:1 address:

# ifconfig vtnet0
vtnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
    ether 0c:c5:49:d7:8c:00
    hwaddr 0c:c5:49:d7:8c:00
    inet6 fe80::1:1%vtnet0 prefixlen 64 scopeid 0x1
    inet6 fc00:3::51 prefixlen 64
    inet6 fc00:3::55 prefixlen 64 vhid 2
    inet 192.168.3.51 netmask 0xffffff00 broadcast 192.168.3.255
    inet 192.168.3.55 netmask 0xffffff00 broadcast 192.168.3.255 vhid 1
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
    media: Ethernet 10Gbase-T <full-duplex>
    status: active
    carp: MASTER vhid 1 advbase 1 advskew 0
    carp: MASTER vhid 2 advbase 1 advskew 0

and secondary node:

# ifconfig vtnet0
vtnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
    ether 0c:c5:49:26:9f:00
    hwaddr 0c:c5:49:26:9f:00
    inet6 fe80::1:1%vtnet0 prefixlen 64 duplicated scopeid 0x1
    inet6 fc00:3::52 prefixlen 64
    inet6 fc00:3::55 prefixlen 64 vhid 2
    inet 192.168.3.52 netmask 0xffffff00 broadcast 192.168.3.255
    inet 192.168.3.55 netmask 0xffffff00 broadcast 192.168.3.255 vhid 1
    nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
    media: Ethernet 10Gbase-T <full-duplex>
    status: active
    carp: BACKUP vhid 1 advbase 1 advskew 100
    carp: MASTER vhid 2 advbase 1 advskew 100

both nodes have static IPv6 addresses, and no any other IPv6 addresses - WAN is DHCP (IPv4), and SYNC interface is Static IPv4

I don't this is a CARP/HA issue, it seems to be a bug with link_interface_to_track6() or interface_track6_configure() and clean config

Associated revisions

Revision 2bdf0364 (diff)
Added by Viktor Gurov 5 months ago

Remove fe80::1:1 from interface. Issue #10661

History

#1 Updated by Viktor Gurov 5 months ago

Found the issue -
on initial interface setup in console, it automatically set
DHCP + DHCP6 on the WAN interface, and 192.168.1.1 + Track WAN interface on the LAN interface,
but when I go to the Interfaces / LAN page, it shows IPv6 Configuration Type = None,
because of ipaddrv6 is empty:

<lan>
                        <enable></enable>
                        <if>vtnet0</if>
                        <ipaddr>192.168.1.1</ipaddr>
                        <subnet>24</subnet>
                        <ipaddrv6></ipaddrv6>
                        <subnetv6></subnetv6>
                        <media></media>
                        <mediaopt></mediaopt>
                        <track6-interface>wan</track6-interface>
                        <track6-prefix-id>0</track6-prefix-id>
                        <gateway></gateway>
                        <gatewayv6></gatewayv6>
</lan>

after switching IPv6 mode to Static, fe80::1:1 is not removed from the interface

#2 Updated by Viktor Gurov 5 months ago

Remove fe80::1:1 alias from interface in interface_configure() "remove all IPv4 and IPv6 addresses" loop:
https://github.com/pfsense/pfsense/pull/4354

#3 Updated by Viktor Gurov 5 months ago

Viktor Gurov wrote:

but when I go to the Interfaces / LAN page, it shows IPv6 Configuration Type = None,
because of ipaddrv6 is empty:
[...]

None, this is correct, it empty after setting IPv6 to none in 'Set interface(s) IP address' menu

#4 Updated by Jim Pingle 5 months ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0

#5 Updated by Renato Botelho 4 months ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

#6 Updated by Viktor Gurov 4 months ago

  • Status changed from Feedback to Resolved

works fine on 2.5.0.a.20200622.1850 - fe80::1:1 successfully removed from interface after switching from Track Interface to other IPv6 Configuration Type

Also available in: Atom PDF