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

    Source interface for management traffic

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 2 Posters 395 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.
    • B
      Blade1024
      last edited by

      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

      M 1 Reply Last reply Reply Quote 0
      • M
        michmoor LAYER 8 Rebel Alliance @Blade1024
        last edited by michmoor

        @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).

        Firewall: NetGate,Palo Alto-VM,Juniper SRX
        Routing: Juniper, Arista, Cisco
        Switching: Juniper, Arista, Cisco
        Wireless: Unifi, Aruba IAP
        JNCIP,CCNP Enterprise

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