background image

2

Patch Release Note

Patch 86241-02 for Software Release 2.4.1

C613-10340-00 REV B

Features in 86241-02

Patch 86241-02 includes all issues resolved and enhancements released in 
previous patches for Software Release 2.4.1, and the following enhancements:

IPX traffic passing between two switch instances using VLAN for Rapier48 
now operates correctly. 

Buffer leaks occurred when DNS relay was enabled. This issue has been 
resolved.

A buffer leak occurred when a large number of flows (over 4000) were in use 
and needed to be recycled. This issue has been resolved.

The EPORT parameter in the ADD SWITCH L3FILTER ENTRY and SET 
SWITCH L3FILTER ENTRY commands was matching multicast and 
broadcast packets with software filtering. This issue has been resolved.

Sometimes the retransmission of an FTP packet was not permitted through 
the Firewall. This issue has been resolved.

VRRP returned an incorrect MAC address for an ARP request. This issue 
has been resolved.

The virtual MAC address was used as the source MAC for all packets 
forwarded on an interface associated with a Virtual Router (VR). This was 
confusing when multiple VRs were defined over the same interface because 
only one virtual MAC address was ever used. The other virtual MAC 
addresses (for the other VR's) were only used if the source IP address 
matched the VR’s IP address. To avoid this confusion, the system MAC 
address is now always used unless the source IP address of the packet is the 
same as the VR’s IP address.

When route aggregation was enabled, the atomic aggregate was not being 
set. This issue has been resolved.

HTTP requests from a fixed IP address were erroneously reported as a host 
scan attack in the Firewall deny queue. This issue has been resolved.

PCR: 02103

Module: SWI

Network affecting: No

PCR: 02210

Module: DNS Relay

Network affecting: No

PCR: 02214

Module: IPG

Network affecting: No

PCR: 02220

Module: SWI

Network affecting: No

PCR: 02236

Module: FIREWALL

Network affecting: No

PCR: 02245

Module: VRRP

Network affecting: No

PCR: 02263

Module: VRRP

Network affecting: No

PCR: 02267

Module: BGP

Network affecting: No

PCR: 02268

Module: FIREWALL

Network affecting: No

Summary of Contents for 86241-02

Page 1: ...ion Set for Software Release 2 4 1 available on the Documentation and Tools CD ROM packaged with your switch or from www alliedtelesyn co nz documentation documentation html WARNING Using a patch for...

Page 2: ...rtual MAC address was used as the source MAC for all packets forwarded on an interface associated with a Virtual Router VR This was confusing when multiple VRs were defined over the same interface bec...

Page 3: ...king correctly Also the SHOW CONFIGURATION DYNAMIC and SHOW CONFIGURATION DVMRP commands were not working correctly These issues have been resolved TELNET sessions are now closed with D only when the...

Page 4: ...urce IP address of ICMP redirects should be the IP address that the end host used when making its next hop routing decision In the case of a packet sent to a VRRP virtual MAC address this is the prima...

Page 5: ...n after a 2 5 second delay The sequence number extracted from the AH and ESP header was in the wrong endian mode which caused an FTP error with IPSEC anti replay This issue has been resolved It is now...

Page 6: ...tered as the interface value in the DESTROY FRAMERELAY command The command now only accepts 0 63 for this parameter The ADD FRAMERELAY DLC command incorrectly accepted a TYPE parameter Also this comma...

Page 7: ...utOctets counter to increment Now if the ONLINELIMIT is exceeded the link will close Entering 63 for the EPORT parameter in the ADD SWITCH L3FILTER command caused a fatal error This parameter now acce...

Page 8: ...ly A warning now appears when the DELETE IP INTERFACE command is executed before the DELETE DVMRP INTERFACE command VRRP pre empt mode was not working with advertisement updates of 1 second or more be...

Page 9: ...ter Advertisements RAs were discarded when the interface was enabled to send RAs This issue has been resolved The IPv6 priority filter was not matching correctly when TCP was specified as the protocol...

Page 10: ...rt on the Rapier 48 did not correctly compensate for the stack tag on frames received via the filter This issue has been resolved Firewall subnet NAT rules were not working correctly from the private...

Page 11: ...e offered address was on the same network as the other Ethernet interface An error is now recorded when DHCP offers an address that is in the same subnet as another interface Availability Patches can...

Page 12: ...12 Patch Release Note Patch 86241 02 for Software Release 2 4 1 C613 10340 00 REV B...

Reviews: