I don’t think you understand what we are asking for. Sure the LAN ports become trunking ports, we don’t want that necessarily. Say I have the default vlan, vlan 20 and vlan 30 assigned. I want to set port one of the peplink’s switch to mark any packets that are untagged as vlan 30 and block all other traffic. Set port two to pass packets on vlan 30 only and isolate those two ports to their own network. I could see this useful in both the voip and wireless guest arenas as a start. I guess I really don’t see the usefulness of vlans in the peplink when most any layer 3 switch can handle the routing. The only benefit I might concede is the fact that you can have multiple DHCP ranges, but again, many layer 3 switches can do the same now. Couple that with application based QoS only and I really don’t think I will use it in it’s current state. If you suggest I use the ports as trunking on the peplink side, I really see no added benefit but merely extra programming that may be unnecessary. Anyone feel free to correct me if I am wrong.