@Daemonseed: That drives me nuts. I've run into issues finding the right wireless adapter for compatibility due to a card being available with 3 different chipsets, and had to figure out which revision had the chipset i needed. yeah it sucks for anyone not running Windows… can't trust any big name vendor (Linksys, DLink, etc.) to keep their hardware consistent.

LOL  :) not even close to a genius, but glad to be of help with your problem Now you can edit your first post and add [ Solved ] to the Subject  ;)

@/CS: @trunix: You may want to prefix this thread with the words "SOLVED" in the title. I also wanted to do that but coudn't find an option in the menu to rename it, The ability of the writer of a post to Modify the post seems to expire within a time less than a couple of days.

tnx. i changed it to amd64 and it's work really good

Are you sure it's not showing 100% idle? The idle process uses up whatever cpu cycles are not being used by anything useful and is shown by 'top -SH' and opn the System Activity page. E.g.: [2.0.2-RELEASE][root@pfsense.fire.box]/root(2): top -SH last pid: 58916;  load averages:  0.22,  0.08,  0.02    up 2+13:37:03  12:05:18 101 processes: 2 running, 83 sleeping, 16 waiting CPU:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle Mem: 45M Active, 15M Inact, 66M Wired, 1064K Cache, 59M Buf, 359M Free Swap:  PID USERNAME PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND   10 root     171 ki31     0K     8K RUN     59.5H 98.00% idle  262 root      76   20  3408K  1224K kqread   9:36  0.00% check_reload_status   11 root     -32    -     0K   128K WAIT     8:01  0.00% {swi4: clock}   11 root     -68    -     0K   128K WAIT     4:15  0.00% {irq18: em0 ath0+} A copy of your output will clear this up in seconds. Steve

I never changed it.  I think its set to 1500?  Dont remember…

Thanks!!!!!    :)

Check the compatibility list at http://www.freebsd.org/releases/8.1R/hardware.html#ETHERNET

VIP settings, after saving those again everything worked

http://doc.pfsense.org/index.php/Installing_FreeBSD_Packages

@dhatz: I wonder if it's still a problem with the newer FreeBSD 8.3 kernel used by pfsense 2.1-BETA I have since sold the small WISP business that used the virtualized pfSense system I reported on earlier. However, my new employer (an ISP) asked me to build a vSphere cluster and help them virtualize large parts of their central office. So I will soon be able to do further testing with pfSense in this virtual environment.

Looks like packets pass across the bridge from the Physical OPT at least to the QinQ member vlan. I have to wireshark on the WAN (QinQ) link to see if packets actually make it onto the wire. Maybe it's some weird ARP issue? I will have to recheck that the alix boxes I used had the bridging fix applied. I'm actually not sure cuz they were used in a previous lab setup!

I would suggest the first thing is to agree on a test procedure that will give a useful result. It has to be relatively easy to test to get a good number of people producing numbers. It also has to give results that are meaningful to users (not 'I can get 800Mbps if I use jumbo frames across a 4 NIC LAGG'). Then setup a forum thread where people can post results. Finally ask for edit rights on the wiki and setup a page describing the above.  ;) A good example of some great testing is here: http://forum.pfsense.org/index.php/topic,27780.0.html Speak to Jim (jimp) and/or Chris (cmb) who will have a better idea about this than me! Steve

Ok thanks, and thanks for all the great work :)

I miss his provocative avatar.  :( Steve

@sdm12: Then I pointed all vlan 10 traffic to the pfsense. What is the mechanism you used to do that? Since your Cisco firewall is on the same VLAN as the guests it will probably be fairly easy for a knowledgeable user to work out how to bypass pfSense.

Thank you for clarification.

Success!!! :D Okay, after i just realized that WAN/PPPOE actually was on rl0 and not how I assumed the whole time on rl1. I went looking for the now missing rl1 and could not find it in the system.  I then plugged the "rl1" nic back into the pci slot it has been in before and then it got detected again by pfsense. So the only problems there really were, were that i am dumb :P and that something is wrong with one of my pci slots :/ WAN, LAN1 and OPT1 are now working as intended! :) Thanks for all the help!!! <3