Special setup: Choose originating IP for PFSENSE own internal traffic



  • Hi,

    We have a very special setup to an MPLS cloud, i'll try to explain very short using faked IP's:

    <internet><-> <hq: 16="" 10.1.0.0="">// ROUTER: <10.1.0.254 INT, 10.3.0.254 PtP>  <–--HA FIBER ----> PFSENSE: <10.3.0.1 WAN, 10.2.0.254 LAN> // <lan: 16="" 10.2.0.0="">HQ: Has 10.1.x.x/16 network and gateway to internet
    OUR NET: We have 10.2.x.x/16 LAN network. We also have 3 OPT networks but that does not matter here i think.

    Important: We don't use any NAT !!

    PF SENSE WAN: The WAN connection is a PtP link using HA fiber to their router. That "router" PtP network uses 10.3.x.x/16

    So our PFS box uses 10.3.0.254 as default gateway and i can access everything from my internal 10.2 LAN, including Internet through their connection.

    Sadly it is not possible for them (don't ask me why) to route my PFS box WAN address 10.3.0.1 to the internet. So PFS itself can't access outside NTP servers, can't do ClamAV updates, can't install packages e.t.c.

    I am told to use a LAN or OPT source address for PFS own internal traffic as they are the only networks routed.

    Can i choose what source address / interface PFS uses for it's own outgoing traffic ?</lan:></hq:></internet>



  • @Foxi352:

    Can i choose what source address / interface PFS uses for it's own outgoing traffic ?

    You can use outbound NAT therefor. Firewall > NAT > Outbound

    By default it is set to "Automatic outbound NAT rule generation".  Check "Manual Outbound NAT rule generation" and click save.
    Then edit the rule
    WAN  127.0.0.0/8 * * * WAN address 1024:65535 NO Auto created rule for localhost to WAN 
    and change the Translation to LAN address.

    If the routing for LAN network works correctly pfSense should get its responds well this way.


Log in to reply