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

    Watchguard X550e no WAN?

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 3 Posters 2.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
      redflag237
      last edited by

      Hi,

      I've set up a Fireboix X550e with pfsense 2.0.2 - 2G i386 nanobsd.
      Box comes up, Webinterface can be accessed.

      WAN Link is up, IP 192.168.0.252/24, GW 192.168.0.11
      LAN Link is up, IP 192.168.1.1/24, DHCP etc. running.

      My PC on LAN get's an IP from DHCP, but there es no traffic routed to WAN Port. Gateway on Client points to 192.168.1.1, DNS points to the same Address.
      Checkbox Routing to private networks is set.

      The Update or List Packages Functionality from Web Interface returns No Connection Error.

      Does anybody have an idea, what's going wrong here? Maybe Hardware failure?

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        Your pfSense WAN interface has static IP? You haven't set a gateway?

        Please post the output of pfSense shell command```
        netstat -n -r

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

          @wallabybob:

          Your pfSense WAN interface has static IP? You haven't set a gateway?

          Please post the output of pfSense shell command```
          netstat -n -r

          I will look ip up later, because i'm currently not at home.
          IP is static, Gateway is set correctly.

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

            What is 192.168.0.11?
            Do you still have the VPN routing problem you describe here, and have you done anything that might have affected routing to try and solve it?

            Steve

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

              @stephenw10:

              What is 192.168.0.11?
              Do you still have the VPN routing problem you describe here, and have you done anything that might have affected routing to try and solve it?

              Steve

              Hi,

              The IP is the ISP Router.
              Routing Problem is a differene Machine, but still not solved.
              ~~edit

              I can Ping the WAN Port IP 192.168.0.252 of the Firebox from LAN, but *.11 is still not responding.

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

                Ok, can you ping 192.168.0.11 from the pfSense box? Either form the webgui Diagnostics: Ping: or from the CLI. Is your router normally pingable? Can you ping anywhere else from the pfSense box?

                It's possible that your router is not responding to pings, for whatever reason. In that case pfSense will see the WAN connection as down and stop routing packets over it. In that situation you would see WAN marked as down in the dashboard though.

                Steve

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

                  @stephenw10:

                  Ok, can you ping 192.168.0.11 from the pfSense box? Either form the webgui Diagnostics: Ping: or from the CLI. Is your router normally pingable? Can you ping anywhere else from the pfSense box?

                  It's possible that your router is not responding to pings, for whatever reason. In that case pfSense will see the WAN connection as down and stop routing packets over it. In that situation you would see WAN marked as down in the dashboard though.

                  Steve

                  I can ping *.11 if i plug my laptop into router network, yes. I cannot ping my Router by pfsense using cli.
                  router is normally pingable.

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

                    How is the pfSense WAN address (192.168.0.252) assigned? Static? DHCP?

                    @redflag237:

                    Checkbox Routing to private networks is set.

                    I assume you mean it is set to allow traffic from private networks?

                    Steve

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

                      @stephenw10:

                      How is the pfSense WAN address (192.168.0.252) assigned? Static? DHCP?

                      @redflag237:

                      Checkbox Routing to private networks is set.

                      I assume you mean it is set to allow traffic from private networks?

                      Steve

                      Yes, private and bogon traffic is allowed.
                      Maybe i found the Problem (but no solution).
                      First i tried to change the WAN Nic, still no Connection.
                      Second i tried to change from static ip to dhcp. No Response - if is always up, but IP 0.0.0.0. What can i do?

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

                        So it's not receiving an IP on WAN.
                        Check the logs to see if it is sending a dhcp request. Check the logs in the ISP router to see if that is seeing and responding to the request.
                        Given that it didn't work with WAN set as static it's probably something more fundamental. It could have failed to negotiate the ethernet connection correctly. Could be a bad cable.
                        Does the router have link lights on it? What are they saying about the connection speed and duplex?
                        Please post the output of ifconfig here, that should show any problems.

                        Steve

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