Source interface for management traffic
-
Hi,
We are in need of a separate interface from where I should source the traffic from. Some of our services are located in AWS and it only allows 169 non-routable addresses as tunnel addresses that attach firewall. Hence, all traffic that is generated from the FW to consume cloud-located services is failing. Usually, in these situations, Lo0 interface is used and some non-127 address can be assigned to it. Any ideas on how we can get around this?
Regards
-
@Blade1024 Not really following here.
You have a tunnel (IPsec or GRE) to AWS. You need to have all traffic that leaves pfsense, SNAT, to a 169.x.x.x address ? Why cant you SNAT it?
Or id imagine you create an IP Alias with the interface set to Localhost. Put in your 169 address there. Apply that to an outbound NAT rule (SNAT).