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

    LAN to WAN IPv6 dropping packets intermittently

    Scheduled Pinned Locked Moved IPv6
    ipv6ping
    2 Posts 2 Posters 772 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.
    • C
      cbassett1000
      last edited by

      I have a /60 tracked interface on LAN. Devices are getting IPv6 addresses as needed and IPv6 works, BUT not as well as IPv4 since IPv6 is having packet issues. This is where I need help resolving the issue.

      pfSense (2.4.4 release p2) has an IPv4+6 ip address for each interface (WAN & LAN)
      LAN clients have IPv4+6 addresses (IPv6 addresses are public IPv6 addresses as well as having a link-local)
      [From here down I will be talking about IPv6. IPv4 does not suffer from the following problem(all is well)]
      Note:
      LAN to LAN pings (and packets) from any client to any client (pfSense or not) will NOT drop or have transmission issues
      WAN to WAN (pfSense WAN IPv6 address to ex: ipv6.google.com) pings and packets will NOT drop or have transmission issues
      LAN to WAN (Even pfSense LAN public IPv6 address) to ipv6.google.com WILL drop pings and have transmission issues.

      TL;DR LAN to WAN IPv6 dropping packets (Approx 30% loss). WAN to WAN and LAN to LAN are fine.

      Any solutions?

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

        How about LAN to the IPv6 address on the pfSense WAN interface?

        How about LAN to the very next IPv6 hop outside the WAN?

        Packet capture on WAN. If the echo requests are being sent but no reply is being received, there's nothing pfSense can do about it. Complain to the ISP.

        It is very possible they could have something different configured (perhaps unintentionally) for the interface address/prefix and the routed, delegated /60 prefix.

        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.