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

    IPv6 Address assignments for internal devices

    Scheduled Pinned Locked Moved IPv6
    11 Posts 4 Posters 1.5k 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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator
      last edited by johnpoz

      If your isp provided you a prefix delegation, And you configured RA then yeah its possible that any device that are ipv6 capable could get and use Ipv6.

      If your isp does not provide you with a delegated than prefix then enabled track on your lan side interface is not going to do anything.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.11 | Lab VMs 2.8, 24.11

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

        Thank you, I appreciate your reply, and on a holiday weekend, too. The only place I see RA listed is in IPv6 ICMP, which I had enabled by a WAN rule after reading that ICMP was required for IPv6, but I did not enable RA. My ISP is Comcast and does support IPv6. pfSense does show an IPv6 address on the WAN interface. My WAN config is default (DHCP/DHCP6), no other changes. Please advise if this is completely wrong. Sorry to bother if these are completely elementary questions...
        fd2f78c5-d12c-4a4b-bf3b-cf50595ce771-image.png

        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
        • johnpozJ
          johnpoz LAYER 8 Global Moderator
          last edited by johnpoz

          If your not getting a ipv6 on wan then there is nothing "track"

          You do not need to enable anything on wan for IPv6 to work..

          Does your lan actually get an IPv6 address via track - again not really possible if your wan didn't get 1..

          RA would be enabled on LAN interface..

          RAs.png

          To be honest - if you don't understand anything about IPv6 I would be curious to why you want to enable it even.. Is there something you believe you need IPv6 for? Other than learning experience?

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.8, 24.11

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

            I think maybe you misunderstood me. I do get an IPv6 WAN address and LAN, guessing due to "Track Interface", right?
            6d4fbc9a-6871-4946-a8ad-f7d2b7a74846-image.png
            And my devices do as well.
            0bfef6f6-be60-49c4-a327-decc3f44fc1d-image.png
            But LAN DHCPv6 server is disabled, LAN RA set to Unmanaged (Default, never been in there). So I'm wondering how these addresses get assigned w/o a DHCPv6 server on LAN. Yes, and learning. Like I said, if these questions are too elemental, blow me off.

            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)

            JKnottJ 1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator
              last edited by johnpoz

              IPv6 does NOT require a dhcpv6 server.. That is what RA do..

              IPv6 is quite different than how IPv4 works to be honest.. It way more than just a longer address ;)

              Your not showing a global IPv6 address there - that is a link local address, your clients will not be able to access internet ipv6 unless it gets a global IPv6 address.. Those that start with your 2601:xxx..x.x.x.x.x.xx

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

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

                OK, that explains a lot. It's sort of like a 169.x.x.x then?

                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
                • johnpozJ
                  johnpoz LAYER 8 Global Moderator
                  last edited by johnpoz

                  Yeah its kind of like 169.254.x.x in the ipv4 world - but not exactly ;) But sure close enough for the comparison to be correct

                  While you can use 169.254, its not a requirement in ipv4 - while in ipv6, link-local is required and all devices will have them and use them.

                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                  If you get confused: Listen to the Music Play
                  Please don't Chat/PM me for help, unless mod related
                  SG-4860 24.11 | Lab VMs 2.8, 24.11

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

                    Got it, thanks. Answers my original q. Thanks again.

                    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
                    • JKnottJ
                      JKnott @provels
                      last edited by

                      @provels said in IPv6 Address assignments for internal devices:

                      But LAN DHCPv6 server is disabled, LAN RA set to Unmanaged (Default, never been in there). So I'm wondering how these addresses get assigned w/o a DHCPv6 server on LAN. Yes, and learning. Like I said, if these questions are too elemental, blow me off.

                      That's entirely normal with IPv6. The router advertisements provide the network prefix and the device provides it's own suffix, based on the MAC address or a random number.

                      PfSense running on Qotom mini PC
                      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                      UniFi AC-Lite access point

                      I haven't lost my mind. It's around here...somewhere...

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

                        See Also: SLAAC

                        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.