OK I'm now using the Sunday May 13 build, fresh install. Still the same problem.

@jimp:

That would be the easiest thing to do, if the package is gone, a firmware update (or a gitsync) would be the best way to ensure a good system state.

That did the trick - thanks.  I did an update - there's plenty of snapshots coming out without having to do a Git sync 8)

Ok so, as you say, it looks like you have 6 Intel NICs and they're all the legacy type, em(4) driver.

Thus apart from the the nmbclusters tweak the others are not doing anything.

You should use /boot/loader.conf.local for additonal loader options as /boot/loader.conf can be overwritten at a firmware upgrade.

I don't see why you need to load the igb driver.
Put in hw.em.num_queries="1" instead of igb.
Remove the bce stuff.

Cross your fingers!  ;)

Interestingly I don't have any OIDs at hw.em but most were introduced after FreeBSD 8.1.
Edit: Doesn't appear to be a valid OID under 8.3 either.  :-\

Steve

Edit: As suggested above, if it is out of nmbclusters that should show up after a crash.
Also putting a dmesg list in a code box makes your post much easier to read.  ;)

@m4f1050:

802.11n is something I am hoping we get soon on FreeBSD.  Is it available yet (on 8.3 or 9?)

No. Some 802.11n capable devices are supported in 802.11g compatible mode.

I would very much like to this guy I met, he's called murphy. You'll love him, he has a great sense of humor.

Thanks! Hopefully someone makes one for 2.1 :)

Ok, here is what i have done.
Taken over the pc cover and removed the hard disk, i was amazed on how much dust can be found in a piece of machinery almost 10 years old, i then screwed back the hd in place, put back the cover and guess what? still no luck with the same error message, i then remembered that i did not reconnect the wires on the hd  ;D  so opened up again, restarted, and now is back in business, thanks you guys!  :D

It works on virtual IPs. You might not have a firewall rule permitting the traffic to that destination, or may have NAT configured  that redirects that traffic elsewhere so the server doesn't receive it (there is none by default).

fixed, thanks

great.

Hi mikesamo,

Sure, the thing is it looks like there's a complete package of Unbound that's included in the 2.1 dev builds that was added back in the first week of April, it's just not available\visible as a service you can enable. I don't know how far along it is or if they found some problem but it looks like it's there and just needs the final bits committed to make it available for us to test.

-Will

Foxconn D270S board here (Intel Atom D2700). Realtek 8111e onboard NIC, doesn't work at all in 2.0.1 for me, works great in 2.1. So yup, definitely new Realtek driver that's in 8.3. See here:

http://www.freebsd.org/releases/8.3R/relnotes-detailed.html

I just wish 2.1 was actually usable. I know, I know, patience. I just wasn't expecting this and am trying to get this system up for a client (a friendly client running an old machine borrowed from me for now, thankfully). For the most part, what works, works great. Unfortunately, the traffic shaper doesn't work. Snort doesn't work. Etc. The traffic shaper is what I care about, it needs to work before I can even consider setting this up up at the campground it's for. In time, it'll come. :)

Also, anyone considering an Atom D2700 based board (or presumably D2500) - AVOID LIKE THE PLAGUE. The graphics driver in FreeBSD (even 9.0) is messed up beyond belief. You can get through install with the 32-bit version, though there are missing characters and stuff. The 64-bit version only shows one line of text, so you can't even get through an install :( Seriously - it's that bad. I got this board because it was cheap, and it's for a non-profit (I'm semi-donating my time… they'll give me something they're friendly and always do - but I'm not billing them. They also know I use them as a "sandbox" of sorts to try things before I unleash them on my other clients)

If the ethernet link is down it will throw that message after something like 30 something packets.

as soon as the network card buffer is full really. We might be able to patch radvd tosurpress that message.

thank you! I think this is the first time I've seen OpenNTPD logging functioning.    :)

Updated to May 1 release, confirming that this was fixed.

Thanks for the quick draw mcgraw!

I confirm (via a gitsync and a reboot) that this fixes my problem, I now get a "Traffic shaping is not configured" page.

2.1-DEVELOPMENT (amd64)
built on Tue May 1 06:11:28 EDT 2012
FreeBSD pfs.dv.loc 8.3-RELEASE FreeBSD 8.3-RELEASE #1: Tue May 1 07:20:03 EDT 2012 root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64

@jimp:

We stopped resetting the logs at bootup.

OK, thanks for confirmation its intended behaviour.