Pfsenes on SUPERMICRO SYS-5015A-H?
-
I have one of these running 1.2.3-RELEASE. It did become unresponsive after about 24 hours of boot. I think the Realtek interfaces are to blame. I disabled TSO (hardware offload) on the advanced page and it's been running without issue since.
-
upon further searching of the message board and the pfsense website I noticed some recommendations for
http://www.hacom.net//catalog/network-appliances/pfsense , more specifically their Phoenix / Mercury versions; which may even be better since these are complete solutions and the cost seems reasonable as well. Any opinions of the Hacom appliances? Although I just noticed they too have realtek Nics….Some of the Hacom units have the Intel Atom and Intel NIC's. These would be preferable over their offerings that have a VIA processor and/or Realtek NIC's. Check which is which before ordering.
-
I was currently looking at this supermicro barebones 1U setup I found at
http://www.newegg.com/Product/Product.aspx?Item=N82E16816101262I mainly was curious if anyone has any experience with these boards with the Intel Atom 330 Dual-Core interms of performance and if it can keep up as well as if it is compatible with Pfsense. I plan to setup at least minimum 2 vlans, with about 25 computers and possibly a VPN connection to our remote site.. which really only has 1 staff computer so the VPN connection isnt that intense interms of clients using it.
Any insight on this would be great, or even other suggestions if this turns out not to be powerful enough.
Those Atom 330's from Supermicro are great. I have several of them in the field and they have worked very well. Some people have had concerns about the Realtek network cards in them, but I haven't had a single problem. It should more than handle that load, even with some packages running.
-
Awesome, thanks a lot for the feed back jimp. I'm looking forward to getting my hands on these SuperMicro boards.
-
I recently picked one of these up after my mini-box died.The machine itself so far seems great. I am having one software issue though.
It looks like dhclient has a tough time getting a lease from my Zoom cable modem. This is not a problem with any other machine. It does work sometime but it seems very inconsistent. Even when it does work, if cable goes down and a new IP has to be assigned, I see the interface start bouncing down/up and these log entries appear:
dhclient re0
re0: no link …. got link
dhclient: netstat
dhclient: PREINIT
DHCPREQUEST on re0 to 255.255.255.255 port 67
DHCPREQUEST on re0 to 255.255.255.255 port 67
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
ip length 328 disagrees with bytes received 332.
accepting packet with data after udp payload.
DHCPACK from 192.168.100.1I'm running 2.0-alpha from October. Should I try upgrading or is this just a bug with the re driver?
Thanks!
-
October is extremely old for a snapshot. There have been countless changes to the base OS since then (it's tracking FreeBSD 8-STABLE) so if there was a bug the likelihood of it being fixed since that time is very high. Try to upgrade and see if the problem disappears.
-
I'll give an upgrade a shot.
Auto-update is telling me: The image file is corrupt.
What update URL should I be using? Looks like I'm using FreeBSD 7.2-RELEASE-p3. How worried should I be about auto-upgrading to 8.1?
-
Looks like http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters works. Wish me luck!
-
Yaay! Upgrade to Fbsd 8.0 seems to have fixed my dhcp problems with the Realtek 8111c controllers. THANKS!!!
-
edit ignore, my question was answered
