Navigation

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

    AWS Routing/NAT oddity?

    General pfSense Questions
    2
    5
    605
    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.
    • A
      arthurbrownleeiv last edited by

      So I have a Netgate community instance running for a client of mine in AWS in a VPC.

      The instances behind the pfsense, can route their traffic through pfsense just fine for internet/IPSEC access.

      pfSense itself, can be reached over the IPSEC interfaces fine.

      However, I cannot download any packages, or update pfsense from either the GUI or the CLI.

      So I dug a bit deeper.

      I can ping from the CLI without issue on pfsense (say to the L3 DNS server 4.2.2.2). I can also ping via DNS to Google without issue.

      However, doing a traceroute to 4.2.2.2 results in: traceroute: findsaddr: failed to connect to peer for src addr selection.

      If I do a traceroute and specify the WAN connection with -i, the traceroute works as normal.

      I've scoured the UI, and I can't figure out where I'm missing anything. So I'm open for all sorts of advice. Never really had to ask for this kind of help since starting with 1.2 years ago :)

      Thanks guys!

      1 Reply Last reply Reply Quote 0
      • A
        arthurbrownleeiv last edited by

        Anyone have an idea?

        1 Reply Last reply Reply Quote 0
        • D
          DanC last edited by

          Check your AWS security rules.  You're probably blocking outbound traffic with their firewall, assuming pfSense is setup correctly.

          1 Reply Last reply Reply Quote 0
          • A
            arthurbrownleeiv last edited by

            It's all open, and wouldn't that then make it so specifying the interface for a traceroute fail as well?

            Like I said, IPSEC works fine, I can get to the webgui fine, ping works fine, the devices behind the pfsense instance are fine, just pfsense itself for some reason is having issues.

            It's like it is ignoring it's own routing table?

            1 Reply Last reply Reply Quote 0
            • A
              arthurbrownleeiv last edited by

              Is there anywhere else to specify a "default gateway" for the internals of pfSense?

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Products

              • Platform Overview
              • TNSR
              • pfSense
              • Appliances

              Services

              • Training
              • Professional Services

              Support

              • Subscription Plans
              • Contact Support
              • Product Lifecycle
              • Documentation

              News

              • Media Coverage
              • Press
              • Events

              Resources

              • Blog
              • FAQ
              • Find a Partner
              • Resource Library
              • Security Information

              Company

              • About Us
              • Careers
              • Partners
              • Contact Us
              • Legal
              Our Mission

              We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

              Subscribe to our Newsletter

              Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

              © 2021 Rubicon Communications, LLC | Privacy Policy