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

    MPLS Routing

    Routing and Multi WAN
    3
    20
    1.8k
    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.
    • R
      rustydusty1717 @michmoor
      last edited by

      @michmoor we obviously don't need the IPsec tunnel once I can get the routes established. Does that change anything?

      R 1 Reply Last reply Reply Quote 0
      • R
        rustydusty1717 @rustydusty1717
        last edited by

        @rustydusty1717 I was hoping to disable the IPsec after hours and test routing things over the MPLS. Once I can verify everything functions the IPsec won't be needed anymore.

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

          @rustydusty1717 if you disable IPsec how will you connect to the remote side? I assume you have some sort of cutover plan.
          In any event, if there is only one path then static routing will be all you need

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

          R 1 Reply Last reply Reply Quote 0
          • R
            rustydusty1717 @michmoor
            last edited by

            @michmoor whats the best way to setup the static routes? Haven't had to do them before in pfsense.

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

              @rustydusty1717
              https://docs.netgate.com/pfsense/en/latest/routing/static.html#static-routes

              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
              • R
                rustydusty1717
                last edited by

                So I've added 192.168.60.0/24 (LAN on other side) to the static routes, disabled the IPSec tunnel and not able to reach across the MPLS. Do I also need to add static routes for the MPLS networks on both sides as well?

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

                  @rustydusty1717 So you created a gateway as well? Can you ping across the MPLS - from pfsense to pfsense?

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

                  R 1 Reply Last reply Reply Quote 0
                  • R
                    rustydusty1717 @michmoor
                    last edited by

                    @michmoor correct I have my WAN gateway and then OPT as the 2nd gateway for the MPLS. I can ping the MPLS on the other end. Just can't reach anything on the LAN on other side. Wondering if my static routes are wrong or if I need to do anything with outbound NAT.

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

                      @rustydusty1717
                      Do you have firewall rules that state that your LAN can reach the network 192.168.60.0/24? What do those rules look like

                      Are you gateways UP?
                      Can you ping from your pfsense ? So log in to your pfsense via ssh. From the CLI initate a ping. so ping 192.168.60.1 [if thats an address on the other side[

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

                      R 1 Reply Last reply Reply Quote 0
                      • R
                        rustydusty1717 @michmoor
                        last edited by

                        @michmoor can ping the MPLS gateway on the other end however not the firewall or LAN on other end. It's not a pfsense/netgate unfortunately.

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

                          @rustydusty1717 Does the MPLS side have a route back?

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

                          R 1 Reply Last reply Reply Quote 0
                          • R
                            rustydusty1717 @michmoor
                            last edited by

                            @michmoor yes it does. Should outbound NAT be turned off?

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

                              @rustydusty1717 Whatever you are NATting to, the other side must know how to get back to that IP.
                              If this is a site 2 site link generally NAT wouldnt be needed but depends on your design.

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

                              R 1 Reply Last reply Reply Quote 0
                              • R
                                rustydusty1717 @michmoor
                                last edited by

                                @michmoor said in MPLS Routing:

                                If this is a site 2 site link generally NAT wouldn't be needed but depends on your design.

                                So we are able to now reach each LAN on both sides but any remote site (OpenVPN site to site) can't reach the LAN MPLS on other side.

                                What's weird is using the old IPsec instead of MPLS it all works fine. The OpenVPN site to site's already have the LAN of the other side of the MPLS. Besides doing static routing at my primary site for the LAN on other side of MPLS it should all work, no?

                                Doing tracert from a remote site on my side hits the OpenVPN assigned tunnel network then fails. Revert back tp IPsec and routing works perfect.

                                R 1 Reply Last reply Reply Quote 0
                                • R
                                  rustydusty1717 @rustydusty1717
                                  last edited by

                                  @rustydusty1717 anyone have any ideas? Would a diagram help?

                                  DerelictD 1 Reply Last reply Reply Quote 0
                                  • DerelictD
                                    Derelict LAYER 8 Netgate @rustydusty1717
                                    last edited by Derelict

                                    @rustydusty1717 Accurate, comprehensive, numbered diagrams always help.

                                    Chattanooga, Tennessee, USA
                                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

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