Answer the question
In order to leave comments, you need to log in
Why don't VLAN ACLs work on D-Link?
There is a D-Link DES-3200-18 rev. A1
When creating ACLs for subscribers, we usually apply ACLs specifically to specified ports. If the service on the port changes, we demolish all ACLs and place them again, binding to each port.
I decided to confuse the ACL with a binding not to the port, but to the VLAN, so that when changing the service on the port, it would be enough to change the VLAN and apply the ACL for the VLAN that is specified on the port.
It turned out like this:
DES-3200-18:5#sh conf cur begin "ACL"
Command: show config current_config begin "ACL"
# ACL
#Правило для VLAN'ов, по которым предоставляется PPPoE. Разрешаю PADI/PADO пакеты.
create access_profile ethernet vlan 0xFF ethernet_type profile_id 2
config access_profile profile_id 2 add access_id 1 ethernet vlan v100 ethernet_type 0x8863 port 1-16 permit
config access_profile profile_id 2 add access_id 2 ethernet vlan v100 ethernet_type 0x8864 port 1-16 permit
#Правило для VLAN, по которому гонится SIP - разрешаю всё в 15-ом VLAN'е
create access_profile ethernet vlan 0xFF source_mac 00-00-00-00-00-00 profile_id 3
config access_profile profile_id 3 add access_id 1 ethernet vlan v15 source_mac 00-00-00-00-00-00 port 1-16 permit
#Остальное - блочим нафиг
create access_profile ethernet source_mac 00-00-00-00-00-00 profile_id 512
config access_profile profile_id 512 add access_id 1 ethernet source_mac 00-00-00-00-00-00 port 1-16 deny
disable cpu_interface_filtering
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question