With external traffic you can pretty easily setup an ACL for Ingress or Egress traffic.  Ingress ACLs will only take effect when traffic enters the interface from an external source. It will not address traffic that originated in the switch, or has arrived from another interface (for example, being routed between VLANs). So I am not aware of how to setup to where one VLAN can communicate with all others, but they cannot communicate back. You may be able to use ACLs to limit what communication comes back. Here are some links to ACL white pages, these include some great examples of when an ACL would be used and step by step on how it would be implemented. You may be able to use this information to help come up with something that may work for your situation. www.dell.com/.../pwcnt_IP_ACLs.pdf www.dell.com/.../app_note_3.pdf www.dell.com/.../app_note_10.pdf Keep us updated if you find something that works, Thanks
Hello everyone, We are trying to configure our powerconnect 6224 with multiple vlans with routing. For example we have vlan 10-15 and vlan 254 vlan 10 is for server vlan 11 is for telephony vlan 12 is for workstations vlan 13 is for human resources vlan 14 is for the domain administrators vlan 15 is the management vlan for the switches vlan 254 is for the router   What we would like to have is that every vlan has a access to vlan 10 and 254 but not to the other vlans. This we can configure using acl's so that is not the problem.  The problem is that vlan 14 should have access to every vlan but should not be accessible by other vlans. we can enable outgoing traffic from vlan 14 to every other vlan and are able to ping the gateway of all vlan's but are not able to ping to any system connected to the switch out of vlan 14. Is it possible to configure this or will vlan 14 allways be accessible from any other vlan it should have access to.  With kind regards, Luc Verhoeven 
Problems with vlan routing on Powerconnect 6224