Watchguard XTM 5 Series
-
As recommended on this page-
sprechen Sie Deutsch?
http://www.triebwerk23.de/joomla/index.php/firewalls/watchguard-xtm-5-xtm-505-515-525-545-pfsense-64-bit
Advanced/Terminal Type- VT100
Ive rebooted one time after I made this change and it seemed to print out just fine for me for the first time. Before I would have to reset the terminal after the initial boot screen.
-
As recommended on this page-
sprechen Sie Deutsch?
http://www.triebwerk23.de/joomla/index.php/firewalls/watchguard-xtm-5-xtm-505-515-525-545-pfsense-64-bit
Advanced/Terminal Type- VT100
Ive rebooted one time after I made this change and it seemed to print out just fine for me for the first time. Before I would have to reset the terminal after the initial boot screen.
That did it. Thank you!
-
Ah, that's interesting I'll have to try that. The invisible output problem has always been an issue for me but I put it down to my console setup. If you restart putty after booting has started it will print out normally.
Thanks.Steve
-
Ah, that's interesting I'll have to try that. The invisible output problem has always been an issue for me bit I put it down to my console setup. If you restart putty after booting has started it will print out normally.
Thanks.About time I was able to help you out with something on these boxes! :) Its usually you giving me the ah ha moments…
-
Ah, that's interesting I'll have to try that. The invisible output problem has always been an issue for me bit I put it down to my console setup. If you restart putty after booting has started it will print out normally.
Thanks.Steve
Well, I feel much better now being the noob I am. Pfsense is up and running I love it. I got snort… Next to configure Dansguardian for the kids, squid and antivirus.
-
Got a weird issue. I have the latest version of pfense running on a Watchguard XTM 525 from a SSD drive. I had to unplug the CF card in order to boot from the SSD drive. The BIOS is locked down (has not been flashed). I have been running this setup for months. In pfsense, WAN port is assigned to em3 and the LAN port is assigned to em4. This corresponds to Port 5 and Port 6 on the front of the XTM 525. However, every time I reboot pfsense, the WAN and LAN port in pfsense is still assigned to em3 and em4 but it now corresponds to a different Port on the front to the XTM 525. So now I have to switch the network around on the front of the XTM 525 to get to work.
Anyone else experience this issue.. Very frustrating.
-
Hmm, that's interesting in two ways.
The ports should not change between boots, they are numbered on the order they are detected but since they are on-board that should not change. It could conceivably change with a new kernel or some PCIe subsystem component but I've never seen that.
Ports 5 and 6 on the XTM5 are the last two em ports so they should be em4 and em5 not 3 and 4. Unless you have a second gen xtm5 perhaps though I thought they were the same in terms of ports.What ports does it change to?
Steve
-
Got a weird issue. I have the latest version of pfense running on a Watchguard XTM 525 from a SSD drive. I had to unplug the CF card in order to boot from the SSD drive. The BIOS is locked down (has not been flashed). I have been running this setup for months. In pfsense, WAN port is assigned to em3 and the LAN port is assigned to em4. This corresponds to Port 5 and Port 6 on the front of the XTM 525. However, every time I reboot pfsense, the WAN and LAN port in pfsense is still assigned to em3 and em4 but it now corresponds to a different Port on the front to the XTM 525. So now I have to switch the network around on the front of the XTM 525 to get to work.
Anyone else experience this issue.. Very frustrating.
I use 515 with 128GB SSD and 4GB of RAM and Quad CPU so pretty similar setup. My firewall is running very smooth and stable and only times it gets rebooted is when new pfsense is released. Thing is that I never had to move any cables around - my settings stick and survive a reboot. I did however flash the BIOS and have full functionality on it thanks to stephenw10. It is recommended but dangerous - do it on your own risk.
-
Statistically it's not that dangerous. I think I'm the only one who actually bricked their box and I only did it by flashing a bad image. It is possible to recover the bricked box also. ;)
Steve
-
Hmm, that's interesting in two ways.
The ports should not change between boots, they are numbered on the order they are detected but since they are on-board that should not change. It could conceivably change with a new kernel or some PCIe subsystem component but I've never seen that.
Ports 5 and 6 on the XTM5 are the last two em ports so they should be em4 and em5 not 3 and 4. Unless you have a second gen xtm5 perhaps though I thought they were the same in terms of ports.What ports does it change to?
Steve
I realize this is weird. So each port on the XTM 525 has it own unique Mac address right? It looks like when I reboot the pfsense box, the port assignments in pfsense (i.e. em3 & em4) gets assigned to a different port on the XTM 525 because the unique Mac address assigned to em3 and em4 is now difference than before….
-
The only time I've seen that happen is if one of the ports is bad in some way and doesn't always come up at boot. Do you see all 7 NICs at every boot?
Steve
-
First of all thanks for your hard work and advice. Iam new to pfSense and Im still reading this whole topic but I'd like to ask you 2 question to resume things up:
- Does pfSense 2.2.3/4 work on XTM 505? I mean by only replacing CF with one pfSense
- What would you say is the FW Throughput? and concurrent sessions?do you know of any issues when using pfSense 2.2.x with XTM 505?
Best wishes for you and thank in advanced,
xTiNcTion
-
First of all thanks for your hard work and advice. Iam new to pfSense and Im still reading this whole topic but I'd like to ask you 2 question to resume things up:
- Does pfSense 2.2.3/4 work on XTM 505? I mean by only replacing CF with one pfSense
- What would you say is the FW Throughput? and concurrent sessions?do you know of any issues when using pfSense 2.2.x with XTM 505?
Best wishes for you and thank in advanced,
xTiNcTion
I'm installing my recently purchased XTM 510 as well. For now I have flashed a CF-card with pfSense 2.2.4, put it in the box and it worked flawless.
Configuring seems to be a slow process, but I read in this thread it might be due to the slow writing to CF.I can't tell you anything about performance yet…
-
I'm installing my recently purchased XTM 510 as well. For now I have flashed a CF-card with pfSense 2.2.4, put it in the box and it worked flawless.
Uhmm… just to (me) be sure. You just copied image to CF ... booted from it ... and run installer I guess? and pF got installed on CF itself, right?
Configuring seems to be a slow process, but I read in this thread it might be due to the slow writing to CF.
I can't tell you anything about performance yet…
I read about cf-performance issues too. have you tried to add "extra" HDD? so pF mount it during boot??
Thanks for you reply, I appreciate it.
xTiNcTion -
I'm installing my recently purchased XTM 510 as well. For now I have flashed a CF-card with pfSense 2.2.4, put it in the box and it worked flawless.
Uhmm… just to (me) be sure. You just copied image to CF ... booted from it ... and run installer I guess? and pF got installed on CF itself, right?
Rather flashing than just copying, I used Win32 Disk Imager. It's like burning an ISO-file to a DVD: if you just copy over the .iso (or in this case .img)-file it won't work.
Configuring seems to be a slow process, but I read in this thread it might be due to the slow writing to CF.
I can't tell you anything about performance yet…
I read about cf-performance issues too. have you tried to add "extra" HDD? so pF mount it during boot??
Thanks for you reply, I appreciate it.
xTiNcTionNo, and I don't think I will: the initial configuration will take some time (adding networks, NAT, firewall rules,…), but afterwards there won't be much changes. I don't use it as a proxy either, so I don't think I need a HDD.
-
burnt 2.2.4 image to the stock 1gb cf card in my xtm5. Trying to update the bios so I can use an old HDD. I have installed PKG, but there is not enough room to install flashrom and all its dependencies. Is everyone using a larger CF card than 1gb to accomplish this?
-
burnt 2.2.4 image to the stock 1gb cf card in my xtm5. Trying to update the bios so I can use an old HDD. I have installed PKG, but there is not enough room to install flashrom and all its dependencies. Is everyone using a larger CF card than 1gb to accomplish this?
Ive always used 4gig card myself so can't answer.
-
Can someone guide me, in the what kind of memory I should buy to upgrade?
I can see, that it is DDR2 800, but i don't know the number of pins.I just bought an XTM 5, but it was very unstable and slow. I loaded the image (4gb 2.2.4 64 bit) on a kingston 4 Gb card.
I boots up slow, the interface is very slow, and when changing settings, it hangs for more than one minute.
Now I'll try the 32 bit image, and a different card. I will also try changing the memory.
I bought it used on ebay, assumeably working, but I can't be sure of course.My firebox x500 works fine.
regards
-
The stability issue seems to be caused by the flash card. When using a 4 GB Sandisk extreme IV card it worked much better, even even faster when I used the Sandisk Ultra 8 Gig.
Actually I think i recall other people discussing an issue with the flash cards, specifically using a larger one.
Still didn't find out the pin number. Guess I will have to count them :)
-
thanks for your post. since last year, out watchguard xtm 505 is working under pfsense (embedded on CF), but we need a proxy server, so I decided to flash bios, install on hdd.
flashing bios needs enabling pkg, and pkg install comand. after that, clearing CMOS to change settings in BIOS. and, finally, it won't boot from USB stick, so I use another PC to install pfsense on HDD. after first reboot, I detached the HDD, plug into WG, pull out CF-card, and it's works like a charm. Thank you!
Now i have full (not embedded) PFsense booting and running from HDD, much of free space on disk.
