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

    Can't get Dual Stack *quite* running

    Scheduled Pinned Locked Moved IPv6
    7 Posts 3 Posters 4.8k 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.
    • N
      Nutterpc
      last edited by

      Well I got the issue sorted of my LAN receiving IPV6 Addresses, my WAN connection got its /64 allocation from the ISP

      I have the gateway up, but for some strange reason, when I go to http://test-ipv6.com , it still tells me that ipv6 is not enabled

      I've created the rules as well to allow ipv6 traffic out, but for some strange reason I cant get it to work

      Anyone got any ideas please for what I am missing?

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

        Well, there is a lot of missing info. Like, are you routing from one range to another?
        What happens when you trace route to 2001:4860:4860::8888 from the firewall and from a system behind the firewall?

        Details on you setup will only help here.

        1 Reply Last reply Reply Quote 0
        • N
          Nutterpc
          last edited by

          Routing only from the internal /56 the ISP supplied me (2001:44b8:22b:b100)

          I've got it successfully showing up as assigning addresses out via DHCP

          Here's what happens when I try to tracert the afore mentioned address

          Tracing route to google-public-dns-a.google.com [2001:4860:4860::8888]
          over a maximum of 30 hops:

          1  Destination host unreachable.

          Trace complete.

          I have the Firewall rules set to allow traffic, LAN auto added them when I did a factory reset

          I also added one via WAN to allow, should I set it to allow all ipv6 data from lan?

          Let me know what other info you need

          EDIT: Attached shows that the necessary ipv6 addresses are there

          pfsense.png
          pfsense.png_thumb
          pfsense2.png
          pfsense2.png_thumb
          pfsense3.png
          pfsense3.png_thumb
          pfsense4.png
          pfsense4.png_thumb
          pfsense5.png
          pfsense5.png_thumb

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

            What is intresting is that fe80 addresses are not internet routable.

            from  http://en.wikipedia.org/wiki/Link-local_address :

            Link-local addresses for IPv4 are defined in the address block 169.254.0.0/16. In IPv6, they are assigned with the fe80::/64 prefix.

            If they are routing that block to you, it is not going to be on that gateway. Perhaps they are expecting you to route on another IP? I would think that the gateway is somehow wrong since any router will not pass a link local address.

            Your WAN is assigned an address from dhcp, so you are probably going to have to talk to your ISP. All the ones I have dealt with so far all use static IP and not from a dhcp, so I might be wrong.

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

              Your gateway can be a link local address. There is no harm in specifiying the gateway as a link local or global address since it is the same host.

              It makes perfect sense for gateways since these are normally always directly connected.

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

                @databeestje:

                Your gateway can be a link local address. There is no harm in specifiying the gateway as a link local or global address since it is the same host.

                It makes perfect sense for gateways since these are normally always directly connected.

                thanks for the clarification.

                1 Reply Last reply Reply Quote 0
                • N
                  Nutterpc
                  last edited by

                  Turns out there is a device or two on the network here that wont work with ipv6, so I've had to turn off the ipv6 stuff for now :(

                  Mainly the FetchTV box and the printer, the moment both IPV4 & IPV6 are being advertised, those 2 devices stop working

                  All good, without ipv6 running now, the network is running rather nicely

                  Im rather liking the uptime :D

                  Screenshot.png
                  Screenshot.png_thumb

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