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

    IPv6 pfSense not working

    Scheduled Pinned Locked Moved IPv6
    12 Posts 7 Posters 3.2k 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.
    • P
      pra
      last edited by

      what test do you do(ping, traceroute,mtr , tcpdump ….)?
      if you don't tell more information pfsense team can't help you and nobody try to help you.
      a simple 'it is not working'  , is not enough

      pra

      1 Reply Last reply Reply Quote 0
      • P
        privatekey
        last edited by

        ipconfig:
        Verbindungsspezifisches DNS-Suffix:
        Verbindungslokale IPv6-Adresse  . : fe80::::****:6cf1%12
        IPv4-Adresse  . . . . . . . . . . : 192.168.1.254
        Subnetzmaske  . . . . . . . . . . : 255.255.255.0
        Standardgateway . . . . . . . . . : 192.168.1.1

        ping ipv6.google.com
        gives me this error:
        "Ping-Anforderung konnte Host "ipv6.google.com" nicht finden. Überprüfen Sie den
        Namen, und versuchen Sie es erneut."
        Ping-Request couldn't find host "ipv6.google.com. Check the name, and try again.

        tracert ipv6.google.com
        "Der Zielname ipv6.google.com konnte nicht aufgelöst werden."
        The destinationname ipv6.google.com could not be resolved.

        ping from pfSense to ipv6.google.com works by the way.
        It seems to be a problem with the client settings.

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan
          last edited by

          @privatekey:

          ping from pfSense to ipv6.google.com works by the way.

          This is problematic.

          ping ipv6.google.com
          

          will not give any results - no ping reply comes back. Because ipv6.google.com will not reply to IPv4 pings.

          This:

          ping6 ipv6.google.com
          

          will produce this:

          PING6(56=40+8+8 bytes) 2001:470:xxxx:xxxx::2 --> 2a00:1450:400c:c05::65
          16 bytes from 2a00:1450:400c:c05::65, icmp_seq=0 hlim=54 time=60.706 ms
          16 bytes from 2a00:1450:400c:c05::65, icmp_seq=1 hlim=54 time=57.140 ms
          16 bytes from 2a00:1450:400c:c05::65, icmp_seq=2 hlim=54 time=55.188 ms
          16 bytes from 2a00:1450:400c:c05::65, icmp_seq=3 hlim=54 time=52.768 ms
          ^C
          
          

          which means: it works.

          pfSense has an IPv6 connection to the net ?

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

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

            what IPv6 address is your client getting?  I only saw a fe80 address - link local, that is not going to work.

            clientipv6.png
            clientipv6.png_thumb

            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
            • MikeV7896M
              MikeV7896
              last edited by

              @Gertjan:

              ping ipv6.google.com
              

              will not give any results - no ping reply comes back. Because ipv6.google.com will not reply to IPv4 pings.

              This:

              ping6 ipv6.google.com
              

              will produce this:

              PING6(56=40+8+8 bytes) 2001:470:xxxx:xxxx::2 --> 2a00:1450:400c:c05::65
              16 bytes from 2a00:1450:400c:c05::65, icmp_seq=0 hlim=54 time=60.706 ms
              16 bytes from 2a00:1450:400c:c05::65, icmp_seq=1 hlim=54 time=57.140 ms
              16 bytes from 2a00:1450:400c:c05::65, icmp_seq=2 hlim=54 time=55.188 ms
              16 bytes from 2a00:1450:400c:c05::65, icmp_seq=3 hlim=54 time=52.768 ms
              ^C
              
              

              which means: it works.

              Under Windows - I'm assuming Windows since the OP provided ipconfig info - ping does both IPv4 and v6. To force v6, you use ping -6. But if it resolves an IPv6 address via DNS, it will still work, even if not forced.

              The S in IOT stands for Security

              1 Reply Last reply Reply Quote 0
              • H
                Halvsvenskeren
                last edited by

                Have you enabled IPv6 on the physical ESXi host running pfsense??

                Remember to reboot the host.

                ipv6.PNG
                ipv6.PNG_thumb

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

                  you do not have to enable ipv6 on esxi host vmkern to have devices talk ipv6.

                  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
                  • P
                    privatekey
                    last edited by

                    @virgiliomi:

                    @Gertjan:

                    ping ipv6.google.com
                    

                    will not give any results - no ping reply comes back. Because ipv6.google.com will not reply to IPv4 pings.

                    This:

                    ping6 ipv6.google.com
                    

                    will produce this:

                    PING6(56=40+8+8 bytes) 2001:470:xxxx:xxxx::2 --> 2a00:1450:400c:c05::65
                    16 bytes from 2a00:1450:400c:c05::65, icmp_seq=0 hlim=54 time=60.706 ms
                    16 bytes from 2a00:1450:400c:c05::65, icmp_seq=1 hlim=54 time=57.140 ms
                    16 bytes from 2a00:1450:400c:c05::65, icmp_seq=2 hlim=54 time=55.188 ms
                    16 bytes from 2a00:1450:400c:c05::65, icmp_seq=3 hlim=54 time=52.768 ms
                    ^C
                    
                    

                    which means: it works.

                    Under Windows - I'm assuming Windows since the OP provided ipconfig info - ping does both IPv4 and v6. To force v6, you use ping -6. But if it resolves an IPv6 address via DNS, it will still work, even if not forced.

                    ping -6 does not work with ipv6.google.com
                    It just works on the pfsense. What kind of settings do I have to enable to get "real" IPv6-Adresses on my clients.
                    DHCPv6? DHCPv6 Router Advertising settings? DHCPv6 Relay?

                    1 Reply Last reply Reply Quote 0
                    • H
                      hda
                      last edited by

                      @privatekey:

                      …
                      What kind of settings do I have to enable to get "real" IPv6-Adresses on my clients.

                      If you have ISP on WAN or do you have a MoDem inbetween ?, try Track Interface on your LAN (and RA(Unmanaged)/SLAAC for clients).

                      1 Reply Last reply Reply Quote 0
                      • P
                        privatekey
                        last edited by

                        I have a Modem in between.

                        This guy has exact the same problem..

                        https://forum.pfsense.org/index.php?topic=82220.0

                        I don't think that there is a solution..

                        1 Reply Last reply Reply Quote 0
                        • H
                          hda
                          last edited by

                          OK, you need a MoDem transparent (pass-tru/bridged to PPPoE) -OR- a MoDem-Router that can act as a DHCP6-Server (like the Fritz!Box 7360).

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