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

    Trouble configuring pfsense on AWS

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    1 Posts 1 Posters 927 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
      joshuamichaelsanders
      last edited by

      I'm having a tough time getting a pfsense firewall configured correctly on AWS. I have a public subnet and private subnet configured on AWS and have attached the interfaces (eth0 172.16.2.20 & eth1 172.16.4.20) as outlined in https://www.netgate.com/docs/aws-vpn-appliance/vpc-guide.html. I then threw up a generic Windows machine (ip address 172.16.4.244) on the private subnet so that I could test basic connectivity (ping and RDP). I can't ping the Windows box from the pfsense LAN interface let alone is port forwarding on the WAN interface letting me RDP from the Internet. If someone could walk me through the basic connectivity issues I think I'd be able to work out the Port Forwarding issue. It's just something I'm not seeing.

      Cheers!

      Edit
      Well I got the basic config down (helps if the change source/destination check if selected, oh and there is a default route for the subnet), but now for the life of me I can't get the port forward for RDP configured. I have a throw away windows 2008 server running on my private subnet at 172.16.4.126 that I've verified I can now ping. I have a port forward NAT redirect in place that is

      INT      Prot  Src  Src    Dest. Addr      Dest. Ports            NAT IP                NAT Ports
                          Addr Pt
      WAN > TCP > * > * > WAN address > 3389 (MS RDP) > 172.16.4.126 > 3389 (MS RDP)

      It then automatically created the appropriate rule as well. When I go to check if the port is open though it's a no go. I guess it's possible the Windows instance isn't running RDP. I did just install it quickly from the AWS marketplace.

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