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

    2 WAN interface & Outbound on non default Gateway

    Scheduled Pinned Locked Moved NAT
    1 Posts 1 Posters 708 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
      Bullz3y3
      last edited by

      Hi,

      I'm having this weird problem with pfSense outbound NATting.

      My Current setup is I have 2 WAN interface.

      WAN1 198… -------
      WAN2 108... ------- DMZ1
                                    DMZ2
                                    GREEN1
                                    GREEN2

      I've configured manual outbound nat and internet works fine.
      DMZ1 and GREEN1 are going through Default GW (WAN1)
      DMZ2 and GREEN2 are set to go through WAN2 GW in firewall rules

      Traceroute
      When I do traceroute from any zones it goes through WAN2 IP address even though it's not default.

      Tracepath from a DMZ1 host

      [root@dns1 /]# tracepath google.com
      1:  10.10.10.12 (10.10.10.12)                              0.078ms pmtu 1500
      1:  10.10.10.1 (10.10.10.1)                                0.265ms
      1:  10.10.10.1 (10.10.10.1)                                0.132ms
      2:  108.170.x.x (108.170.x.x)                              2.100ms
      3:  10.220.23.1 (10.220.23.1)                              4.435ms
      4:  eth15-1.bb1.phx0.0.170.108.in-addr.arpa (108.170.0.10)  2.067ms
      5:  vl300.bb1.ash0.239.38.64.in-addr.arpa (64.38.239.1)  61.090ms

      Tracepath from a DMZ2 host

      [root@dns2 /]# tracepath google.com
      1:  10.10.20.3 (10.10.20.3)                                0.063ms pmtu 1500
      1:  108.170.x.x (108.170.x.x)                              2.073ms asymm  2
      1:  108.170.x.1 (108.170.x.x)                              2.070ms asymm  2
      2:  10.220.22.1 (10.220.22.1)                              1.926ms asymm  3
      3:  eth15-2.bb1.phx0.0.170.108.in-addr.arpa (108.170.0.30)  2.166ms asymm  4
      4:  10.140.2.17 (10.140.2.17)                              2.127ms
      5:  xe-10-3-1.bar2.Phoenix1.Level3.net (4.28.82.17)        2.435ms
      6:  ae-3-80.edge5.LosAngeles1.Level3.net (4.69.144.139)  11.604ms asymm  7
      7:  ae-2-70.edge5.LosAngeles1.Level3.net (4.69.144.75)    11.646ms

      If you notice DMZ2 which goes through WAN2 is fine but there are asymm records. which is not shown in DMZ1 traceroute.

      Problem 1 - DMZ1 is not going through Default WAN GW (198…)
      Problem 2 - asymm on DMZ2 traceroute

      Would be great if you could help me to resolve this :)

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