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

    XG7100-1U Multiple WAN to Multiple LAN

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    13 Posts 4 Posters 1.5k Views 4 Watching
    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.
    • S Offline
      SenseiNYC @Rico
      last edited by

      @Rico We've watched the video a number of times and while it seems informative, its not instructional on various configuration options.

      1 Reply Last reply Reply Quote 0
      • S Offline
        SenseiNYC @stephenw10
        last edited by

        @stephenw10 Thank you I believe this will need to be our course of action.

        1 Reply Last reply Reply Quote 0
        • M Offline
          madapter
          last edited by

          If you have something like a white paper or FAQ on how to do this type of configuration, I'd be interested in it as well. The switch port is presenting some challenges here as well, almost looks like we should have ordered the the PCIe network card at this point.

          1 Reply Last reply Reply Quote 0
          • stephenw10S Offline
            stephenw10 Netgate Administrator
            last edited by

            If you're configuring from scratch I'd first restore this config that will configure the switch and VLANs in pfSense to have all the ports separately assigned. Then you can treat them like individual interfaces.

            If you have existing VLANs things get more complex but as I said above if you open a ticket with us we can help you with that. We've done lots of these conversions with numerous different configurations.

            Steve

            7100-8-port-config.xml

            1 Reply Last reply Reply Quote 0
            • S Offline
              SenseiNYC
              last edited by

              Hi @stephenw10 thank you again for helping with this the other day. I am sorry to bother but I have a question based on your prior assistance.

              Eth1 4081 - WAN1
              Eth2 4082 - LAN1
              Eth3 4083 - WAN2
              Eth6 4086 - LAN2
              Eth7 4087 - WAN3
              Eth8 4088 - LAN3

              Now I want to have each LAN # route outbound using the corresponding WAN # (eg; LAN1 to WAN1, LAN2 to WAN2, LAN3 to WAN3). I was able to get the config to the point where it's usable for our needs with regards to IPSEC tunnels and all, but as each WAN is a different ISP and each LAN is a different VLAN tag on the switches (the LAN ports are ACCESS to the switches ports where the switches then carry the traffic internally over the tagged VLAN's).

              Is the best way to route the LAN's to the appropriate WAN's to use rules (eg; Rule - LAN1 / Rule - LAN2 , etc) or is there a better way to do this?

              Thanks again.

              1 Reply Last reply Reply Quote 0
              • stephenw10S Offline
                stephenw10 Netgate Administrator
                last edited by

                Yes, use policy routing rules on the incoming LAN interfaces to route traffic via the correct gateway.

                You may want to add rules above that on each interface to allow traffic to the pfSense DNS and NTP services on the LAN interface itself if they are using that.

                Steve

                1 Reply Last reply Reply Quote 0
                • S Offline
                  SenseiNYC
                  last edited by SenseiNYC

                  Here is what I have so far, not sure if this was done correctly. Showing in order of work performed:

                  Interface Assignments

                  Switch Ports

                  0Switch port VLANs

                  LAN_Corporate (Main LAN) Rules

                  LAN_POS Rules

                  LAN_Guest Rules

                  Gateway Groups

                  Thanks again.

                  1 Reply Last reply Reply Quote 0
                  • S Offline
                    SenseiNYC
                    last edited by SenseiNYC

                    And to be clear, we do not yet know if it is working, we wish to go live next week and are hoping to get the configuration correct from the start.

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S Offline
                      stephenw10 Netgate Administrator
                      last edited by

                      Yeah that looks OK but you will probably want rules above those policy routing rules to allow clients there to access DNS and NTP on the firewall. Otherwise all traffic matched by the policy rule will be forced to leave via the gateway group including dns and ntp. You might also want a rule to prevent devices access the GUI on the WAN IP.
                      Something like:

                      Selection_611.png

                      Steve

                      1 Reply Last reply Reply Quote 1
                      • S Offline
                        SenseiNYC
                        last edited by

                        @stephenw10 you really are awesome! that is exactly what i did yesterday. Thank you so much!

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