Successful Install on Watchguard Firebox X700!

Brak

My X-Core box is failing, when I switch it on the arm/disarm led flashes green and it doesn't post.
While looking for any information on what it might be trying to tell me I cam across a couple of interesting things.
Firstly the X-Core box is pretty much identical to the fw-6650, an appliance that is marketed by various companies, e.g.
www.delvingware.com/webservices/medialibrary/media/datasheets/FW-6650-1.pdf

Secondly the motherboard in that box is the MB-X66 (the X-Core board is labled WG-X66A) but I can't find anything about that. However there is some information available on the MB-X67. A user manual is available here:
http://wenku.baidu.com/view/e04f207831b765ce05081465.html
It is an almost identical board but uses Intel NICs instead of Realtek. All the pinouts are listed and all the jumpers explained.
It looks like it might be possible to download the pdf from there but my Chinese is very bad!

No help with my led though. ::)

Steve

Yeah, I saw some of those units on eBay and as soon as I saw the drive-tray clips I was like… "Damn, Lanner made all the Fireboxes..."

I really think though if someone was aiming to build new units, you might as well go for the Lanner FW-7565, but I don't know if the LCD/LCM is usable. : /

I wanted to start selling new with warranty pfSense boxes, but people are so picky about the LCDs, it's unreal.

jdetmold

Hey hopefully some one may be able to shed some light on this issue.

when i connect to teh serial port (9600 8-n-1) i can see the boot just fine but when it asks if i want to set vlan if i say no it just skips the wan configuration and loops back to vlan… if i say yes configure vlan it takes me to the wan configuration when it asks to enter my wan port and i enter re0 it just skips over the lan line and asks if i want to procede

Enter the WAN interface name or 'a' for auto-detection: re0

Enter the LAN interface name or 'a' for auto-detection 
NOTE: this enables full Firewalling/NAT mode.
(or nothing if finished): 
The interfaces will be assigned as follows: 

WAN  -> re0
.
Do you want to proceed [y|n]?

in the past i have only upgraded from 1.2.3 but I can no longer find a download for it so im trying a fresh 2.0.1 install

hope someone can shed some light on this issue!

stephenw10

Hmm, weird. As though it can only detect one interface. Are you still seeing all the other interfaces probed during the boot?
What if you select a different interface for WAN?

If, for whatever reason, it thinks you only have one interface I believe it will bring up the webgui on WAN so you should be able to then assign the other NICs that way.

You can still get old releases: http://files.chi.pfsense.org/mirror/downloads/old/

Steve

jdetmold

@stephenw10:

Hmm, weird. As though it can only detect one interface. Are you still seeing all the other interfaces probed during the boot?
What if you select a different interface for WAN?

If, for whatever reason, it thinks you only have one interface I believe it will bring up the webgui on WAN so you should be able to then assign the other NICs that way.

You can still get old releases: http://files.chi.pfsense.org/mirror/downloads/old/

Steve

Sorry i should have given more info it does display all interfaces and will do the same thing if I enter a different interface for wan
its as if the terminal sends an extra enter or something and then skips configuring the lan interface

I tried just allowing it to configure wan and was planning to modify it after but forgot the lack of terminal after "bootup complete"

EDIT:

Well after trying the same thing for about the 100th time it seems to have just worked :-S

stephenw10

That sort of thing, that can have you pulling your hair out for hours, can be caused by something really simple like a loose console cable. I was once completely stumped by a computer showing all sorts of bizarre symptoms that turned out to be a sticky key on the keyboard! ::)

Steve

jdetmold

@stephenw10:

That sort of thing, that can have you pulling your hair out for hours, can be caused by something really simple like a loose console cable. I was once completely stumped by a computer showing all sorts of bizarre symptoms that turned out to be a sticky key on the keyboard! ::)

Steve

because it was driving me nuts i kept playing and could reproduce the issue almost every time when using putty so i switched to using screen on my mac and cant reproduce the issue there so it must be something with my putty app

dig1234

Hi I finally got a chance to test pfsense on our firebox x500, and I'm seeing the dreaded watchdog timeout on re0. So far it doesnt appear to be affecting traffic but I haven't had it booted for that long. I thought 2.0.1 was supposed to have fixed that problem? I disabled gateway monitoring as we only have one gateway anyway but didn't help.

PS re0 is connected directly to a Cisco IAD2430 T-1 router.

stephenw10

Unfortunately there seems to be no easy explanation for this.
I have a box here that I am running purely for testing and have yet so see any timeouts. It's connected to a cheap unmanaged SMC 10/100 switch.
2.0.1 is still based on FreeBSD 8.1 and the driver hasn't changed. 2.1 is based on 8.3 so has newer drivers. However it currently has other issues with Nano mounting the filesystem. I had to go back to 2.0.1 for testing, the delay probably wouldn't be problem in a system you're not constantly fiddling with. ::)

Steve

woc38

Since 2.0 I have less to none watchdog timeouts compared to 1.2.3. My re0 is directly connected to my (bridged) cable modem. The re1 is connected to a small and simple HP ProCurve 1400-8G Switch. Only problem is Skype: during calls (with or without video) there are watchdog timeouts on re1 (I have a Skype port forward in the ruleset). Using Skype is therefore no option. SIP based phonecalls are no problem.

stephenw10

Since the timeouts seem to be related to packet fragmentation you might try doing a packet capture to see if Skype is doing something weird.

Steve

tritron

Did anyone installed 2.1 on firebox x700

m4f1050

@tritron:

Did anyone installed 2.1 on firebox x700

Yes, I did. On a 2gb cf card. I did the firmware update. I was installing every update but looks like every 2 days there is one (or at least im checking every 2 days) I am going to test it every week. I don't want to mess up my cf card by writing it so much.

WatchGuard_Police

Just want everyone in the room to know that we (Watchguard Police) are coming to confiscate the modified Watchguard appliances.

You've violated your agreements and we know about it.

Sifter

@WatchGuard_Police:

Just want everyone in the room to know that we (Watchguard Police) are coming to confiscate the modified Watchguard appliances.

You've violated your agreements and we know about it.

hahaha! ya ok, looking forward to it!

cmb

@WatchGuard_Police:

Just want everyone in the room to know that we (Watchguard Police) are coming to confiscate the modified Watchguard appliances.

You've violated your agreements and we know about it.

hahaha Post of the year maybe. :D

I didn't know the Watchguard Police worked for a heavy equipment manufacturing company.

WatchGuard_Police

Yeah… Who'd of guessed it!

Hahaha!

dig1234

@WatchGuard_Police:

Just want everyone in the room to know that we (Watchguard Police) are coming to confiscate the modified Watchguard appliances.

You've violated your agreements and we know about it.

Actually once we have you here there's some issues we'd like to discuss..

stephenw10

Just for a second there alarms went off in my head! ::)

Steve

summy

Ok, so I bought an X700 and I've been having fun messing with it. I had an older IDE hdd sitting around, and figured I would try to make use of it instead of going the CF route. I installed PFsense onto the hdd through a live cd, did the 99 install and selected embedded for console access. I had issues with the 2.x releases, so for now I put on 1.2.3 and planned on upgrading through the WebGUI to 2.1, etc. I put the hdd in, started the FB, and I get to the section where pfsense asks to mount the new hdd. Typing in "?" gives nothing to mount, auto-detection fails and will re-boot the box, and I tried a few of the options people have mentioned here (ufs:ad0s1a, etc)to no success. Am I missing something here? Thanks for any help ^^

I can post screens of the initial startup later tonight when I get home if that's necessary.

stephenw10

Hmm, I've not actually done this myself on this box but according to the very first post of this now ridiculously long thread:
@jmcentire:

8. Couldn't mount drive(since installed on different machine), so it asks what you want to mount enter: ufs:ad2s1a

The internal IDE connector is the secondary and assuming your drive is configured as master (or cable select) it is assigned as ad2 by FreeBSD. Edit: I'm actually a little vague on this! ::)

Steve