Route subnet through other (non pfsense) gateway



  • Hi.
    I have this, pretty obviously non-working, setup, described in attachment.
    My task - allow servers to talk to each other, without adding static routes to 192.168.132.0/24 through pfSense on every server in 192.168.0.0/24 subnet.
    Any ideas?

    Yes, I can add an interface to ISA on .132.0 subnet, and adding sloppy-state workaround I can make TCP work from .100.0 to .132.0,
    but not the other way (from .132.0 to .100.0). Also I really want to leave pfsense as default router for .132.0 network.

    (yeah, @johnpoz, ISA would be decomissioned ASAP, but till that…)



  • Rebel Alliance Global Moderator

    Connect your ISA to pfsense via a transit vs the asymmetrical mess you currently have..  ISA then routes to pfsense via its transit, pfsense will send the traffic back to isa vs direct since it won't have an interface directly on that 192.168.100 network..




  • I must have an IP on pfSense in .100.0 network. If I didn't needed it, I would be posting this mess here.


  • Rebel Alliance Global Moderator

    No you do not need it.. Why do you need it?  If your going to put pfsense on that network, and the clients use a different gateway to get to get to other networks then that network becomes a transit.. Hosts on transit networks that need to use multiple gateways to get to other networks need to have host routing.. To tell them which gateway to use, if not then you end up with asymmetrical routing..

    Why can pfsense not use the new transit network you create from the isa router to pfsense to get to the 192.168.100 network.

    If you want to run it the way your running it then you will have to create routes on every host in the 192.168.100 telling them which gateway to use - or you have asymmetrical mess.