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

How to enable ICMP ping response on WAN/OPT1 interfaces

Scheduled Pinned Locked Moved Firewalling
12 Posts 2 Posters 121.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.
  • Y
    yazzgoth
    last edited by Aug 26, 2006, 9:39 AM

    Hi,

    This is my first post here so be gentle  ::)
    I've tried to search for this on the forums and googled a bit for it but didn't manage to find anything, sorry :-\

    Can anyone help me out? How can I enable ICMP ping on WAN/OPT1 interfaces (two WANs with load balancing). I need it to debug some issues.

    Thanks

    1 Reply Last reply Reply Quote 0
    • H
      hoba
      last edited by Aug 26, 2006, 1:33 PM

      Create a pass rule at these interfaces for protocol ICMP, source any, destination "WAN-IP-Adress" / "OPT1-IP-Adress" (depending on the interface you create that rule on).

      1 Reply Last reply Reply Quote 0
      • Y
        yazzgoth
        last edited by Aug 26, 2006, 2:44 PM

        I've tried that  ::) without luck… any other ideas?

        Where does it states in the configuration of the firewall that the ICMP is being blocked?

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by Aug 26, 2006, 8:15 PM

          status>systemnlogs, tab firewall. If you see blocks there click the small icon in front of the line. It will tell you which rule caused the block. If you don't see anything there and the ping doesn't work either there is something in front of you that causes the blocks I guess.

          1 Reply Last reply Reply Quote 0
          • Y
            yazzgoth
            last edited by Aug 27, 2006, 8:57 AM

            I've got a popup msg with:

            The rule that triggered this action is:
            
            @69 block drop in log quick all label "Default block all just to be sure."
            
            
            1 Reply Last reply Reply Quote 0
            • H
              hoba
              last edited by Aug 27, 2006, 10:03 AM

              Then your rule is not correct. This is the invisible last rule that blocks everything that is not explicitly allowed.

              1 Reply Last reply Reply Quote 0
              • Y
                yazzgoth
                last edited by Aug 27, 2006, 10:57 AM

                Any way to manually disable/alter that default rule? (ie. from command line)
                It's really an easy setup - there are two WAN interfaces (WAN and OPT1) with outgoing load balancing, I can access the web gui remotly on any of the two interfaces(I've forwarded the ports for that). But the ICMP rule doesn't seem to work. I've tried many diffrent approaches, on both interfaces and still the firewall is blocking every ICMP requests I send.

                1 Reply Last reply Reply Quote 0
                • H
                  hoba
                  last edited by Aug 27, 2006, 1:52 PM

                  Show me the rules. Btw, you don't need to forward a port to open up webgui access at WAN. You only need a firewall rule to permit traffic on that port.

                  1 Reply Last reply Reply Quote 0
                  • Y
                    yazzgoth
                    last edited by Aug 27, 2006, 10:31 PM

                    Action: Pass
                    Interface: WAN2 (OPT1)
                    Protocol: ICMP
                    ICMP Type: any
                    Source: any
                    Destination: {WAN2IP}
                    State type: Keep state
                    Gateway: {WAN2Gateway}

                    As for the webgui port - I know, but I want to keep it on a diffrent port on the external interfaces.

                    1 Reply Last reply Reply Quote 1
                    • H
                      hoba
                      last edited by Aug 27, 2006, 10:42 PM

                      drop the gateway in that rule and make it default. This is not a rule for outgoing traffic and shouldn't have a gateway set.

                      1 Reply Last reply Reply Quote 0
                      • Y
                        yazzgoth
                        last edited by Aug 27, 2006, 11:13 PM

                        I've tried that as well….

                        I'm really stuck with that one.
                        It's running RC1 if that's any good.

                        1 Reply Last reply Reply Quote 0
                        • H
                          hoba
                          last edited by Aug 27, 2006, 11:32 PM

                          upgrade to the latest version. the rule is correct if you set the gateway to default.

                          1 Reply Last reply Reply Quote 0
                          12 out of 12
                          • First post
                            12/12
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                            This community forum collects and processes your personal information.
                            consent.not_received