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

    Can ping IPv6 on PfSense but not on the work station

    Scheduled Pinned Locked Moved IPv6
    9 Posts 5 Posters 7.1k 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.
    • F
      Frozen_Fire
      last edited by

      I just installed the recent IPv6 version and followed the instruction. The gateways are online, IPv6 DNSlookup is working on PfSense. But when I do ping6 on my workstation, all is timed out.
                I have two IPv6 accounts on the WAN side and put another account on the LAN side
                'don't have firewall installed on the workstation
      *The application supplied by the ISP is working, but always disconnecting (5 min on, 30 sec off) ^_^

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

        " I have two IPv6 accounts on the WAN side and put another account on the LAN side"

        what?

        And what IPv6 address is your workstation getting? Or did you give it, what routes do you have on the client?

        I can tell you that ipv6 works freaking AWESOME on pfsense and the free hurricane electric tunnel.. Takes like 10 minutes to setup.

        From a workstation on lan side of pfsense
        C:\Windows\System32>ping ipv6.google.com

        Pinging ipv6.l.google.com [2001:4860:8001::69] with 32 bytes of data:
        Reply from 2001:4860:8001::69: time=96ms
        Reply from 2001:4860:8001::69: time=72ms
        Reply from 2001:4860:8001::69: time=64ms
        Reply from 2001:4860:8001::69: time=65ms

        Ping statistics for 2001:4860:8001::69:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
            Minimum = 64ms, Maximum = 96ms, Average = 74ms

        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
        • F
          Frozen_Fire
          last edited by

          Please help me setup this in pfSense:

          Os: Windows XP 3

          Tunnel broker: GogoClient {IPv6-in-UDP-IPv4 Tunnel [Nat traversal]}

          Local address: 2001:0fd8–----:000b / 56
                              124.6.135.36

          Remote address: 2001:0fd8--------:000a

          How do I setup the firewall rules and what IPv6 to enter on the lan side?

          thanks for the help...^_^

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

            Just use he tunnel, there is a complete walk through how to set it up on pfsense here.

            http://iserv.nl/files/pfsense/ipv6/

            That gogo client would be a tunnel through your pfsense, endpoint on your box your running the client on..  Lame way to do it since you can just endpoint the tunnel on your pfsense box.  No need for any client software, etc.  The above link walks you through setting it up on hurricane electrics FREE tunnel they will give you.  And you can even get a /48 if you want to router multiple /64's etc.

            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
            • I
              ipv6kid
              last edited by

              You need to add a route to Global IPv6 IP addresses in "Routes"… instructions here: http://forum.pfsense.org/index.php/topic,40527.0.html

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

                No he doesn't – see my response to your other topic..  You should already have a default route there is no need to add a route for 2000:: /3

                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
                • I
                  ipv6kid
                  last edited by

                  I did exactly as the guides said – no default route was setup and I've been trying to get IPv6 for the past few months (through several different 2.0+ versions) , not once did it setup a default route for me.

                  It's something to try if nothing else is working: His problem is exactly like mine was.

                  1 Reply Last reply Reply Quote 0
                  • a-a-ronA
                    a-a-ron
                    last edited by

                    It looks like there are a couple bugs right now that are stopping IPv6 from working properly….

                    Check near the bottom

                    http://forum.pfsense.org/index.php/topic,40377.0.html

                    1 Reply Last reply Reply Quote 0
                    • D
                      databeestje
                      last edited by

                      that one should be fixed right about now, was introduced when I added link local gateways support (which is completely valid).

                      The gogo client is not supported yet. It's on the todo list for dynamic tunnels.
                      Jim added a HE.net dyndns type that will fixup the tunnel IP for you if you change WAN address. The Sixxs tunnel obviously can't do that.

                      The gogo client is a nice way to completely autoconfigure the entire machine, but that doesn't fit well with the rest of the pfSense mechanics.

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