Hmm, possibly some hardware fault then. Does the box boot anything else successfully? The original Watchguard OS? The FreeDOS image? Do you know the history of that box? Many of those original X-Core boxes have seen many hours in hot racks, my own X700 failed probably due to bad capacitors. Different to symptoms to your though. Steve

Hi Jimp Thanks a Lot for your help, this is the content of the ddb.txt file, if you can help me with this topic and save my job jeje db:0:kdb.enter.default>  run lockinfo db:1:lockinfo> show locks No such command db:1:locks>  show alllocks No such command db:1:alllocks>  show lockedvnods Locked vnodes db:0:kdb.enter.default>  show pcpu cpuid        = 1 dynamic pcpu = 0x56b7080 curthread    = 0xc6d948a0: pid 11 "idle: cpu1" curpcb      = 0xc6be9d80 fpcurthread  = none idlethread  = 0xc6d948a0: tid 100003 "idle: cpu1" APIC ID      = 1 currentldt  = 0x50 db:0:kdb.enter.default>  bt Tracing pid 11 tid 100003 td 0xc6d948a0 kdb_enter(c0f9278c,c0f9278c,c0fc6637,c15c9970,1,…) at kdb_enter+0x3b panic(c0fc6637,1,1,0,0,...) at panic+0x102 dblfault_handler() at dblfault_handler+0x9b --- trap 0x17, eip = 0xc0e6ebb8, esp = 0xc6be9008, ebp = 0xc6be9cf0 --- Xpage(0,c6be9d28,0,0,0,...) at Xpage fork_exit(c0ac2af0,0,c6be9d28) at fork_exit+0x87 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xc6be9d60, ebp = 0 --- db:0:kdb.enter.default>  ps   pid  ppid  pgrp  uid  state  wmesg    wchan    cmd 57550  1363 79000    0  RE      CPU 0              pfctl 42846 72549 79000    0  S      nanslp  0xc1550844 sleep 1363 79000 79000    0  S      wait    0xc8f44000 php 63696 75359 75359    0  S      nanslp  0xc1550844 php 63988    1 63988  1002  Ss      select  0xc877e8e4 dhcpd 72549    1 79000    0  S      wait    0xc8f42000 sh 5968    1  5855 65534  S      select  0xc877e324 dnsmasq 96801 85024 84448    62  S      sbwait  0xc830d254 initial thread 96547 85024 84448    62  S      sbwait  0xc8f65254 initial thread 96527 85024 84448    62  S      sbwait  0xc827b254 initial thread 96302 85024 84448    62  S      sbwait  0xc94173f0 initial thread 96140 85024 84448    62  S      sbwait  0xc827bd98 initial thread 41151    1 79000    0  S      piperd  0xc7bcc498 logger 41030    1 79000    0  S      bpf      0xc831d800 tcpdump 6630    1  6630    0  Ss      (threaded)          mpd4 100175                  S      select  0xc8348524 mpd4 45504    1 45504    0  Ss      select  0xc73334a4 racoon 92278 90346 92278    0  S+      ttyin    0xc6f2c470 sh 90346 90135 90346    0  S+      wait    0xc72d0560 sh 90275 37999 90275    0  Ss      (threaded)          sshlockout_pf 100137                  S      nanslp  0xc1550844 sshlockout_pf 100136                  S      piperd  0xc7386620 initial thread 90135    1 90135    0  Ss+    wait    0xc82d5000 login 87882 87577 87577    0  S      nanslp  0xc1550844 minicron 87577    1 87577    0  Ss      wait    0xc7a25ac0 minicron 87505 87187 87187    0  S      nanslp  0xc1550844 minicron 87215 86730 86730    0  S      nanslp  0xc1550844 minicron 87187    1 87187    0  Ss      wait    0xc8287ac0 minicron 86730    1 86730    0  Ss      wait    0xc8285560 minicron 86655 85024 84448    62  S      piperd  0xc8a91498 unlinkd 85024 84448 84448    62  S      kqread  0xc88e7d00 initial thread 84448    1 84448    0  Ss      wait    0xc82d5560 squid 39954    1 39954    0  Ss      nanslp  0xc1550844 cron 37999    1 37999    0  Ss      select  0xc853d824 syslogd 99107    1 99107    0  Ss      select  0xc853fbe4 ntpd 79000 74926 79000    0  Ss      wait    0xc738d2b0 initial thread 75359 74926 75359    0  Ss      wait    0xc8286560 initial thread 74926    1 74675    0  S      kqread  0xc8405200 lighttpd 68870 68742 68742    0  S      piperd  0xc7bcc000 rrdtool 68742    1 68742    0  Ss      select  0xc853e4a4 apinger 65178    1 65178    0  Ss      select  0xc7e3e1e4 inetd 11429    1 11429    0  Ss      (threaded)          sshlockout_pf 100115                  S      nanslp  0xc1550844 sshlockout_pf 100075                  S      uwait    0xc7333bc0 initial thread 11288    1 11288    0  Ss      select  0xc7e3f1e4 sshd   269    1  269    0  Ss      select  0xc7bae7e4 devd   260  258  258    0  S      kqread  0xc7a72900 check_reload_status   258    1  258    0  Ss      kqread  0xc7a72880 check_reload_status   66    0    0    0  SL      mdwait  0xc7328000 [md0]   37    0    0    0  SL      (threaded)          zfskern 100088                  D      l2arc_fe 0xc7510b04 [l2arc_feed_thread] 100087                  D      arc_recl 0xc750197c [arc_reclaim_thread]   24    0    0    0  SL      sdflush  0xc157f1e0 [softdepflush]   23    0    0    0  SL      vlruwt  0xc7300810 [vnlru]   22    0    0    0  SL      syncer  0xc15645b8 [syncer]   21    0    0    0  SL      psleep  0xc15642e8 [bufdaemon]   20    0    0    0  SL      pollid  0xc154fd7c [idlepoll]   19    0    0    0  SL      pgzero  0xc157fe94 [pagezero]   18    0    0    0  SL      psleep  0xc157fabc [vmdaemon]   17    0    0    0  SL      psleep  0xc157fa84 [pagedaemon]   16    0    0    0  SL      ccb_scan 0xc1518c54 [xpt_thrd]     9    0    0    0  SL      pftm    0xc050c170 [pfpurge]     8    0    0    0  SL      waiting_ 0xc156b9b8 [sctp_iterator]   15    0    0    0  SL      (threaded)          usb 100056                  D      -        0xc70f5d34 [usbus4] 100055                  D      -        0xc70f5d04 [usbus4] 100054                  D      -        0xc70f5cd4 [usbus4] 100053                  D      -        0xc70f5ca4 [usbus4] 100052                  D      -        0xc70dddac [usbus3] 100051                  D      -        0xc70ddd7c [usbus3] 100050                  D      -        0xc70ddd4c [usbus3] 100049                  D      -        0xc70ddd1c [usbus3] 100048                  D      -        0xc70cbdac [usbus2] 100047                  D      -        0xc70cbd7c [usbus2] 100046                  D      -        0xc70cbd4c [usbus2] 100045                  D      -        0xc70cbd1c [usbus2] 100044                  D      -        0xc70b5dac [usbus1] 100043                  D      -        0xc70b5d7c [usbus1] 100042                  D      -        0xc70b5d4c [usbus1] 100041                  D      -        0xc70b5d1c [usbus1] 100040                  D      -        0xc70a4dac [usbus0] 100039                  D      -        0xc70a4d7c [usbus0] 100038                  D      -        0xc70a4d4c [usbus0] 100037                  D      -        0xc70a4d1c [usbus0]     7    0    0    0  SL      aifthd  0xc6d93560 [aac0aif]   14    0    0    0  SL      -        0xc15506a4 [yarrow]     6    0    0    0  SL      crypto_r 0xc157e78c [crypto returns]     5    0    0    0  SL      crypto_w 0xc157e768 [crypto]     4    0    0    0  SL      -        0xc154de64 [g_down]     3    0    0    0  SL      -        0xc154de60 [g_up]     2    0    0    0  SL      -        0xc154de58 [g_event]   13    0    0    0  SL      (threaded)          ng_queue 100010                  D      sleep    0xc14ec5e0 [ng_queue1] 100009                  D      sleep    0xc14ec5e0 [ng_queue0]   12    0    0    0  WL      (threaded)          intr 100072                  I                          [swi1: netisr 1] 100060                  I                          [irq7: ppc0] 100059                  I                          [swi0: uart uart] 100058                  I                          [irq1: atkbd0] 100057                  I                          [irq14: ata0] 100036                  I                          [irq17: uhci0 ehci0] 100035                  I                          [irq16: bge0 rl0+] 100032                  I                          [irq25: vr0] 100031                  I                          [irq24: ste0] 100029                  I                          [irq19: aac0 uhci1+] 100028                  I                          [irq9: acpi0] 100027                  I                          [swi6: Giant taskq] 100025                  I                          [swi5: +] 100022                  I                          [swi2: cambio] 100018                  I                          [swi6: task queue] 100008                  I                          [swi3: vm] 100007                  I                          [swi4: clock] 100006                  I                          [swi4: clock] 100005                  I                          [swi1: netisr 0]   11    0    0    0  RL      (threaded)          idle 100004                  CanRun                      [idle: cpu0] 100003                  Run    CPU 1              [idle: cpu1]     1    0    1    0  SLs    wait    0xc6d92ac0 [init]   10    0    0    0  SL      audit_wo 0xc157eb80 [audit]     0    0    0    0  SLs    (threaded)          kernel 100086                  D      -        0xc7334400 [system_taskq_1] 100085                  D      -        0xc7334400 [system_taskq_0] 100034                  D      -        0xc7071740 [em0 txq] 100033                  D      -        0xc7071700 [em0 que] 100026                  D      -        0xc6ee6180

I used the gig realtek nics in a production environment for a long time with no issues.  They are not as bad as they were many years ago but the reputation they (deservedly) received has remained. If you can afford a supermicro board they are worth the price especially if this is for a work environment.  For a home network I would not stress about what board you use to much. I tried about a year ago to get wireless working with pfsense directly and had many issues so eventually I gave up.  I now use a ubiquity AP instead and it has been rock solid.  Worth the extra expense IMO. http://www.ubnt.com/unifi/unifi-ap/ http://www.amazon.com/Ubiquiti-Networks-UniFi-Enterprise-System/dp/B004XXMUCQ/ref=sr_1_1?ie=UTF8&qid=1405274434&sr=8-1&keywords=ubiquiti+uap

first of all you have to try to set up the definitive modem mode of your stick. It might be done using usbswitch software.

Try it and see, you already have the hardware. If you really don't need anything other than captive portal you may be able to disable a lot of things to improve performance. Steve

Exactly. Realisticly to get 16 ports using NICs alone you're going to have use four quad port cards and they're not cheap!  ;) Steve

Im also on a 1Gbit/1Gbit line.  On 2.1.4 in transparent bridge,  with SNORT,  pfblocker.  Having webserver, mail and some vps running behind it. I was surprised how demanding a gigabit line actually was,  i cannot max out  my CPU,  but its close when i throw all at it.  and if you are planning on 1Gbit and " want to be able to hammer the connection 24/7 with no hassle."  Then without beeing an expert in this i would recommend better hardware,  especially if you plan on using snort and other heavy packages. My build:  e3-1240 v2,  asus P8B-E/4L,  8gb ecc ram,  using the onboard 4 x 82574L. Before you buy hardware for this,  be sure to lookup the hardware to be sure its supportet :)

Thanks for your reply. It's been in production for about 6 months, mfi0 wasn't monitored before but popped up one day when I logged into the admin interface. Oddly enough, it's disappeared again today! I am still on 2.1, so will try updating to 2.1.4 when we have downtime available.

I see there are 2 Hyper-V hosts. I assume they have Quad Gigabit both. You'll not get more than 1Gbit on server-client connection, but You can get more when server-multiple-clients are connected or/and they use different IP subnets. Here is good explanation how to use Network Teaming with Intels: http://www.intel.com/support/network/sb/cs-009747.htm Note, that according to Best Practices You should have at least 2 separate Gigabit switches for redundancy. You may hit internal forwarding limit on this single switch.. (at least - We DID ;D now I know that Gigabit doesn't always mean Gigabit..) You should use LACP (dynamic) or no-LACP (static) Link Aggregation which has to be supported by the switch. SQUID can mess up things since it's redirecting requests on LAN interface.. EDIT: In Your case You should be interested in Virtual Machine Load Balancing (VMLB)

@Smokeshow: We are running quite a few A1SRi-2758F systems on 2.1.3 (they are using the i354 as well). One thing I have found is that you will need to do a bit of tuning to get the cards working great. I had some major slow-dows until I discovered this information. I was always maxing out the mbuf table and causing kernel panics. I followed the instructions here, but here is what you need to do: In /boot/loader.conf.local - Add the following (or create the file if it does not exist): kern.ipc.nmbclusters="131072" hw.igb.num_queues=1 That will increase the amount of network memory buffers, and make the card use one queue instead of multiple queues, to reduce the strain on the system. Tuning for NICs isn't going to help this situation, though changes like the ones you mentioned (well, at least the first one) are necessary for any system with this many cores and NICs. The C2758 lacks the CPU power to do more than 1Gbit or so in a single thread.  That isn't going to change until pfSense 2.2 drops and is based on FreeBSD 10 with multi-threaded pf.  Gonzopancho posted a couple weeks back that they had also found a way to get 12% more out of pf which will help even more.

@robina80: now i understand there BS marketing jargon , when they say AV500, the internface is only 10/100, so you will never ever see 500mbps speeds should have really got the AV500 gigabit, least i would have got 500mbps out of them as the interface is a gig i cant believe i have been had!!! Doubt it.  Think of it like WiFi.  Your link speed may be 300Mbit/s but the odds of you getting more than 40-50% of that, even with line of sight to the AP, are pretty long.  The absolute best of the AV500 adapters are capable of about 250Mbit/s WHEN PLUGGED INTO THE SAME POWER STRIP.  They all drop to 60-80Mbit/s in more realistic residential scenarios. If you really need networking over power lines then I'd suggest waiting a month or two for the AV2 MIMO adapters to start hitting the streets (based on QCA7500).  These should be branded as AV1000 or similar and should be capable of 2-3x the rate of older adapters and be able to maintain higher speeds in less optimal scenarios.

No DNS? Invalid gateway? Faulty one of these SATA drives? (it happends) Why using RAID0 on a SERVER instead of RAID10?? RAID controller model/type?

What exactly are you trying? Assuming you are running a full install there isn't a serial console unless you've enabled it in System: Advanced: Admin Access: With that enabled I would expect to see it via the RJ45 port since the roamer module should start up in pass-through mode. To use the LCD from pfSense it looks like you need to put the roamer module in shell mode and then talk to it using  cu. Steve

Thanks. The router was in place to load balance before I went with pfsence, so it remained.  There are a couple network connections in front of the pfsence box too, so it was just left as is. I prefer a little overkill :-)

The two D2700 boards I have will not allow a 64-bit OS to install.  I've tried with Windows, different versions of Ubuntu and pfSense.  The boards are from different manufactures, but both purchased at the same time.  Every OS tells me the same thing, it says the hardware does not support 64-bit software.

The Broadcom BCM5720 NICs should be supported by the bge(4) driver. Steve