Allied Telesis 86251-08 Switch User Manual


 
Patch 86251-08 For Rapier Series Switches 19
Patch 86251-08 for Software Release 2.5.1
C613-10356-00 REV I
A problem existed in a configuration with a single policy involving one
private interface and two On Demand PPP public interfaces with NAT
acting on traffic from the private to each of the public interfaces. Traffic
generated on the device (e.g. pings) that was routed out one of the public
interfaces sometimes caused both PPP interfaces to activate. This occurred
if the NAT relating to the correct PPP was configured first. This behaviour
was partially fixed in PCR 02250. This issue has been resolved so that only
one PPP interface is activated and NAT is used correctly.
The Proxy Arp default setting should be OFF for VLAN interfaces. This
issue has been resolved.
The dot1dStpPortForwardTransitions value in the dot1dBridge MIB was not
correctly incremented when STP transitioned a port to the forwarding state.
This issue has been resolved.
It is now possible to configure an IP filter with the default route of 0.0.0.0.
This allows BGP to control the default route for route distribution.
The dot1dStpInfoTopChanges value in the dot1dBridge MIB was not correctly
incremented when a topology change was detected by the bridge. This issue
has been resolved.
When the device received a route from two separate sources to the same
destination network, RIP only used the metric value when selecting the best
route. RIP now selects the route by lowest preference value, or if they are the
same, by the metric.
Previously, when the ADD FIREWALL POLICY INTERFACE command
activated software routing, the static IP ARP entries were removed
automatically. Static IP ARP entries now remain and the following message
is displayed:
WARNING: Static ARPs associated with a particular VLAN are
recommended to be deleted when Firewall is enabled on the VLAN.
MLD had no mechanism for dealing with an IPv6 interface changing its
local link address. This issue has been resolved.
IPv6 ping or traceroute sometimes caused the device to restart. This issue
has been resolved.
PCR: 03569 Module: FIREWALL Level: 3
PCR: 03571 Module: IPG Level: 3
PCR: 03572 Module: STP Level: 4
PCR: 03573 Module: IPG Level: 2
PCR: 03574 Module: STP Level: 4
PCR: 03576 Module: IPG Level: 2
PCR: 03582 Module: FIREWALL, IPG Level: 4
PCR: 03584 Module: MLD Level: 3
PCR: 03594 Module: PING Level: 2