@johnpoz:
And what are these AP.. support of multiple SSIDs does not always mean they support vlan tagging of the SSID if your using what amounts to a user wifi router as AP, etc..
As to procedural help for you d-link switches.. Your going to be better off RTFM for your switch or via dlink forums, etc. What is the make and model of these switches? Maybe someone uses them.
Here is a example drawing I did up for another user that PM about their network.. This should help as an overview.
So in this example pfsense has 3 interfaces used on the "local" side of pfsense. Lan and VPN would be two layer 2 networks (vlans on the switch - not in pfsense) Where the switch would isolate this traffic but its not tagged. While the wlan interface in this drawing has a native untagged network just like lan and vpn, it also does vlan tagging on that interface and handles your wifi tagged ssid based vlans.
So in a wired network you can do tagged or untagged "vlans" with wifi your going to have to do tagging of the vlans. This is can be confusing to new vlan users.
In the example there are 2 switches, this can be expanded to as many switches as you have, etc. The term "trunk" here reflects the cisco use of the term to man a port that carries tagged vlans. The color coding of the ports reflects what the native vlan of that port is, etc.
This is pretty good overall example of how in a very simple network how you could isolate different networks from each other some tagged and others untagged "vlans" So in pfsense you would have setup of interface of wlan, and then on top of that physical interface you would create the "vlans" for your wifi networks.
Hope that helps.
In our PFSense , we just have to cards , LAN & WAN.under the LAN interface as the parent I have created a sub interface for the guest vlan, logically…. will this work or is it advisable to add one extra NIC card on the pfsense machine, and this extra NIC card i configure it to serve new Guest VLAN i intend to create
