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

    Problems with IPv6 Routing from LAN to WAN in datacenter with own IPv6 /64

    IPv6
    3
    4
    1.1k
    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.
    • K
      kor86
      last edited by

      Hey,
      maybe someone could help me:

      I have a quarter rackspace in a datacenter with IPv4 and IPv6.
      IPv4 is working great with virtual IPs and 1:1 NAT for the Servers behind the PFSense Router.

      My problem is how to connect from LAN to WAN.
      I have a /64 IPv6 net with a Gateway on lets say 2001:xxxx:yyyy:zzzz::1
      The WAN interface is connected via own WAN IP 2001:xxxx:yyyy:zzzz::2 (static ipv6)

      Now i can ping google ipv6.google.com with no problems via diagnostic and ping via WAN interface.

      Problem is the LAN interface and the servers connected to it. IPv4 is working stable without problems.
      IPv6 is not.  The LAN interface has the IPv6 adress 2001:xxx:yyy💤1111::1
      But how can I connect from LAN to WAN? Normaly i will set the Server IP that is behind pfsense like  2001:xxx:yyy💤1111::1000 and Gateway to 2001:xxx:yyy💤1111::1
      but theres no connection / route to the WAN interface and the internet…

      Anyone could help me please?

      DHCPv6 on WAN interface does not work and thus no track interface is working on lan side.

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

        As has been pointed out today elsewhere: you need at least a /63 from your ISP to make one LAN behind a WAN.

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

          Get a /48 routed to your interface address from the datacenter.

          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
          • K
            kor86
            last edited by

            Thank you so much, it's working now :-)

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