Watchguard X750e running pfSense on a SATA hard drive easily with about $10 mods
-
Thanks DeLorean / Steve.
I will replace the ribbon to rule it out, however the console remains fully functional and the shell is usable so I doubt it is that.
Steve, there are no timeout messages and having known there was an issue with the 4 extra ports, I configured the LAN interface on SK0 so that I would still be able to access the device, but this drops too. I will have a read through the link and see if I make any progress.
Thanks
-
If all the NICs stop passing traffic you might check for an mbuf limit being hit. You would usually see something logged when that happens.
[2.3.4-RELEASE][root@pfsense.fire.box]/root: netstat -m 11100/1305/12405 mbufs in use (current/cache/total) 2997/799/3796/20758 mbuf clusters in use (current/cache/total/max) 2997/798 mbuf+clusters out of packet secondary zone in use (current/cache) 0/10/10/10378 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/3075 9k jumbo clusters in use (current/cache/total/max) 0/0/0/1729 16k jumbo clusters in use (current/cache/total/max) 9045K/1964K/11009K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/9/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfileSteve
-
I know this is a bit old but i'm just now getting a bit of free time! ::)
The lcdproc package should run pretty reliably in 2.3.4 with whatever option screens you selected.
To get the NIC LEDs working as expected you need the modified drivers that set the LED registers correctly. However I've seen some reports of them not running nicely in 2.3.X. YMMV.
Steve
yeah I will have to work on the LCD a bit and I think I am one of them who is going to have the LED's not run nicely :/ I did modified the drivers and they are still the same. Guess ill have to look into this a bit more. ::)
EDIT/ADD TO:
So I got my IDE drive and installed it, I will make a new post later on to update on the progressI am using these:
http://www.vizi0n.com/watchguard/if_sk.ko
http://www.vizi0n.com/watchguard/if_msk.koSolid when link up and no activity
Blinks when there is activityWorks fine on 2.3.4
You can verifiy if the mod is running by running "dmesg | grep LED". You should see an output like this:
[2.3.4-RELEASE][admin@pfSense.localdomain]/root: dmesg | grep LED mskc0: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0x8000-0x80ff mem 0xd0020000-0xd0023fff irq 16 at device 0.0 on pci1 mskc1: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0x9000-0x90ff mem 0xd0120000-0xd0123fff irq 17 at device 0.0 on pci2 mskc2: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xa000-0xa0ff mem 0xd0220000-0xd0223fff irq 18 at device 0.0 on pci3 mskc3: <marvell yukon="" 88e8053="" gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xb000-0xb0ff mem 0xd0320000-0xd0323fff irq 19 at device 0.0 on pci4 skc0: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xc000-0xc0ff mem 0xd042c000-0xd042ffff irq 16 at device 0.0 on pci5 skc1: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xc400-0xc4ff mem 0xd0420000-0xd0423fff irq 17 at device 1.0 on pci5 skc2: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xc800-0xc8ff mem 0xd0424000-0xd0427fff irq 18 at device 2.0 on pci5 skc3: <marvell gigabit="" ethernet="" (led="" mod="" 2.2)="">port 0xcc00-0xccff mem 0xd0428000-0xd042bfff irq 19 at device 3.0 on pci5</marvell></marvell></marvell></marvell></marvell></marvell></marvell></marvell>Thanks I will give this a try.
PS.
Sorry I didn't post an update like I said, it was late and I was at the DC working and on a bit of a slow night when I did the mod so I forgot to take pic's :(
