Always. Search result is picky about input naturally and it's not always easy to know what key words have been mostly used in threads dealing with your specific problem (which you may or may not know since you may only see symptoms and your guesses as to whatr causes it may be incorrect and hence you use and search for the incorrect keywords) and what exact combination of words will yield that output with the truth… Search for torrent and states only yields 2 pages of hits and not many seems closely relevant at first glance. I previously only found one post that seemed 100% relevant (and have forgotten the search keyword to find it). Thanx for your constructive reply.

@GruensFroeschli: Currently you can run the traffic shaper only on 2 interfaces. No workaround. There was a bounty that lead to the addition of said new shaper. If i remember correctly everyone commiting to the bounty back then was provided with a howto to get the new shaper running on the current version. Not sure if you could get that if you donate some money to the developer of the new shaper (ermal). Where to start for other distros? Not sure actually. How much are you willing to pay?

Try the test without the switches, i.e., just use crossover cables: test machine                      ¦                   ¦               pfSense                   ¦                   ¦                    test machine

Yes, i use PFSENSE as a router and AP (dd-wrt) without dhcp. My first problem was that AP could not reach external ntp-server, i solved it today with google. I had missed to set DNS adress in AP to PFSENSE router. The time came directly. Now shall i test to run time from PFSENSE. I dont need it now, just for a test. Thanks for your help.

Thanx buddy a lot. Prbm was with my ip adress that I was using.Now after using RFC 1918 prbm get solved.

Can you show the switch configuration here? Also I'd like to see the pfSense rules and interfaces configurations. Also a simple diagram showing how you've got things connected would help.

What NICs are in use for WAN and LAN interfaces? Instantly upon receiving my package, the port closest to the power input is used for LAN The question isn't about their physical location - but the types of NIC.  At the very least you need to identify the driver or interface name (eg, fxp or fxp0).

This issue has been solved.  I'm not sure exactly what was wrong, after spending so much time thinking it was the software i decided to take my entire network apart and put it back together. After doing this and a fresh install, and setting everything up manually instead of using one of my previus backups, everything works. I'm still not sure what it was but it's all good now.

Sounds to me like your box doesn't support ACPI. http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface

dotdash is correct, you will not be able to assign CARP IP addresses that don't belong to the same range as the interface they're assigned to.  This is a FreeBSD limitation and it causes nasty kernel panics.

@HelloZ: Can I set it up as a switch so that performace is equal to my switch. If you want switch performance you need to use a switch.