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

    Watchguard Help

    Scheduled Pinned Locked Moved Hardware
    25 Posts 5 Posters 5.1k 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.
    • chpalmerC Offline
      chpalmer
      last edited by

      You will like the XTM5 better anyhow.  :)

      Triggering snowflakes one by one..
      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

        I won't disagree there. The XTM5 is much nicer. Of course you could have bought our hardware… ;)

        It could be an entirely coincidental hardware failure but it seems unlikely. Very strange. I would not expect it to boot into the BIOS if it was a failure.  :-\

        Steve

        1 Reply Last reply Reply Quote 0
        • U Offline
          uknownme123
          last edited by

          This looks like the x-core-e? Which is the same motherboard in X550e, X750e and X1250e? If you see it boot and then stuck, most likely the baud rate has changed during boot. As I recall freedos uses a different buad rate (9600) from the default bios buad rate (115200). Have you tried changing buad rate on your viewing computer after booting. Also when freedos has completed loading, it should make two beeps.

          I had a couple of these x750e and I remember Watchguard's default buad rate is 115200 (same as pfSense) this would allow you to see the bios boot and then see pfsense boot. freedos baud rate is 9600. So you change to 9600 and you'll need to press "Enter" key multiple times to get the freedos console.

          I think there is a feature, when you reboot the unit too many times it'll default to baud rate of 9600 for a one time boot. It'll work at this buad rate until you reboot. This allows idiots like me to at least see the system boot once, and then see freedos prompt. Believe me, I had my fair share of experience with the x-core-e series.  Also note that these primitive console com were buggy and sometimes you get weird characters even when you are on the correct buad rate, make sure you have good ground on your serial connection and hit "Enter" key multiple times.

          I think your motherboard is working. Once you get freedos prompt showing, move on to getting pfSense on the CF card.

          1 Reply Last reply Reply Quote 0
          • U Offline
            uknownme123
            last edited by

            Yah, I remember now. So when I had the v81 bios flashed and freeDos on compact flash. I would keep my computer com baud rate at 9600 and boot it watchguard unit. I wouldn't see the bios boot, but after a while hit "enter" key a couple of time and the freeDos prompt appears.

            Once I had pfSense on a compact flash. I keep my computer com baud rate at 115200 and I could see bios boot then pfSense boot.

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

              Hmm, it's been a long time since I did this… definitely worth trying. I would have expected to still hear the three beeps when freedos boots even if you don't see a console but I have a vague memory about that not happening.

              Steve

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