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

    I'm not config NAT on WireGuard link?

    Scheduled Pinned Locked Moved NAT
    1 Posts 1 Posters 343 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.
    • 이
      이종훈
      last edited by 이종훈

      Topology
      "Client <-> pf1(tun_wg0) <-> pf2(tun_wg0) <-> Server(192.168.2.10)"

      • Client : 192.168.55.23
      • tun_wg0 : 10.50.3.3
      • tun_wg0 : 10.50.3.2
      • Server : 192.168.2.10

      On those topology, I try to ping to 192.168.2.10, result with tcpdump below;

      • Client
        7f5bc613-3e09-434d-8db1-69d4ae7c2bd3-image.png
      • pf1
        ee1e4cd3-6dac-4060-9896-39c3fee9b558-image.png
      • pf2
        da9ae2d8-504d-45e3-89ae-38fb9b852fef-image.png
      • server
        31e13653-53f7-4014-af52-4fd297b6cf92-image.png
        Its symptom like NAT behavior.
        However, I never config NAT on WG link.

      I am attaching dump file.
      textdump.tar.0
      Can someone help me to understand or reporting bug to developer.

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