On 09/07/12 06:01, Chris Buechler wrote:
...
Can anyone comment on the quality of the Broadcom driver in post-8.1
releases? Is there any way to run a more recent kernel in conjunction
with pfSense?
Short of running 2.1, not easily. I do have some customer systems
running 2.1 in
On Sat, Jul 7, 2012 at 3:26 AM, Paul Gear p...@gear.dyndns.org wrote:
On 07/07/12 14:33, Adam Van Ornum wrote:
FreeBSD's driver apparently is much improved in later releases (remember,
pfSense is based on 7.3, which is quite a few years old now), so it's
just
a matter of waiting until
On 07/07/12 14:33, Adam Van Ornum wrote:
FreeBSD's driver apparently is much improved in later releases (remember,
pfSense is based on 7.3, which is quite a few years old now), so it's
just
a matter of waiting until pfSense 2.1(???) comes out, based on FreeBSD 8,
or 9, or whatever the next
On 29/06/12 11:07, Paul Gear wrote:
...
Server hardware: IBM x3550, Xeon E5405 2 GHz, 2 GB RAM, 2 x 300 GB 10K
RPM SAS HD in hardware RAID 1, 2 x Broadcom NetXtreme II BCM5708
1000Base-T (B2)
...
Hope that all makes sense. My gut/experience tells me this is a NIC
driver bug/deficiency.
It's disappointing that FreeBSD's Broadcom drivers are so far behind
VMware Linux - is there anything we can do (as non-kernel hackers)
to help get this very common chipset well-supported? Would throwing
some $$$ at a pfSense or FreeBSD developer be useful?
FreeBSD's driver apparently is
FreeBSD's driver apparently is much improved in later releases (remember,
pfSense is based on 7.3, which is quite a few years old now), so it's just
a matter of waiting until pfSense 2.1(???) comes out, based on FreeBSD 8,
or 9, or whatever the next evolutionary step is.
For what it's
You're largely correct, pfSense has - sometimes - issues with Broadcom NICs.
If you search the mailing list archives and the bug tracker you'll see a number
of reports/complaints.
Many of these issues have been fixed since the 1.x era, but there are still
occasional compatibility issues.
The NIC
Hi,
From: Adam Thompson athom...@athompso.net
You're largely correct, pfSense has - sometimes - issues with Broadcom NICs.
If you search the mailing list archives and the bug tracker you'll see a
number of reports/complaints.
Many of these issues
On Thu, Jun 28, 2012 at 9:07 PM, Paul Gear p...@gear.dyndns.org wrote:
Server hardware: IBM x3550, Xeon E5405 2 GHz, 2 GB RAM, 2 x 300 GB 10K
RPM SAS HD in hardware RAID 1, 2 x Broadcom NetXtreme II BCM5708
1000Base-T (B2)
About two weeks ago I had to put into production a temporary hacked
Hi all,
I'm testing pfSense for a client, looking to put it into an existing
production network some time in the next month or two. (Some background
at [1], if anyone cares...) In terms of features and interface it is a
win, but we're having massive problems with stability that seem to be
On Thu, Jun 28, 2012 at 9:07 PM, Paul Gear p...@gear.dyndns.org wrote:
Hi all,
I'm testing pfSense for a client, looking to put it into an existing
production network some time in the next month or two. (Some background
at [1], if anyone cares...) In terms of features and interface it is a
On Thu, Jun 28, 2012 at 10:11 PM, Paul Gear p...@gear.dyndns.org wrote:
What should be my next troubleshooting step?
memtest? Different NICs?
Have you looked at your MBUF usage (netstat -m)? I get similar
symptoms after running out of MBUFs, but if you followed the first
step in the doc you
12 matches
Mail list logo
