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

    Where/How to post Procedure for setting up Dual Wan for current Snapshot?

    Routing and Multi WAN
    6
    32
    11.5k
    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.
    • P
      Pootle
      last edited by

      @Vescovo:

      Why don't you add it to the DOC example.

      Like this?  http://doc.pfsense.org/index.php/Multi-Wan/Load-Balancing

      btw its from a visio diagram, if anyone wants the visio file, I'm happy to send it…

      1 Reply Last reply Reply Quote 0
      • V
        Vescovo
        last edited by

        Hi Pootle,  :-[ Unfortunately, I was not specific enough.
        In the pfSense Box where you have Gateway 192.168.0.1 it should read 192.168.0.254
        In the pfSense Box where you have Gateway 192.168.2.1 it should read 192.168.2.254

        At the edge of the pfSense box where you have 192.168.0.254 it should read 192.168.0.2
        At the edge of the pfSense box where you have 192.168.2.254 it should read 192.168.2.2

        At the entrance to the modem/ routers where you have 192.168.0.2 it should read 192.168.0.254
        At the entrance to the modem/ routers where you have 192.168.2.2 it should read 192.168.2.254

        To insert the image "in-line" where you thought it would be most helpful you click the image ikon in the menu. It will put code in that looks like this [[Image:Example.jpg]].
        You then preview the document. Go to the link where you place the example.jpg. You will not see the image. Click the link. It will take you to a page where you can download the image. Name the image something sensible. Once you save the image it appears where you want it.

        To deteremine the location, ask yourself where the image would be most helpful to you in building the pfsense box if you were doing it for the first time.

        Thanks very much for contibuting. :D

        1 Reply Last reply Reply Quote 0
        • P
          Pootle
          last edited by

          Ah! I see.  That explains why I got confused reading the guide  :D

          I've uploaded a new version, can you check it's now got the right addresses?  If OK, then I'll look at editing the page.

          1 Reply Last reply Reply Quote 0
          • V
            Vescovo
            last edited by

            It is perfect! ;D It will be interesting to see how you position it. It is good to get new views. This always improves the documentation.

            1 Reply Last reply Reply Quote 0
            • L
              lampie
              last edited by

              I also contributed to the documentation. Added the FTP workaround for multiwan and a little cosmetics :)

              '''''FTP WORKAROUND'''''

              If you want to connect to a FTP server you need to add this workaround to your LAN tab.

              Proto      Source        Port        Destination        Port        Gateway
              TCP        LAN net      *          127.0.0.1          1 - 65535  *

              Now the packets are forwarded correctly and you can connect to an FTP server.

              '''''pORT FORWARDING'''''

              1 Reply Last reply Reply Quote 0
              • V
                Vescovo
                last edited by

                Hey Pootle, you positioning was great. The image was just put in line. It is a little tricky to do it but it worth it to show your image! The image will make it easier for the next person. ;D

                Hi Lampie, thanks for you additon.  :)  I know it is hard to add stuff to the DOCO and make it look good! Unfortunately, I did not get a chance to fully test FTP.  My outgoing FTP(passive) has worked with the default rules.  Is the workaround is for Inbound or oubound FTP?  Why is that rule superior to the default LAN -> Wan1 rule in the Firewalls:Rules image?

                1 Reply Last reply Reply Quote 0
                • P
                  Pootle
                  last edited by

                  OK, that's good.  I wasn't sure if it was better to link to the picture or put it in line, but you're right, it works well in line.

                  Just thinking of doing a short note on running in a VM….

                  1 Reply Last reply Reply Quote 0
                  • L
                    lampie
                    last edited by

                    @Vescovo:

                    Hey Pootle, you positioning was great. The image was just put in line. It is a little tricky to do it but it worth it to show your image! The image will make it easier for the next person. ;D

                    Hi Lampie, thanks for you additon.  :)  I know it is hard to add stuff to the DOCO and make it look good! Unfortunately, I did not get a chance to fully test FTP.  My outgoing FTP(passive) has worked with the default rules.  Is the workaround is for Inbound or oubound FTP?  Why is that rule superior to the default LAN -> Wan1 rule in the Firewalls:Rules image?

                    For active FTP connections (not passive) i needed this rule to make it work. Inbound i still have to test, but that is working out of the box i guess. Without this rule i simply cant make any connection (active) to a FTP server.

                    What i also noticed is that rebooting the system makes after you add these LAN rules is the best option. I had some problems with not correctly forwarding ports to a designated IP adress. After a reboot this worked fine.

                    1 Reply Last reply Reply Quote 0
                    • V
                      Vescovo
                      last edited by

                      Thanks Lampie, I have also noticed that a reboot after filter changes appears to always make things work that may not have worked before. I will check out your comments later this week.

                      1 Reply Last reply Reply Quote 0
                      • S
                        sullrich
                        last edited by

                        Update to  the latest snapshot.  There are bits in place to make sure check_reload_status is always running now.

                        1 Reply Last reply Reply Quote 0
                        • P
                          Pootle
                          last edited by

                          Dunno if you spotted it yet Vescovo, but I've amended the document page on multi wan to put in proper wikiheaders so you get a content list at the front - makes it easier to find the bit you want….

                          1 Reply Last reply Reply Quote 0
                          • V
                            Vescovo
                            last edited by

                            No I did not. :-[ Let me try it. The change page did not point it out to me. Sounds great. :)
                            I like it. Many, many thanks. ;D Your doco on the Vitual Machine vesion of pfSense is very good.

                            1 Reply Last reply Reply Quote 0
                            • K
                              krull
                              last edited by

                              @Vescovo:

                              Hey Pootle, that's an excellent diagram. Why don't you add it to the DOC example. The only difference is the DOC sets the the WAN1(192.168.0.2) and WAN2(192.168.2.2) and The modem/routers to 192.168.0.254 and 192.168.2.254. If you can make those changes it will be consistent with the rest of the DOC.

                              Hey all,

                              I apologize for diggin up ole posts, but I got a slightly 'on topic' query that needs attention:

                              Looking through the doc.pfsense.org wiki page for LoadBalancing, the modem/routers are stated to have none-routable IPs on them as stated above by Vescovo. What if they were on bridge mode with Static IPs on? Would setting up the Pfsense WAN ports to the designated Static IPs work as good as it is set on the Wiki? (Thus eliminating the need for three consecutive local net to only your LAN Network…)

                              I have a setup based on the wiki's Howto following word by word but substituting the Static IP Addresses instead and I get online connectivity just fine, but for some reason my portforwards are not working and I suspect that it has something to do with the bridge mode of the ADSL modems.

                              Please advice. Thanks a bunch.

                              1 Reply Last reply Reply Quote 0
                              • P
                                Pootle
                                last edited by

                                It should work as you say, and as long as your WAN / WAN2 subnets and addresses are set up OK, it should all work OK.

                                I did try setting my linksys am200 into bridge mode but could not even persuade it to connect, so I gave up and let it NAT

                                Sounds like you have outgoing access working, but are just having trouble with incoming port forwarding.  I use port forwarding in my config OK, but haven't used it with modems in bridge mode.

                                1 Reply Last reply Reply Quote 0
                                • K
                                  krull
                                  last edited by

                                  Thanks Pootle for the reply. Since the Port forwarding section of the LoadBalancing wiki page just states to do the normal Portforwards, I see no problems with the rules I set (Port 80 to internal IP system for example…). I am going to do a run down of it once more (3rd time install...) with a clean slate install of pfsense to see if I miss anything.

                                  My goal here is to somehow contribute to the docs as well once everything's working on my setup. Superb work so far with the docs guys! Thanks a bunch.

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