@Perry:
I've been happy with the old version HP 1800-8G
But I'm unsure you'll get what really wanted to begin with
like the layout on this page with the 3com
In other words (maybe do to my own lack of knowledge) I don't see from the 3com docs the benefit of vlan support on the 3com if it can't transfer tagget traffic over the ethernet port and buying a new switch wouldn't change that afaics.
The 3Com WAP fully supports VLANs. I have everything working right now with the new switch I used to replace the Dell. It is/was the Dell that won't allow VLAN1 tagged traffic, not the 3Com WAP. Here's my config now:
pfSense
em0: none
em0_vlan1: LAN - 192.168.254.1/24, DHCP enabled
em0_vlan2: Guest - 172.16.1.1/24, DHCP enabled
alc0 - WAN
Switch
1-22: VLAN1 untagged
23 (3Com WAP) VLAN 1 and 2 tagged
24 (pfSense) VLAN1 and 2 tagged
WAP
SSID: Private, Tagged VLAN1
SSID: Guest, Tagged VLAN2
If I connect to the private SSID then I get the proper IP addressing for that network and am able to communicate with all the other machines on my LAN. If I connect to the guest SSID then I get the proper addressing and cannot access the LAN, only Internet I've also setup a limiter for the traffic speed.
Riley