P/s: may my machine with 32 bit ( 3G ram) can set kern.ipc.nmbclusters="1000000" ?

Try it but step by step to see how the free RAM is going down and think about you will need some
for the rest entire pfSense.

i swear, i dont know kern.cam.boot_delay=131072 whre from.

And I was not recognizing the time delay time interval!

@BlueKobold:

Is normally to give the pfSense a delay time or pain more time to recognize mostly some USB devices
better to make them then working smooth inside of the pfSense if you have such a device likes a USB
modem or whatever and now it is not really shown once more in your configuration you can easily put
this line of code back in the /boot/loader.conf.local

Yes, but with something much smaller than 131072. That would be a 36.4 hour delay at boot time. :D

Hey, that's just barely enough time for a short nap!

It's work  ;D :D

i swear, i dont know kern.cam.boot_delay=131072 whre from. i copied line  kern.ipc.nmbclusters="131072"  load or save button ( i dont sure), then reboot.
but now, it work.

thank all  :D

P/s: may my machine with 32 bit ( 3G ram) can set kern.ipc.nmbclusters="1000000" ?

Is normally to give the pfSense a delay time or pain more time to recognize mostly some USB devices
better to make them then working smooth inside of the pfSense if you have such a device likes a USB
modem or whatever and now it is not really shown once more in your configuration you can easily put
this line of code back in the /boot/loader.conf.local

Yes, but with something much smaller than 131072. That would be a 36.4 hour delay at boot time. :D

kern.ipc.nmbclusters="1000000"

And before you will doing this you should tell us first please how many RAM is installed inside your
pfSense firewall. 2 GB or 4 GB or 8 GB or how many RAM are inside?

Then you need to reboot this pfSense machine.

kern.cam.boot_delay=131072

Is normally to give the pfSense a delay time or pain more time to recognize mostly some USB devices
better to make them then working smooth inside of the pfSense if you have such a device likes a USB
modem or whatever and now it is not really shown once more in your configuration you can easily put
this line of code back in the /boot/loader.conf.local


i did it, but didn't work.

Really? Why it does not work on your side?
The forum is full of threads and posts that this will be working in many times and situations
for many peoples so I am pretty sure it must work and hepl you also.

can anyone here, help me?

Is this 64Bit hardware?
Is this really a 64Bit pfSense image?
Is this a NanoBSD or full install on a SSD/mSATA?

6 interface = 96%

Let us imagine that you have 8 GB RAM installed and 6,5 GB of RAM are free
and then set up the mbuf size to 1.000.000 you should see that then only
perhaps 4 GB of RAM are free but the mbuf usage is only at 4% or something around this.

So if you have enough RAM to insert, do it! It will not be wasting anymore because it
can be used for high up the mbuf sizes.

pfSense is based on FreeBSD and there fore it might be a problem that comes inside
from FreeBSD and that is the Kernel-buffer, that buffer has a really reserved size and can´t
be moved or enlarged by users. But with tuning the entire mbuf size you are able to swap some
buffer of this Kernel-Buffer and free him a little bit. So this is not only a cosmetic tuning more then
a work around for a really old and known problem, that comes traditionally with very old systems
likes BSD based Operating Systems are.

Please not, for each Core and each LAN interface a queue would be created in pfSense!
So let us imagine you has an Intel Atom C2758 with 8 CPU Cores and 6 LAN interfaces:
8 Core x 6 Interfaces = 48 queues and often then it would be wise to set up another
mbuf size!