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

    IPv6 No Gateway after 2.5 upgrade

    Scheduled Pinned Locked Moved IPv6
    97 Posts 27 Posters 29.6k Views
    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.
    • viktor_gV
      viktor_g Netgate @mrsunfire
      last edited by

      @mrsunfire Please attach the /var/log/dhcpd.log file for checking

      M 1 Reply Last reply Reply Quote 0
      • M
        mrsunfire @viktor_g
        last edited by mrsunfire

        @viktor_g said in IPv6 No Gateway after 2.5 upgrade:

        /var/log/dhcpd.log

        igb5 = WAN (DHCP6), igb4 = LAN (tracked)

        Feb 19 09:21:26 pfsense dhcp6c[25262]: Sending Solicit
Feb 19 09:21:26 pfsense dhcp6c[25262]: a new XID (56b2b5) is generated
Feb 19 09:21:26 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:26 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:26 pfsense dhcp6c[25262]: send solicit to ff02::1:2%igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1091
Feb 19 09:21:26 pfsense dhcp6c[25262]: receive advertise from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162142, T2=259427
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324284 vltime=929084
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162137, T2=259420
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324275 vltime=929075
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option preference, len 1
Feb 19 09:21:26 pfsense dhcp6c[25262]:   preference: 255
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:26 pfsense dhcp6c[25262]: server ID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx, pref=255
Feb 19 09:21:26 pfsense dhcp6c[25262]: Sending Request
Feb 19 09:21:26 pfsense dhcp6c[25262]: a new XID (1e2c66) is generated
Feb 19 09:21:26 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set server ID (len 14)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA address
Feb 19 09:21:26 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:26 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:26 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:26 pfsense dhcp6c[25262]: send request to ff02::1:2%igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: reset a timer on igb5, state=REQUEST, timeo=0, retrans=909
Feb 19 09:21:26 pfsense dhcp6c[25262]: receive reply from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:26 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162142, T2=259427
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324284 vltime=929084
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162137, T2=259420
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:26 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324275 vltime=929075
Feb 19 09:21:26 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:26 pfsense dhcp6c[25262]: dhcp6c Received REQUEST
Feb 19 09:21:26 pfsense dhcp6c[25262]: nameserver[0] 2a02:908:2:a::1
Feb 19 09:21:26 pfsense dhcp6c[25262]: nameserver[1] 2a02:908:2:b::1
Feb 19 09:21:26 pfsense dhcp6c[25262]: make an IA: PD-0
Feb 19 09:21:26 pfsense dhcp6c[25262]: create a prefix 2a02:80xx:xxx:xxxx::/56 pltime=324275, vltime=929075
Feb 19 09:21:26 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 on igb4
Feb 19 09:21:26 pfsense dhcp6c[25262]: make an IA: NA-0
Feb 19 09:21:26 pfsense dhcp6c[25262]: create an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324284, vltime=2143238558160137532
Feb 19 09:21:26 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx/128 on igb5
Feb 19 09:21:26 pfsense dhcp6c[25262]: executes /var/etc/dhcp6c_wan_script.sh
Feb 19 09:21:26 pfsense dhcp6c[26929]: dhcp6c RELEASE, REQUEST or EXIT on igb5 running rc.newwanipv6
Feb 19 09:21:28 pfsense dhcp6c[25262]: script "/var/etc/dhcp6c_wan_script.sh" terminated
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing an event on igb5, state=REQUEST
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing server (ID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx)
Feb 19 09:21:28 pfsense dhcp6c[25262]: got an expected reply, sleeping.
Feb 19 09:21:28 pfsense dhcp6c[25262]: restarting
Feb 19 09:21:28 pfsense dhcp6c[25262]: Bypassing address release because of -n flag
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an IA: NA-0
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx/128 on igb5
Feb 19 09:21:28 pfsense dhcp6c[25262]: reset a timer on igb5, state=INIT, timeo=0, retrans=118
Feb 19 09:21:28 pfsense dhcp6c[25262]: Bypassing address release because of -n flag
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an IA: PD-0
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove a site prefix 2a02:80xx:xxx:xxxx::/56
Feb 19 09:21:28 pfsense dhcp6c[25262]: remove an address 2a02:80xx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 on igb4
Feb 19 09:21:28 pfsense dhcp6c[25262]: reset a timer on igb5, state=INIT, timeo=0, retrans=256
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing an event on igb5, state=INIT
Feb 19 09:21:28 pfsense dhcp6c[25262]: removing an event on igb5, state=INIT
Feb 19 09:21:28 pfsense dhcp6c[25262]: reset a timer on igb5, state=INIT, timeo=0, retrans=244
Feb 19 09:21:29 pfsense dhcp6c[25262]: Sending Solicit
Feb 19 09:21:29 pfsense dhcp6c[25262]: a new XID (2fb2e1) is generated
Feb 19 09:21:29 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:29 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:29 pfsense dhcp6c[25262]: send solicit to ff02::1:2%igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1055
Feb 19 09:21:29 pfsense dhcp6c[25262]: receive advertise from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=302400, T2=483840
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx pltime=604800 vltime=1209600
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=302400, T2=483840
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:8071:xxxx:xxxx::/56 pltime=604800 vltime=1209600
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option preference, len 1
Feb 19 09:21:29 pfsense dhcp6c[25262]:   preference: 0
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:29 pfsense dhcp6c[25262]: server ID: 00:01:00:01:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx, pref=0
Feb 19 09:21:29 pfsense dhcp6c[25262]: reset timer for igb5 to 0.985677
Feb 19 09:21:29 pfsense dhcp6c[25262]: receive advertise from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162140, T2=259424
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324281 vltime=929081
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162136, T2=259417
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324272 vltime=929072
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option preference, len 1
Feb 19 09:21:29 pfsense dhcp6c[25262]:   preference: 255
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:29 pfsense dhcp6c[25262]: server ID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx, pref=255
Feb 19 09:21:29 pfsense dhcp6c[25262]: Sending Request
Feb 19 09:21:29 pfsense dhcp6c[25262]: a new XID (c679ec) is generated
Feb 19 09:21:29 pfsense dhcp6c[25262]: set client ID (len 10)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set server ID (len 14)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA address
Feb 19 09:21:29 pfsense dhcp6c[25262]: set identity association
Feb 19 09:21:29 pfsense dhcp6c[25262]: set elapsed time (len 2)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set option request (len 4)
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD prefix
Feb 19 09:21:29 pfsense dhcp6c[25262]: set IA_PD
Feb 19 09:21:29 pfsense dhcp6c[25262]: send request to ff02::1:2%igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: reset a timer on igb5, state=REQUEST, timeo=0, retrans=1019
Feb 19 09:21:29 pfsense dhcp6c[25262]: receive reply from fe80::201:5cff:xxxx:xxxx%igb5 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option client ID, len 10
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:03:00:01:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option server ID, len 14
Feb 19 09:21:29 pfsense dhcp6c[25262]:   DUID: 00:01:00:01:15:b9:82:xx:xx:xx:xx:xx:xx
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option identity association, len 40
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA: ID=0, T1=162140, T2=259424
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA address, len 24
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_NA address: 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324281 vltime=929081
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD, len 41
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD: ID=0, T1=162136, T2=259417
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option IA_PD prefix, len 25
Feb 19 09:21:29 pfsense dhcp6c[25262]:   IA_PD prefix: 2a02:80xx:xxx:xxxx::/56 pltime=324272 vltime=929072
Feb 19 09:21:29 pfsense dhcp6c[25262]: get DHCP option DNS, len 32
Feb 19 09:21:29 pfsense dhcp6c[25262]: dhcp6c Received REQUEST
Feb 19 09:21:29 pfsense dhcp6c[25262]: nameserver[0] 2a02:908:2:a::1
Feb 19 09:21:29 pfsense dhcp6c[25262]: nameserver[1] 2a02:908:2:b::1
Feb 19 09:21:29 pfsense dhcp6c[25262]: make an IA: PD-0
Feb 19 09:21:29 pfsense dhcp6c[25262]: create a prefix 2a02:80xx:xxx:xxxx::/56 pltime=324272, vltime=929072
Feb 19 09:21:29 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 on igb4
Feb 19 09:21:29 pfsense dhcp6c[25262]: make an IA: NA-0
Feb 19 09:21:29 pfsense dhcp6c[25262]: create an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx pltime=324281, vltime=2143238558160137529
Feb 19 09:21:29 pfsense dhcp6c[25262]: add an address 2a02:80xx:xxx:x:xxxx:xxxx:xxxx:xxxx:xxxx/128 on igb5
Feb 19 09:21:29 pfsense dhcp6c[25262]: executes /var/etc/dhcp6c_wan_script.sh
Feb 19 09:21:29 pfsense dhcp6c[34946]: dhcp6c RELEASE, REQUEST or EXIT on igb5 running rc.newwanipv6

        Netgate 6100 MAX

        1 Reply Last reply Reply Quote 0
        • provelsP
          provels
          last edited by provels

          This worked for me. Now passes on all IPv6 test sites I tried.

          https://forum.netgate.com/topic/161047/updated-to-2-5-everything-went-smooth-except-for-wan-ipv6-status-being-stuck-on-unknown-and-pending-have-comcast-despite-multiple-cable-modem-restarts-and-pfsense-restarts/3

          Peder

          MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
          BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

          1 Reply Last reply Reply Quote 0
          • A
            amessinamessinet.com
            last edited by

            As suggested, manually adding the Monitor address seems to solve part of the issue, though with Gateway hardcoded as "dynamic", it seems to affect the ability to use it in firewall rules -- CoDel Limiters, for example below.

            21:00:51 There were error(s) loading the rules: /tmp/rules.debug:223: no routing address with matching address family found. - The line in question reads [223]: pass  out  quick  on {  igb1  }  $GWWAN_DHCP6 inet6 from any to any tracker 1610764779 keep state  dnqueue( 2,1)  label "USER_RULE: CoDel Limiters"
            H S MikeV7896M 3 Replies Last reply Reply Quote 0
            • H
              heyj @amessinamessinet.com
              last edited by

              @amessinamessinet-com I am having the same issue.

              1 Reply Last reply Reply Quote 0
              • S
                Segfault 0 @amessinamessinet.com
                last edited by

                @amessinamessinet-com This is the problem I'm having as well. I set the monitor address to the link-local address but now my CoDel Limiter for IPv6 is giving that error.

                1 Reply Last reply Reply Quote 0
                • MikeV7896M
                  MikeV7896 @amessinamessinet.com
                  last edited by

                  @amessinamessinet-com said in IPv6 No Gateway after 2.5 upgrade:

                  As suggested, manually adding the Monitor address seems to solve part of the issue, though with Gateway hardcoded as "dynamic", it seems to affect the ability to use it in firewall rules -- CoDel Limiters, for example below.

                  Yep... See this bug: https://redmine.pfsense.org/issues/11454

                  As you mentioned, only part of the issue has a workaround (the monitoring, which affects IPv6 connectivity as a whole). The gateway selection part will likely require an update to pfSense once fixed.

                  The S in IOT stands for Security

                  1 Reply Last reply Reply Quote 0
                  • peteP
                    pete
                    last edited by pete

                    This post is deleted!
                    M 1 Reply Last reply Reply Quote 0
                    • M
                      mrsunfire @pete
                      last edited by

                      Still no ETA for a fix? IPv6 is unusable after WAN fails one time.

                      Netgate 6100 MAX

                      1 Reply Last reply Reply Quote 2
                      • S
                        SteveITS Galactic Empire @anzenketh
                        last edited by SteveITS

                        @anzenketh said in IPv6 No Gateway after 2.5 upgrade:

                        I can ping ipv6.google.com with IP protocol IPV6 from Diagnostics -> Ping

                        That's where I am on an SG-2100 with 21.02, I can ping that from my PC behind it. Status/Interfaces has a default route for IPv6. The router has a default route for IPv6 in Diagnostics/Routes, just no gateway for IPv6 shown in Status/Interfaces.

                        It sounds like some people have IPv6 connectivity and some don't? Essentially for me it's just a cosmetic issue with the GUI. After upgrade I (re)installed pfBlockerNG-devel and Snort but didn't reboot again.

                        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                        Upvote 👍 helpful posts!

                        1 Reply Last reply Reply Quote 0
                        • G
                          g.shaffer
                          last edited by

                          I noticed that both /tmp/em0_routerv6 and /tmp/em0_defaultgwv6 were empty while the ipv4 versions had the valid router addresses in them. Both of these are set in the script /var/etc/rtsold_em0_script.sh which is built by the script /etc/inc/interfaces.inc. It looks like the parameter is not being passed to the script. I modified the routine in interfaces.inc that builds the resold_em0_script (search for "rtsoldscript") to set a hard coded value for both these files and my IPv6 gateway started working! Routing, firewall rules, Policy Based Routing, etc, all work!

                          My mods:

                          #echo $2 > /tmp/em0_routerv6
                          echo "fe80::X:X:X:X" > /tmp/em0_routerv6
                          #echo $2 > /tmp/em0_defaultgwv6
                          echo "fe80::X:X:X:X" > /tmp/em0_defaultgwv6

                          After I made the mods, I "saved" the WAN interface again without making any changes. Hope this helps someone until a real fix is pushed out.

                          G R M 3 Replies Last reply Reply Quote 1
                          • G
                            g.shaffer @g.shaffer
                            last edited by g.shaffer

                            @g-shaffer

                            UPDATE:

                            Here is a diff of my changes to /etc/inc/interfaces.inc

                            interfaces.inc.diff

                            M 1 Reply Last reply Reply Quote 2
                            • M
                              mrsunfire @g.shaffer
                              last edited by

                              @g-shaffer Worked for me, thank you!

                              Netgate 6100 MAX

                              peteP 1 Reply Last reply Reply Quote 0
                              • peteP
                                pete @mrsunfire
                                last edited by

                                @mrsunfire - thank you. It is working for me here.

                                1 Reply Last reply Reply Quote 0
                                • R
                                  randyshoopman @g.shaffer
                                  last edited by randyshoopman

                                  I'm also seeing this issue.

                                  @g-shaffer What are you setting as the "hard coded value"? The Link Local IPv6 address of the WAN?

                                  G 1 Reply Last reply Reply Quote 0
                                  • G
                                    g.shaffer @randyshoopman
                                    last edited by

                                    @randyshoopman I got it by looking for the "receive advertise from ..." in the dhcpd.log, but you should be able to use the default IPv6 route address (minus the %interface) listed in the default route table (Diagnostics -> Routes).

                                    R 1 Reply Last reply Reply Quote 0
                                    • R
                                      randyshoopman @g.shaffer
                                      last edited by

                                      @g-shaffer I don't seem to have any log entries in my dhcp.log with that exact text. In any case the default route has an fe80 link local address. I will try that -- thanks

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        MarcO42 @g.shaffer
                                        last edited by

                                        @g-shaffer Hi, I did this change with the result that I got a static IPv6 address to monitor.
                                        Btw. This can slo be done here -> System - Routing - Gateways - Edit WAN_DHCP6 -> Monitor IP

                                        But now come the strange part: After I realised that I can do this also in the configuration I revert the change to

                                                $rtsoldscript .= "# This shell script launches dhcp6c and configured gateways for this interface.\n";
        $rtsoldscript .= "echo $2 > {$g['tmp_path']}/{$wanif}_routerV6\n";
        $rtsoldscript .= "echo $2 > {$g['tmp_path']}/{$wanif}_defaultgwv6\n";
        $rtsoldscript .= "/usr/bin/logger -t rtsold \"Received RA specifying route \$2 for interface {$interface}({$wanif})\"\n";

                                        It works. I can not explin why but it works :)
                                        Cheers
                                        Marco

                                        peteP 1 Reply Last reply Reply Quote 0
                                        • peteP
                                          pete @MarcO42
                                          last edited by pete

                                          @marco42

                                          Putting the local link address as an IP6 monitoring address is the first thing I did to originally "fix" the issue.

                                          This time around went back to putting in the google IP6 address as a monitoring address for IP6:

                                          1 - 2001:4860:4860::8888
                                          2 - 2001:4860:4860::8844

                                          This Google DNS monitoring address is what I was using for PFSense 2.4.x

                                          That and went to diagnostics / routes / IP6 routes and took the local interface FE80 address minus the %em1 and used it in the diff file.

                                          I wanted to just leave it alone for time bean as it is working and everytime I play with this I lose my IP6 connectivity.

                                          On the second WAN failover interface which is using a CPE to T-Mobile I tested it with my Laptop and do get an IP6 address just fine. When I connect it to PFSense and set it to IP6 dhcp I do not get an address. I am not sure how to figure this out so went back to connecting to the LAN interface and using that as a WAN interface for my failover.

                                          That and not relating to OP I noticed I lost my IPSec and OpenVPN stuff. Fixed the OpenVPN stuff yesterday and confirmed that it is working. Haven't fixed IPSec VPN yet though.

                                          M 1 Reply Last reply Reply Quote 0
                                          • M
                                            MarcO42 @pete
                                            last edited by

                                            @pete
                                            To be clear: I reverted my changes in the /etc/inc/interfaces.inc to the code above and didn't use the monitoring funktion from System/Routing/Gateways and after a reconect I can see the the Gateway have now the correct entry. :)

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