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

    No outbound on LAN / AWS

    Scheduled Pinned Locked Moved NAT
    1 Posts 1 Posters 202 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.
    • M
      mikesec
      last edited by

      Good Evening,
      I have just setup Pfsense Plus (not sure of my support ID to create a netgate based ticket)

      Its a fairly simple setup (except the AWS Part)

      <= Internet GW <= PfSense external interface = Pfsense Internal interface <= Server

      So far i thought i had it working nicely.

      I have openVPN server running, and my machine is connecting to PfSense, allowing me to SSH to the server.
      I have openVPN client working (stopped) to test i could connect back to our previous hosting provider

      Route table for external configured
      PfSense can reach the internet, download some packages and confirmed with Ping, also the fact i can VPN into Pfsense and ssh into the server

      My Server however cannot gain external access, nor can it even do a DNS lookup using PfSense as the server
      It has a custom route table so its default route is the PfSense internal interface, the routing is correct on the server

      I have disabled Source/destination check on all 3 interfaces (2 x pfsense + 1 Server)

      The firewall seems to see the requests but states show;

      all udp 10.1.0.5:60067 -> 8.8.4.4:53 NO_TRAFFIC:SINGLE 1 / 0 62 B / 0 B
      all udp 10.1.0.5:54613 -> 8.8.4.4:53 NO_TRAFFIC:SINGLE 1 / 0 62 B / 0 B
      all tcp 10.1.0.5:35594 -> 8.8.4.4:53 CLOSED:SYN_SENT 7 / 0 424 B / 0 B
      LAN udp 10.1.0.5:59480 -> 10.1.0.14:53 SINGLE:MULTIPLE 1 / 1 62 B / 40 B
      LAN udp 10.1.0.5:60512 -> 10.1.0.14:53 SINGLE:MULTIPLE 1 / 1 62 B / 40 B
      LAN udp 10.1.0.5:56402 -> 10.1.0.14:53 SINGLE:MULTIPLE 1 / 1 62 B / 40 B
      LAN udp 10.1.0.5:55881 -> 10.1.0.14:53 SINGLE:MULTIPLE 1 / 1 62 B / 40 B
      all tcp 10.1.0.5:55216 -> 8.8.4.4:53 CLOSED:SYN_SENT 2 / 0 124 B / 0 B

      Any advise on where to look next?

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