Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    TNSR (22.06) as a multi-domain MAP-T BR

    Scheduled Pinned Locked Moved TNSR
    2 Posts 2 Posters 2.8k Views 2 Watching
    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.
    • D Offline
      dgeist
      last edited by

      Greetings, all. We're working with NG support on the same, but I thought I'd throw this out of the community.

      We're employing TNSR as the Border Relay in a dev MAP-T environment. Each MAP domain represents an edge router (Cable-CMTS, PON-OLT, etc.) We'd like to be able to use one (or a very small number of) DMRs (the synthetic IPv6 /64 to which customer edge devices send their translated IPv4 traffic).

      Currently, we can define multiple MAP domains with the same DMR and no errors are thrown, however only the last domain listed in the CLI appears to function properly (others are rejected with ICMPv6:
      baeee322-7a03-49d2-9b3d-c9fbc28b4475-image.png

      We believe the math involved should allow for this, but are unsure if there's a gap in the underlying VPP code to account for it, or possibly just a missed use case in the Clixon UI. Any pointers on where to dig into the logic on this (in VPP, Clixon, or both)?

      Dan

      fractal_boyF 1 Reply Last reply Reply Quote 1
      • fractal_boyF Offline
        fractal_boy @dgeist
        last edited by

        @dgeist there is a bug on TNSR that prevents to learn neighbor mac while you have map enabled on the interface. The workaround is to configure static neighbor entry.

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