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

    Successful Install on Watchguard Firebox X700!

    Scheduled Pinned Locked Moved
    Hardware
    151
    690
    870.8k
    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.
    • H
      hlouie
      last edited by

      Now I got myself a WatchGuard x500 and would like to install m0n0 or pfsense.  I see some are using CF (Compact Flash), Microdrives in the CF slot, DOM (Disk on modules), IDE Hard Drive, IDE SSD (Solid State Drive).

      I want to start off with m0n0 because it a small load but I want to grow in to using pfsense and use the full complete load.  I've read somewhere CF have limited writeback due to the bandwidth so it uses a ramdisk.  Does this apply to the Microdrive in the CF slot?  I really don't want to use a IDE Hard Drive due to noise and heat.  In the IDE, I might use a DOM or SSD.

      Because I'm starting fresh with this new firewall, what is the best media to use so I expand in to?

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

        I've been running a full install (not embedded) on a 1GB Transcend DOM for nearly two years now without problems.

        I believe a microdrive is a magnetic drive. A Compact Flash card uses semiconductor storage. Not all microdrives work with FreeBSD - search the forums for more information.

        1 Reply Last reply Reply Quote 0
        • C
          coldfire
          last edited by

          Hi,
          I sell my Firebox X700 (currently under m0n0, cause of 128MB CF) with standard components and a 512MB SDRAM (not tested).
          I've only the box, screws, m0n0 CF and Watchguard CF (no CD, no license).

          For more information : hotfire.fraggeur@free.fr

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

            Was the watchdog timeout issue ever resolved? What about in the latest 2.0 BETA builds?

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

              Hi,

              I have installed Pfsense 1.2.3RC on a Firebos X1000, on a 40Gb 2.5" IDE drive, got the LCD display working and now have some across a time out.
              re1: watchdog timeout -  this occures almost instantnousely wen I try to access the web interface. :(
              Has any one sen this before and does any one have a resolution to it.
              This slows all connection right down.
              I putit into production and with in 2 day it shows up gain.

              I have added a Broadcom BCM4318KFB9 wireless card, but it is not seen by pfsense -  is ther any drivers for it?
              What card is the best to user?

              Does any one if the "Safenet" encrytption card is ued by pfsense -  i know it is pickup on boot.

              Thanks
              George ;D

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

                Hi,

                Made some changes and boot wiht "boot -v" option and now go this  (more details):
                re1: watchdog timeout
                t_delta 16.0218ab2579e66da0 too long

                Any ideas on how to resolve?

                Thanks
                George

                1 Reply Last reply Reply Quote 0
                • I
                  iFloris
                  last edited by

                  @gpapaiko, I think that t_delta might be connected to the harddrive rather than to the watchguard. I found this: http://old.nabble.com/Thinkpad-T23-60-second-stall-on-resuming-8.0-RELEASE-i386-td26765321.html which references the same timeout. Someone else also has the t_delta too long message on a completely different system here: http://kerneltrap.org/mailarchive/freebsd-current/2009/7/12/6182173.
                  Also, da0 is a bsd-reference for your harddrive.

                  one layer of information
                  removed

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

                    So I got my x700, which looks perfect!

                    However, as soon as I access the web interface, watchdog timeouts are thrown all over the place :(

                    Anyone have a fix? Does using the embedded kernel or full kernel make a difference? I'm using BETA 2.0 on the embedded kernel

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

                      Awesome! Also got a working FBX700 here now. Will look for a WLAN card and a 512MB PC133 RAM. Does anyone know how many Watts this baby consumes?

                      | apple fanboy | music lover | network and security specialist | in love with cisco systems |

                      1 Reply Last reply Reply Quote 0
                      • D
                        dsprague2
                        last edited by

                        OK, I am a total noob at this.
                        I have tried doing this as the instructions states but i must be doing something wrong.
                        Setup:
                        USB - Serial adapter (PL-2303 from Prolific)
                        Null modem cable (as per watchguard)
                        X700
                        Safenet m-PCI card
                        64 MB CF Card
                        2GB CF Card
                        Actiontec Wireless LAN 802MIP

                        What i have done….
                        I have flashed a new 2GB CF card with the current version of pfSense 2GB version.
                        put card into CF slot and turn on unit, goes through POST and then a blank LCD screen and Power is lit green and Arm/Disarm is red.
                        I then had the unit boot with no CF card and changed the baud setting to 9600 as some people say works. I have also tried the other 3 with no success. I have set it to 9600/8/n/1/hardware or none or xON xOFF, has not worked.
                        The terminal (tried Putty and Tera Term) sometimes displays a bunch of garble and doesnt stop and most of the time nothing.
                        I have also tried using m0n0wall with no success.
                        I have tried doing all this without the WLAN or SafeNet card.

                        I just cant seem to get anything to work and dont know what else to do.
                        If your wondering, Does It Work?. Yes it does i pulled it to get pfSense on it.

                        I need some help or need to know what i am doing wrong.

                        1 Reply Last reply Reply Quote 0
                        • I
                          iFloris
                          last edited by

                          @dsprague2 seems to me your pl-2303 isn't working right. Perhaps the cable has a defect or your drivers might be outdated or incompatible. I've had problems with that converter in the past, so I've opted for a keyspan (tripplite) connector instead: http://www.tripplite.com/en/products/model.cfm?txtSeriesID=518&EID=14862&txtModelID=3914
                          You could also try an older machine that still has a serial port to see if the null modem cable isn't the culprit.

                          Edit: typo

                          one layer of information
                          removed

                          1 Reply Last reply Reply Quote 0
                          • M
                            mrmyke
                            last edited by

                            Great news I just took a Xcore 700 out of service and now i have a use for it.  Did you get any feedback from others that may or may not have gotten anything going with the display or VPN cards???

                            Have you put this box to the test yet?

                            MrMyke

                            1 Reply Last reply Reply Quote 0
                            • D
                              dr.diesel
                              last edited by

                              @jlepthien:

                              Awesome! Also got a working FBX700 here now. Will look for a WLAN card and a 512MB PC133 RAM. Does anyone know how many Watts this baby consumes?

                              My Kill-A-Watt shows 35 watts with the stock fans and a 2G CF card.

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

                                I'm also running pfsense, but on the what would have been x500!

                                Shame the web interface dies crashes the box when trying to do stuff!

                                X500, 4GB CF, 256MB Ram, BE 24mbps Broadband!

                                1 Reply Last reply Reply Quote 0
                                • M
                                  MarkProvanP
                                  last edited by

                                  @teh

                                  In case you get confused, the x500, x700 and a higher x number all have identical hardware; Watchguard just charged more since they had a more 'advanced' software level in them (i.e. the x500 was intentionally software crippled).

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mericksonj
                                    last edited by

                                    All,

                                    I'm a long-time lurker here that just got this project off the ground.  Although I haven't yet tried the X700 I have in the basement.  I did a sucessfull install with a X5000 "peak" series firebox.

                                    512M ram, 2.8Ghz pentium 4 processor, 3 GigE ports, 7 FastE ports, USB, 4 gig CF (going to install microdrive when I get one), empty mini-PCI slot ready for your wireless NIC.

                                    Thank you all for your assistance, the "set hw.ata.ata_dma=0" from the boot line was a great tip!

                                    Now to go play :)

                                    –James

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

                                      FINALLY got mine up and running tonight.

                                      My 512Mb stick only registers as 256Mb dispite being the Kingston RAM recommended in this thread.

                                      I've pulled the 3 fans from the back and the super cyclone fan on the CPU sink and cut a 120mm hold located over the CPU, mounting a half height 120mm Scythe fan.

                                      All going well, might add a wifi card later, but I'm trying to get the LCD up and running, and struggling :-/

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        mericksonj
                                        last edited by

                                        @PistolPete:

                                        FINALLY got mine up and running tonight.

                                        My 512Mb stick only registers as 256Mb dispite being the Kingston RAM recommended in this thread.

                                        I've pulled the 3 fans from the back and the super cyclone fan on the CPU sink and cut a 120mm hold located over the CPU, mounting a half height 120mm Scythe fan.

                                        All going well, might add a wifi card later, but I'm trying to get the LCD up and running, and struggling :-/

                                        Don't install the LCDPROC package, but if you follow RidnHard19's instructions exactly from the first page of this forum: http://forum.pfsense.org/index.php/topic,7920.msg46356.html#msg46356 it will help until you get to the symlink part.

                                        You'll want to replace the diver with Jean's updated version also in that thread: http://forum.pfsense.org/index.php/topic,7920.msg105179.html#msg105179

                                        Then, to wrap it all up and make it work follow the instructions to create the symlinks to the updated libraries: ( in the same thread)  http://forum.pfsense.org/index.php/topic,7920.msg69315.html#msg69315

                                        You should then be able to start the LCDd script and view the results immediately on your  LCD panel.

                                        I just finished the install on my x700, a problem with a remote serial cable forwarded to a TCP socket(I was too lazy to bring it upstairs and use my known-good serial port/cable) made it harder than expected, but I managed, and was rewarded with CARP!

                                        Hope this helps!
                                        –James

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

                                          Thanks for the heads up - I'll go through those now and see where I get to before I quit for the night

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

                                            All working - a damn sight easier than I was expecting too!!!

                                            Plus, I'm in the web interface all the time and I've not seen a single watchdog timeout in the logs.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post