The only solution is to get another card. AFAIK the QLogic chipset is not supported in both versions. You can review the supported hardware here for 1.2.3 and here for 2.0 if I'm not mistaken.

You still need to follow the same process as before, except there are some changes for 2.0. Check out page 6 of http://forum.pfsense.org/index.php/topic,7920.75.html and you'll see the ramblings of getting it installed on 2.0

Hi
I think my post from quite some time ago might be interesting for you:

@GruensFroeschli:

Nice :)
Well if you have that much bandwidth at hand i suppose you also have appropriate hardware otherwise.
You could split your LAN in multiple DHCP-domains with different gateways but with the users still in the same broadcast-domain.

I'd do this with VLAN's.
Have every client in two VLAN's.
Say VLAN 42 for the broadcast domain.
Everyone in this VLAN can talk with each other.
–> Only clients are in this VLAN (defined by PVID) but not the pfSense.
Additionally every pfSense has its own VLAN.
Say VLAN 100, 200 and 300 (again by the PVID).

Now if a client requests an IP all pfSenses will receive the request.
But only the pfSense on the corresponding VLAN can answer.

NOTE:
The VLAN should NOT be configured on the pfSense.
Egress all packets on all ports untagged (well except the trunks to connect all the switches ;) ).
Inbound packets of the clients should have the PVID of the global domain --> 42
Inbound packets of the pfSense should have the local PVID --> 100, 200 or 300
All ports are members of 42
Only the ports of the local domain are member of 100, 200 or 300.

pfSense1: 10.0.0.1/16 - DHCP-range 10.0.0.2/16 to 10.0.0.255/16, gateway 10.0.0.1
pfSense2: 10.0.1.1/16 - DHCP-range 10.0.1.2/16 to 10.0.1.255/16, gateway 10.0.1.1
pfSense3: 10.0.2.1/16 - DHCP-range 10.0.2.2/16 to 10.0.2.255/16, gateway 10.0.2.1

I'm seeing this again on my Nokia ip330 running 1.2.3 nanobsd with no noticeable performance degradation.

top -SH output:

last pid:  3198;  load averages:  0.97,  0.56,  0.42   up 17+14:10:30  11:08:10 82 processes:  3 running, 63 sleeping, 2 zombie, 14 waiting CPU:  0.4% user, 32.7% nice, 21.5% system,  1.8% interrupt, 43.5% idle Mem: 40M Active, 19M Inact, 32M Wired, 72K Cache, 32M Buf, 147M Free Swap:  PID USERNAME PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND   10 root     171 ki31     0K     8K RUN    381.1H 61.96% idle 9477 root       8   20  6564K  4896K wait   175:35  3.96% sh   31 root     -68    -     0K     8K WAIT   121:58  0.00% irq5: fxp2   12 root     -32    -     0K     8K RUN     63:02  0.00% swi4: clock sio   29 root     -68    -     0K     8K WAIT    48:17  0.00% irq10: fxp0 9615 nobody    64   20  3156K  1232K select  44:17  0.00% apinger   14 root     -16    -     0K     8K -       18:31  0.00% yarrow  944 nobody    44    0  3156K  1336K select  11:55  0.00% dnsmasq   30 root     -68    -     0K     8K WAIT    11:22  0.00% irq12: fxp1 1362 dhcpd     44    0  3156K  2164K select  10:51  0.00% dhcpd   56 root      -8    -     0K     8K mdwait  10:29  0.00% md1 14573 root      44    0  3524K  1868K RUN      5:12  0.00% top  828 root       4    0  5144K  2952K kqread   3:35  0.00% lighttpd    5 root      -8    -     0K     8K -        3:24  0.00% g_down    3 root      -8    -     0K     8K -        3:22  0.00% g_event    8 root       8    -     0K     8K -        3:19  0.00% thread taskq

rrd2.png
rrd2.png_thumb

Back in the day I used an addon for Smoothwall that allowed you to use the LEDs from a keyboard to show activity. (http://martybugs.net/smoothwall/leds.cgi) Maybe someone could do the same with pfSense?

update: I think it had to do with the fact that I was cloning a MAC address before and am no longer do so at the present moment. I no longer have any file system error messages either, so i think that the realtek just had problems accepting a different MAC.

No, not by a long shot currently. They're several AES-256/SHA1/DH5 IPsec tunnels, so I doubt it'll ever reach interface speed. But I'm happy to try it next year as soon as a remote peer also has 100Mbit/s. :)

have a look at the mini-ITX boards
a VIA or ATOM CPU should not have any problems covering your needs.

Whats your internet connection BTW?
Also whats your current systems hardware setup?

anymore info you provide can help you get an answer that provides you with more detail

@fastcon68:

just two vpn tunnels, 4 machines.
rc

you should be fine with 256k
it is 1k per state, I have 7 computers in my network and almost never went above 100 states. To be on the safe side, make sure you have a swap partitiom on you hard drive or compact flash. I also have 256 on the watchguard and I have a 512k swap partition. I don't think however that swap was ever used. Also if you use openvpn make sure on the advanced options you enable the cryptographic card that comes with the watchguard. Just put engine cryptodev on the advanced openvpn options and use one of the supported algorhythms such as aes, des or 3des etc.

Enjoy your watchguard.

The port is labelled "HDDPWR" - or Hard Disk Drive Power.

Thanks a lot for the tips WallabyBob! By the meantime I learned something about pciconf which is similar to lspci in Linux.
I understood. I'll try with some others cards, from other vendors.

Regards,
Matías

Tahowe,

I tried to use a ZTE MF626 with freeBSD, but I think still there is no support for this kind of devices.

http://www.daemonforums.org/showthread.php?t=4597

This is what I could test. I'm new to BSDs, but for the response I got in daemonforums I'd think still there's no support.

May be support is coming soon, or I might be wrong and someone with more experience can add some more useful info.

Regards,
Matías

ah ok, thought so…thanks wasn't sure if the DOM speed had a factor or not once PF was up and running...thanks for the info :)

Looks like it works:
http://forum.pfsense.org/index.php/topic,23919.msg123663.html#msg123663

Not totally straight forward though.  ;D

Steve