AWS Routing/NAT oddity?
-
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!
-
Anyone have an idea?
-
Check your AWS security rules. You're probably blocking outbound traffic with their firewall, assuming pfSense is setup correctly.
-
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?
-
Is there anywhere else to specify a "default gateway" for the internals of pfSense?
