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

    Dual Wan, Portforward not working on OPT-Wan

    Scheduled Pinned Locked Moved Routing and Multi WAN
    31 Posts 5 Posters 17.8k 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.
    • R
      rob_v
      last edited by

      I tested it with:

      WAN 1 static

      WAN 2 static

      And with :

      WAN 1 DHCP

      WAN 2 static

      Thx :)

      1 Reply Last reply Reply Quote 0
      • T
        tec
        last edited by

        I am also now on Release 1:

        • Portforwarding on Opt-Wan not working
          -deleted my static port entries but not effect

        Now backed up config XML
        -deleted all advanced outbound rules and enabled ipsec passthrough, and deleted "oubound tags" in config.xml installed again Pfsense, restored config.xml, did the normal reboot and it doesn´t even work work without having toutbound Nat enabled :-(

        Still the same, the Firewall Rule is showed as above in the firewall log page but nothing happens

        Right now I have the feeling that Dual Wan and Portforwarding is a mess or I am to stupid for this and just how it seems the latter is more likely

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by

          I have several locations where I'm using portforwards on multiwan setups (at WAN and OPT-WAN) without any issues. You really seem to have something wrong. I suggest starting over and not reusing the old config.

          1 Reply Last reply Reply Quote 0
          • T
            tec
            last edited by

            Hoba, do you have on any location PPPOE as a Wan Interface?

            1 Reply Last reply Reply Quote 0
            • H
              hoba
              last edited by

              uhm, no. Static everywhere. Maybe that makes a difference. Can you send me /tmp/rules.debug and your config.xml to holger dot bauer at citec-ag dot de?

              Btw, how did you make PPPoE work at OPT-WAN  ???

              1 Reply Last reply Reply Quote 0
              • T
                tec
                last edited by

                Hi Hoba,
                there maybe some Kind of missunderstanding:
                Wan (the normal PFsensenstandartwan) = Pppoe
                Opt-Wan (Optional Interfaces with static ips or they get them per DHCP).

                Therefore I asked if in any of your Setups you have the normal WAN as a PPPoe Connection?

                1 Reply Last reply Reply Quote 0
                • H
                  hoba
                  last edited by

                  PPPoE at WAN shouldn't affect portforwards at OPT-WAN.

                  1 Reply Last reply Reply Quote 0
                  • T
                    tec
                    last edited by

                    Shouldn´t….
                    I noticed only on an old install that when I plugged the cable of from the PPPOE Connection and rebooted the Portforwards where working on Opt-Wan this is the weird thing.

                    On your Opt-Wans. Do they have all Ip from an ISP ? I have on my Opt-Wan a 192.168.0.0/24 Adress because I need that a DSL Modemroute makes the PPPOE connection or is this a Problem that I am using a private Ip range on the OPT_Wan Interface?
                    Regards

                    I will install the next day from Scratch and make Babysteps, maybe I ca find exactly out at which Point the Problem lies.

                    Should I still mail you the requested files?

                    1 Reply Last reply Reply Quote 0
                    • J
                      jeroen234
                      last edited by

                      did you uncheck this option on the opt interface ?

                      Block private networks
                      When set, this option blocks traffic from IP addresses that are reserved for private
                      networks as per RFC 1918 (10/8, 172.16/12, 192.168/16) as well as loopback addresses
                      (127/8). You should generally leave this option turned on, unless your WAN network
                      lies in such a private address space, too.

                      1 Reply Last reply Reply Quote 0
                      • H
                        hoba
                        last edited by

                        Yes, please send me the files. Maybe something obvious pops up by viewing them.

                        1 Reply Last reply Reply Quote 0
                        • R
                          rob_v
                          last edited by

                          Hi,

                          Is it possible to make a (simple) config file what works with 2 WAN's (port forwarding RDP or HTTP or FTP)
                          It doesn't matter what for IP your use in this config file.
                          I want to compare this config file with my own settings maybe i missed something?

                          Thank you.

                          Kind regards
                          Rob

                          1 Reply Last reply Reply Quote 0
                          • T
                            tec
                            last edited by

                            Hi back at home,
                            so jeroen234 on the Opt-Interfaces there is no Checkbox

                            hoba: I disconnected the Cable from WAN rebooted and then
                            the Forwards worked on OPT-WAN. The config with the normal NAT Setuo and also the Config with Advanced Outbound Nat enabled.

                            rob_V could you also test you Setup if you disconnect the cable from WAN  and pos tyour results, only to verify if this could be the bug

                            Cheers

                            1 Reply Last reply Reply Quote 0
                            • R
                              rob_v
                              last edited by

                              @tec:

                              Hi back at home,
                              so jeroen234 on the Opt-Interfaces there is no Checkbox

                              hoba: I disconnected the Cable from WAN rebooted and then
                              the Forwards worked on OPT-WAN. The config with the normal NAT Setuo and also the Config with Advanced Outbound Nat enabled.

                              rob_V could you also test you Setup if you disconnect the cable from WAN  and pos tyour results, only to verify if this could be the bug

                              Cheers

                              I tryed that without any positive result..
                              After this experiment i switched the networkcards to another pci slot.
                              But pfsense can't handle this action :P (get everytime watch dog failures).
                              So i have to install pfsense again….  I think i gonna buy a hardware router RV042 from linksys i'm tyred about pfsense soz..
                              It looks good and i think it will works fine but on my system....

                              Thanks, maybe i will use pfsense when i'm in a good mood..

                              Or.... Sombody gots a configfile what works with 2 wans and 2x RDP connection from wan to lan and opt to lan?
                              That's the only thing wat i want to try..

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

                                i have similiar problem.
                                i have
                                WAN (STATIC)
                                LAN (STATIC)
                                OPT1 (STATIC)
                                OPT2 (STATIC)
                                WAN2 (STATIC)

                                everything is working through WAN but i can not even ping default gateway or any IP on WAN2 in my WAN2 network (/24). I did tcpdump on WAN2 NIC and see that packets are going in or out. But WAN2 never answers on ARP requests.

                                19:40:57.062126 arp who-has ...103 tell ...96

                                WAN2 status is up. I did reboot pfsense a few times but still no luck.
                                Any suggestions?

                                (pfsense 1.0-RELEASE)

                                –
                                S

                                1 Reply Last reply Reply Quote 0
                                • H
                                  hoba
                                  last edited by

                                  Make sure your WAN2 settings are correct. Maybe there is a typo somewhere? Do you see any traffic from the pfSense at all? Maybe you need a crossovercable?

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

                                    my connection on WAN2 is like that:

                                    DSL_Modem
                                                |
                                          | switch |

                                    WAN2|      | server with ..*.96 IP
                                    with …103

                                    i run tcpdump on 96 and 103.
                                    if i ping from ...96 to ...103 IP i see on both servers (96 and pfsense) arp request from
                                    96 "who has ....103 IP". pfsense doesn't answer.
                                    if i ping from ...103 to ...96 IP i see on both servers ICMP packet from 103 is going to 96.
                                    96 is trying aswer on and an sends ARP request "who has ....103 IP" which pfsense sees but never answers.

                                    wierd... may be it is happening because i did install 1.0-RC3 and upgraded to 1.0-Release...
                                    i'll try to do fresh install from 1.0.1-CD

                                    –
                                    S

                                    1 Reply Last reply Reply Quote 0
                                    • H
                                      hoba
                                      last edited by

                                      Yes, try a fresh install please.

                                      1 Reply Last reply Reply Quote 0
                                      • T
                                        tec
                                        last edited by

                                        Hi Hoba,
                                        I send you my config Files did you find an obvious error?

                                        I am now on 1.0.1 and I can still confirm this strange error, that all of my forwardings on Opt-Wan are working when i plugg the cable from the Wan (Pppoe) Interface off and reboot the machine with a disconnecte WAN.

                                        Maybe this could Help: I tried to connect to my FTP Server trough Opt-Wan. This Setup was working when the Pppoe_Wan Interface had no connectivity because the cables was pulled. I got the following logs in my Filezilla-Server-Log:
                                        (000002) 11/2/2006 13:31:31 PM - (not logged in) (84.58.147.51)> Connected, sending welcome message…
                                        (000002) 11/2/2006 13:31:31 PM - (not logged in) (84.58.147.51)> 220-FileZilla Server version 0.9.19 beta
                                        (000002) 11/2/2006 13:31:31 PM - (not logged in) (84.58.147.51)> could not send reply, disconnected.

                                        The interesting thin is, that I don't receive the welcoming message on my client. But in my Firewall log, the incoming connection is markes a succesfully passed. To me this seems, that something in the "NAT-department" is not working how it should.

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

                                          about my problem with second WAN.
                                          i did fresh install - didnt' help. So i've tried
                                          it as LAN NIC and ….....
                                          it turned out that NIC card was broken.
                                          i've never seen such strange problem before but
                                          i'm happy that everyhing is working now.

                                          –
                                          S

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            tec
                                            last edited by

                                            Hi,
                                            I finally had time to Change my Wan Interface from PPPOE to a static Ip with a Modem router in front of it. After the change I rebooted. An now Portforwards are working with Advanced Outbound NAT on the OPT-WAN Interfaces and Policy Based routing.
                                            From my point of view there seems something not real working if you use PPPOE on the WAN interface, maybe the developers could take a look into it.
                                            Regards

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