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

    Cannot ping opt1 interface or router connected to opt1 (wan2) interface from lan

    Scheduled Pinned Locked Moved Routing and Multi WAN
    34 Posts 4 Posters 13.0k 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.
    • G
      glanc
      last edited by

      This is my loadbalancer config:

      loadbalancer.JPG
      loadbalancer.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • G
        glanc
        last edited by

        ::)…. any suggestions?? Or do i better reset to defaults: rules, nat and loadbalancer and see if i resolve and start over the config step by step?

        Thanks.

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

          Disable the manual advanced outbound nat and set it to automatic again. Retest. Does it work now?

          1 Reply Last reply Reply Quote 0
          • G
            glanc
            last edited by

            tried… :-\ but no ping.... is aon worse than using automatic?

            If tracerouting opt1 pfsense int from lan, give me back wan gateway as this:

            C:>tracert -d 10.0.0.9

            Rilevazione instradamento verso 10.0.0.9 su un massimo di 30 punti di passaggio

            1    <1 ms    <1 ms    <1 ms  85.35.156.x    -----> this is default gateway on pfsense wan int
              2  85.35.141.x  rapporti: Rete di destinazione non raggiungibile. (Network unreachable)
                    |
                    |--> This is next op router

            Rilevazione completata.

            does it mean that it is trying to find a reply from opt1 going out to internet, instead of just replying from its internal int?

            .... ???

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

              It means that for some reason it skips your first new created firewallrule. Don't know why though. Maybe reboot.

              1 Reply Last reply Reply Quote 0
              • G
                glanc
                last edited by

                already rebooted….what other factor can lead to such a problem? only loadbalancing or i've to check also other configurations such trafficshaping (but i don't think so) anyway just to be sure!

                do you think that if i remove loadbalancing and failover conf i'll solve the issue? Thanks.

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

                  Only firewallrules and outbound nat can cause problems here. You don't have any static routes configured, right?

                  1 Reply Last reply Reply Quote 0
                  • G
                    glanc
                    last edited by

                    no static routes. do you need more info on my conf? i can provide you with all the settings? I have the same problem on another pfsense 1.2 box also with dual wan. Everything works fine, but i cannot ping opt1 int from lan nor router attached to that interface. What can be the problem  :-\

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

                      Try to rebuild the config step by step and see where it breaks. I guess that'S the easiest way to find the issue atm.

                      1 Reply Last reply Reply Quote 0
                      • G
                        glanc
                        last edited by

                        ok thanks a lot, I'll post the result if i succeed!

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

                          Yes, I'm interested to see where the problem is as well  :)

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

                            You could try with my setup.

                            mine.JPG
                            mine.JPG_thumb

                            /Perry
                            doc.pfsense.org

                            1 Reply Last reply Reply Quote 0
                            • G
                              glanc
                              last edited by

                              you mean the localnet entry?

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

                                No.  What ip address i you trying from?

                                lanrules2.JPG
                                lanrules2.JPG_thumb

                                /Perry
                                doc.pfsense.org

                                1 Reply Last reply Reply Quote 0
                                • G
                                  glanc
                                  last edited by

                                  i'm trying to ping from internal server 192.168.100.10/24 to pfsense op1 (wan2) interface 10.0.0.10 or router behind it 10.0.0.9 but do not ping. Those rules you mention, was there to let both internal server not being restricted by the last rule "blockall". Do you mean that those rules are blocking pings?

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

                                    Yes if you first 192.168.100.10 rules has the gateway * or 10.0.0.9 it should work imo.

                                    /Perry
                                    doc.pfsense.org

                                    1 Reply Last reply Reply Quote 0
                                    • G
                                      glanc
                                      last edited by

                                      !!SOLVED!! Perry found the problem! ;) The rules under LAN that i put to let 192.168.100.10 go out without being filtered by the last rule, had the gateway not to default one but specified to use opt1 default gateway, so when pinging from lan from that ip, it didn't look at the defaut routing tables causing the problem! Thanks a lot Perry. I suppose that the other rule to let the same internal host go out via opt1 using opt1 default gw is ok. Because i so not want to filter that host when going out from opt1.

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

                                        ;)

                                        Rules:
                                        Rules are processed from top to down.
                                        If a rule catches the rest of the rules is no longer considered.
                                        Per default a "block all" rule is always in place (invisible below your own rules).

                                        Traffic is filtered on the Interface on which traffic comes in.
                                        So traffic comming in on the LAN-Interface will only be processed from the rules you define on the LAN tab.

                                        If you have a private subnet on your WAN: uncheck the "Block private networks" checkbox on your WAN-config page.

                                        http://forum.pfsense.org/index.php/topic,7001.0.html

                                        /Perry
                                        doc.pfsense.org

                                        1 Reply Last reply Reply Quote 0
                                        • G
                                          glanc
                                          last edited by

                                          Ok, But putting a rule on top with default gw * using an alias with all local net, as hoba suggested, didn't work. Why? Now i'm trying to connect from internet to lan servers using opt2(wan2) interface and i've some problem. I've an openssh server on a host, and i can connect from internet using wan, but it fails using opt1. i can see in the log that the connections arrive at pfsense, that is portforwarded correctly and that the rule on opt1 with logging turned on, is activated but the connectio faild. Probably the connection fails to come back!

                                          1 Reply Last reply Reply Quote 0
                                          • G
                                            glanc
                                            last edited by

                                            This are the relevant part of my config:

                                            I'm tryng to connecto via ssh to the firewall itself (not an internal host as stated in the previous post) using opt1 from internet. Via wan it already works. Maybe it is not possible since pfsense use the default gateway of wan as its gateway?  ::)

                                            log1.JPG
                                            log1.JPG_thumb
                                            portforward.JPG
                                            portforward.JPG_thumb
                                            rule.JPG
                                            rule.JPG_thumb
                                            lanrules.JPG
                                            lanrules.JPG_thumb

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