Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PfSense is constantly reloading settings

    IPv6
    4
    10
    3.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      arnog
      last edited by

      Hi all,

      I am running pfSense 2.3.2-RELEASE-p1 on a PC Engines APU1D4 connected to a Deutsche Telekom VDSL line.

      My interface configuration looks like this:

      WAN => PPPoE on re0_vlan7
      LAN => re1
      OPT1 => re2
      OPT2 => re0 (for access to the DSL modem)

      When just using IPv4 everything works fine.

      To use IPv6 I have to enable DHCP for IPv6 on the WAN interface and request the prefix/connection information over the IPv4 link. Prefix delegation size is set to 56 and "Send IPv6 prefix hint" is enabled. The IPv6 type on the LAN interface is set to track the WAN interface with prefix ID 0.

      As soon as I enable this configuration the pfSense box starts to reload the IPv6 configuration several times each minute. Although the box shows that it has IPv6 addresses on the WAN and LAN interface, I can't use IPv6. traceroute6 to an external host stops at the pfSense box. When I try to test for IPv6 connectivity using http://ipv6-test.com (for example) it shows that IPv6 is not supported.

      Here is a log excerpt:

      
Oct 10 18:03:44 pfsense check_reload_status: Reloading filter
Oct 10 18:03:45 pfsense php-fpm[53049]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 10 18:03:45 pfsense php-fpm[53049]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:537:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 10 18:03:45 pfsense php-fpm[53049]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 10 18:03:45 pfsense php-fpm[53049]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 10 18:03:45 pfsense check_reload_status: Reloading filter
Oct 10 18:03:45 pfsense xinetd[12487]: Starting reconfiguration
Oct 10 18:03:45 pfsense xinetd[12487]: Swapping defaults
Oct 10 18:03:45 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 10 18:03:45 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 10 18:03:46 pfsense xinetd[12487]: Starting reconfiguration
Oct 10 18:03:46 pfsense xinetd[12487]: Swapping defaults
Oct 10 18:03:46 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 10 18:03:46 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 10 18:03:46 pfsense php-fpm[53049]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 10 18:03:46 pfsense php-fpm[53049]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:537:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 10 18:03:46 pfsense php-fpm[53049]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 10 18:03:46 pfsense php-fpm[53049]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 10 18:03:46 pfsense check_reload_status: Reloading filter
Oct 10 18:03:47 pfsense xinetd[12487]: Starting reconfiguration
Oct 10 18:03:47 pfsense xinetd[12487]: Swapping defaults
Oct 10 18:03:47 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 10 18:03:47 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 10 18:03:48 pfsense php-fpm[53049]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 10 18:03:48 pfsense php-fpm[53049]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:537:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 10 18:03:48 pfsense php-fpm[53049]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 10 18:03:48 pfsense php-fpm[53049]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0

      What am I doing wrong here?

      Thanks
      Arno

      1 Reply Last reply Reply Quote 0
      • A
        arnog
        last edited by

        There seems to be a second report in the German section https://forum.pfsense.org/index.php?topic=119409.0. This looks to be exactly the same problem that I have.

        1 Reply Last reply Reply Quote 0
        • A
          arnog
          last edited by

          Some more detailed logs including the dhcp6c log.

          
Oct 13 09:35:44 pfsense check_reload_status: Reloading filter
Oct 13 09:35:45 pfsense xinetd[12487]: Starting reconfiguration
Oct 13 09:35:45 pfsense xinetd[12487]: Swapping defaults
Oct 13 09:35:45 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 13 09:35:45 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:780:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: Removing static route for monitor 8.8.8.8 and adding a new route through 62.155.241.152
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: Removing static route for monitor fe80::2a0:a50f:fc81:6d2e and adding a new route through fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:46 pfsense check_reload_status: Reloading filter
Oct 13 09:35:47 pfsense xinetd[12487]: Starting reconfiguration
Oct 13 09:35:47 pfsense xinetd[12487]: Swapping defaults
Oct 13 09:35:47 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 13 09:35:47 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:780:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor 8.8.8.8 and adding a new route through 62.155.241.152
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor fe80::2a0:a50f:fc81:6d2e and adding a new route through fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:47 pfsense check_reload_status: Reloading filter
Oct 13 09:35:48 pfsense xinetd[12487]: Starting reconfiguration
Oct 13 09:35:48 pfsense xinetd[12487]: Swapping defaults
Oct 13 09:35:48 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 13 09:35:48 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:780:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor 8.8.8.8 and adding a new route through 62.155.241.152
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor fe80::2a0:a50f:fc81:6d2e and adding a new route through fe80::2a0:a50f:fc81:6d2e%pppoe0


          
Oct 13 09:35:44 pfsense check_reload_status: Reloading filter
Oct 13 09:35:45 pfsense xinetd[12487]: Starting reconfiguration
Oct 13 09:35:45 pfsense xinetd[12487]: Swapping defaults
Oct 13 09:35:45 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 13 09:35:45 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:780:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: Removing static route for monitor 8.8.8.8 and adding a new route through 62.155.241.152
Oct 13 09:35:46 pfsense php-fpm[22884]: /rc.newwanipv6: Removing static route for monitor fe80::2a0:a50f:fc81:6d2e and adding a new route through fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:46 pfsense check_reload_status: Reloading filter
Oct 13 09:35:47 pfsense xinetd[12487]: Starting reconfiguration
Oct 13 09:35:47 pfsense xinetd[12487]: Swapping defaults
Oct 13 09:35:47 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 13 09:35:47 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:780:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor 8.8.8.8 and adding a new route through 62.155.241.152
Oct 13 09:35:47 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor fe80::2a0:a50f:fc81:6d2e and adding a new route through fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:47 pfsense check_reload_status: Reloading filter
Oct 13 09:35:48 pfsense xinetd[12487]: Starting reconfiguration
Oct 13 09:35:48 pfsense xinetd[12487]: Swapping defaults
Oct 13 09:35:48 pfsense xinetd[12487]: readjusting service 6969-udp
Oct 13 09:35:48 pfsense xinetd[12487]: Reconfigured: new=0 old=1 dropped=0 (services)
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: Info: starting on pppoe0.
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: rc.newwanipv6: on (IP address: 2003:cc:1bbf:780:20d:b9ff:fe3a:35c0) (interface: wan) (real interface: pppoe0).
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting default route to 62.155.241.152
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: ROUTING: setting IPv6 default route to fe80::2a0:a50f:fc81:6d2e%pppoe0
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor 8.8.8.8 and adding a new route through 62.155.241.152
Oct 13 09:35:49 pfsense php-fpm[40126]: /rc.newwanipv6: Removing static route for monitor fe80::2a0:a50f:fc81:6d2e and adding a new route through fe80::2a0:a50f:fc81:6d2e%pppoe0
          1 Reply Last reply Reply Quote 0
          • S
            stickybit
            last edited by

            Hello,

            same problem here since I try out IPv6 at the beginning of 2016. Thought it would be bug in pfsense that would be fixed in further releases … I wasn't ... :/

            Any new facts about this?

            regards from germany

            1 Reply Last reply Reply Quote 0
            • A
              arnog
              last edited by

              The only information that I could gather was that pfSense should ask for a renew of the delegated prefix when it wants to renew it. Asking for a new prefix instead doesn't seem to work at the moment. The thread where this was mentioned is here (in German): https://telekomhilft.telekom.de/t5/Telefonie-Internet/Nach-BNG-Umstellung-v6-Probleme/td-p/1954301

              If anybody knows how we could achieve this with pfSense I would be happy to know. :-)

              1 Reply Last reply Reply Quote 0
              • ?
                A Former User
                last edited by

                Same here. Had to disable IPv6 till its fixed.

                1 Reply Last reply Reply Quote 0
                • S
                  stickybit
                  last edited by

                  I opened a ticket: https://redmine.pfsense.org/issues/6981

                  1 Reply Last reply Reply Quote 0
                  • A
                    arnog
                    last edited by

                    I added some more information to that ticket as I still have this issue.

                    1 Reply Last reply Reply Quote 0
                    • ?
                      Guest
                      last edited by

                      Please look at the ticket and see my comments. I've been doing some work on dhcp6c and if you can post that information I'll do some digging and see what I can find out.

                      1 Reply Last reply Reply Quote 0
                      • A
                        arnog
                        last edited by

                        This is fixed for me now, it was a configuration error on my side. The reason for the reloading of settings was that in Telekom's new BNG network the DHCPv6 would not hand out an IPv6 address for the WAN interface, only DNS server addresses and the delegated /56 prefix comes in via DHCPv6. Because of the empty addresses part of the DHCPv6 reply, dhcp6c would retry the request after a timeout of 0 seconds. In the new BNG network the address for the WAN interface comes in via Router Advertisement.

                        This is now fixed for me by checking "Request only an IPv6 prefix".

                        IIRC in the "old" Telekom network, the WAN interface would also get an address via DHCPv6.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.