Pfsense 2.0 RC1 march 8th build (amd64) = total failure :(
-
Hi all,
I'll keep at is short as possible - have a custom box build for my own home-made router. Box consists of an MSI RS690T (MSI Fuzzy) board with two Marvell 88E8056 1 GBit NICS, one Intel Pro/1000 GT PCI NIC, 2 GB of DDR2-800 and an Athlon 4450e… plenty of power.
The installation went through no problem, however from the get-go I had problems.
Even though TCP segmentation was disabled, I received Tx Mac Parity errors on the LAN Marvell NIC. Swapping to the Intel card yielded watchdog timeout errors every 10-15 minutes which eventually caused complete connection loss and required not only a reboot but restoration to default setting and restore from a backup.
I tried LAGGing the interface which worked fine, for a while, until the watchdog errors reappeared. What happened next was one of the oddest thing I've see - the firewall decided to randomly block ALL LAN->WAN and WAN->LAN requests. The shell log basically showed a block on everything - and nothing I could do reverted that.
Long story short - the wife was not too amused by all these shenanigans so I went back a different product for the time being... I hope the final release of 2.0 would be better for me :(
-
Re: March 8 build - you're lucky, it killed my Alix nano embedded (can't find /bin/sh error) and I had unfortunately
initiated the copy to the second slice before I realized I had a problem, making me reimage the cf card.The RC1 "release" image 20110226 has been working fine in my particular setup (i386 embedded), if you're feeling motivated you could give that a try and see if it works any better for you. Could be the 20110226 release got more testing compared to the recent nightlies, and would work better.
–Ed
-
Re: March 8 build - you're lucky, it killed my Alix nano embedded (can't find /bin/sh error) and I had unfortunately
initiated the copy to the second slice before I realized I had a problem, making me reimage the cf card.The RC1 "release" image 20110226 has been working fine in my particular setup (i386 embedded), if you're feeling motivated you could give that a try and see if it works any better for you. Could be the 20110226 release got more testing compared to the recent nightlies, and would work better.
–Ed
I don't think it would… I had same parity errors in 1.2.3 stable... don't think anything changed between now and then :(
-
UPDATE:
Appears the LAN pointing Marvel NIC has died on the board; it's completely inactive. Probably explains all the grief I've experienced…
Going to pick up a new board tomorrow and RMA this one and we'll see what happens!
Cheers :)
-
That would certainly explain it all. Kind of glad it turned out to be dying hardware instead of a driver issue. Bad for you (but at least you can RMA) but it means others with that chip aren't out of luck.
