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

    IPv6 LAN with Tracking interface problem

    Scheduled Pinned Locked Moved IPv6
    4 Posts 2 Posters 649 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.
    • S
      ssjoco85
      last edited by

      I set my pfsense WAN to DHCP6 and LAN to Tracking Interface. I truied everything but I can't get a public IPv6 on LAN neither any PC.
      DHCPv6 - Request only an IPv6 prefix Tick, Send IPv6 prefix hint Tick, Prefix /56. I enable IPv6 on the firewall.

      I also tried several other settings. I read every tutorial and forums what I find in the google. No luck.
      I have an IPv6 address on WAN side, I confirmed that my ISP should support DHCP PD with /56. Any idea?

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Interfaces > WAN

        In the DHCP6 Client Configuration section, check Debug. Save and Apply.

        Status > System Logs, DHCP

        Filter on process dhcp6c

        Post what is there.

        You probably want to re-title your post to list where you are and your ISP. Someone might have the secret recipe they want since calling the ISP is probably useless.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

          I read that someone did the same config and the IPv6 is working. I think he has the same ISP. First I tried his settings. My ISP is Telekom HU on GPON. They confirmed the 56 prefix and DHCP PD on their website.

          Here is my System logs
          May 1 10:28:27 dhcp6c 75307 send solicit to ff02::1:2%em1
          May 1 10:28:27 dhcp6c 75307 reset a timer on em1, state=SOLICIT, timeo=4, retrans=16326
          May 1 10:28:43 dhcp6c 75307 Sending Solicit
          May 1 10:28:43 dhcp6c 75307 set client ID (len 14)
          May 1 10:28:43 dhcp6c 75307 set elapsed time (len 2)
          May 1 10:28:43 dhcp6c 75307 set option request (len 4)
          May 1 10:28:43 dhcp6c 75307 set IA_PD prefix
          May 1 10:28:43 dhcp6c 75307 set IA_PD
          May 1 10:28:43 dhcp6c 75307 send solicit to ff02::1:2%em1
          May 1 10:28:43 dhcp6c 75307 reset a timer on em1, state=SOLICIT, timeo=5, retrans=31928
          May 1 10:29:15 dhcp6c 75307 Sending Solicit
          May 1 10:29:15 dhcp6c 75307 set client ID (len 14)
          May 1 10:29:15 dhcp6c 75307 set elapsed time (len 2)
          May 1 10:29:15 dhcp6c 75307 set option request (len 4)
          May 1 10:29:15 dhcp6c 75307 set IA_PD prefix
          May 1 10:29:15 dhcp6c 75307 set IA_PD

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            They are not responding.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

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