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

    WAN & VPN Tunnel, Incoming Traffic

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 352 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.
    • J
      JustConfused
      last edited by

      Hi,

      I am doing something wrong here - but I don't see it. Note that this is a testing setup

      Basic Network LAN: 192.168.49.0/24
      pfSense: 192.168.49.1
      WAN: PPoE on VLAN - working
      VPN: Wireguard Tunnel to AIrVPN - working.

      Client 192.168.49.21
      Gateway: 192.168.49.1
      Running: Telnet Server (HK-Telnet-Server). This is accessible locally
      Firewall is off

      VPN Provider is AirVPN
      Tunnel is up
      Port Forward Port: 63816 on Tunnel for this device only

      pfSense Rules etc (for specific case)
      NAT Rules
      Port Forward:
      02927ae2-7b06-4ea5-805c-45bbfe94df33-image.png
      Outbound
      df72a2d3-6ef6-4a8c-a137-3c66466d1d55-image.png
      Firewall Rules (WG_AirVPN)
      8a92bd78-fc84-44d9-aae3-29cf2faf0515-image.png
      Firewall Rules (LAN)
      da2818ff-e93c-4a46-b810-6cd82e4fb4d0-image.png
      No floating rules

      With the rules set as above - the AirVPN website shows the port as open
      Browsing from the Client (.21) shows the AirVPN Server IP Address - not the unencrypted ISP Address

      But I goto a remote PC elsewhere on the internet
      Telnet (VPN Address) and I get connect fail.
      [And my remote site has just had a powercut - sigh]

      I have something very similar working through the WAN Interface on another firewall - and it works. Its just not working here and I don't see why.

      J 1 Reply Last reply Reply Quote 0
      • J
        JustConfused @JustConfused
        last edited by JustConfused

        @justconfused
        And to reply to my own post

        Oh Shit - I am telnetting on the wrong bloody port.

        Note that this is a demonstration of how writing things down can help think things through - even when you are being an utter moron.

        I am certainly not going to admit just how long I have spent struggling with this (and a very similar related issue which is the reason for this test setup)

        Sigh

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