Wireless Edge Services zl Module Release Notes WT.01.03

Known Software Issues and Limitations

Release WT.01.03

■ L2-L3 (41737) — Attaching an IP ACL with an allow any ACE to the downlink port stops

all the traffic on the downlink, even if there is a MAC extended ACL to explicitly allow ARPs.

Workaround: ACLs attached to the downlink port need to explicitly allow the radio port traffic

to get through to the module, as shown by a portion of a show run command below.

ip access-list extended 100

permit ip any any rule-precedence 1

mac access-list extended 200

permit any any type arp rule-precedence 1

permit any any type 34691 rule-precedence 2

interface dnlink

ip access-group 100 in

mac access-group 200 in

■ L2-L3 (41469) — The error message, "ERROR: There must be at least one peer in established

state to execute this command" is always displayed when doing a reload from within the module

CLI redundancy context, even when peers are present.

Workaround: Execute the reload command from either the web management interface, or the

module CLI.

■ L2-L3 (40107) — DHCP boot file names are limited to 63 characters in both the CLI and

the web management interface.

■ L2-L3 (40163) — The DHCP hostname field is unable to accept non-alphanumeric

characters.

■ Redundancy (41949) — A wireless station may show up on multiple modules in a

redundancy group after failing over from a module that was removed from the switch.

Connectivity and traffic for the wireless station are not affected.

Workaround: The genuine current wireless station owner is the one with the shortest amount of

time in the "Last Active" field in the Device Information -> Wireless Stations -> Details button.

■ Security (36833) — The integrated firewall feature is supported only for packets received

on Layer 3 interfaces. For packets getting switched, no firewall protection is applied. The

firewall functionality supports protection against various network level attacks and inspects

each packet for possible corruption that can indicate some kind of attack.

■ Security (41086) — The ACL logging functionality is not available for Layer 2 or WLAN

ACLs.

■ Security (39537) — FTP control packets are not getting appropriately marked when a

standard access list is configured for marking TOS bits.