Allied Telesis 54266-02 User Manual

Patch Release Note

Patch 54266-02

For AR440S and AR441S ADSL Routers

Introduction

This patch release note lists the issues addressed and enhancements made in
patch 54266-02 for Software Release 2.6.6 on existing models of AR440S and
AR441S ADSL routers. Patch file details are listed in Ta bl e 1.

Table 1: Patch file details for Patch 54266-02.

Base Software Release File

Patch Release Date

Compressed Patch File Name

Compressed Patch File Size

This release note should be read in conjunction with the following documents:

■ Release Note: Software Release 2.6.6 for AR440S ADSL Routers (Document

Number C613-10412-00) available from www.alliedtelesyn.co.nz/

documentation/documentation.html.

■ AR400 Series router Documentation Set for Software Release 2.6.6 available

on the Documentation and Tools CD-ROM packaged with your router, or
from www.alliedtelesyn.co.nz/documentation/documentation.html

■ Errata to the Documentation: Software Release 2.6.6 for AR440S ADSL

Routers (Document Number C613-06011-00) available from

www.alliedtelesyn.co.nz/documentation/documentation.html

WARNING: Using a patch for a different model or software release may cause
unpredictable results, including disruption to the network. Information in this
release note is subject to change without notice and does not represent a
commitment on the part of Allied Telesyn International. While every effort has
been made to ensure that the information contained within this document and
the features and changes described are accurate, Allied Telesyn International
can not accept any type of liability for errors in, or omissions arising from the
use of this information.

54-266.rez

9-Dec-2004

54266-02.paz

246872 bytes

.

.

Simply connecting the world

2 Features in 54266-02 Patch Release Note

Some of the issues addressed in this Release Note include a level number. This
number reflects the importance of the issue that has been resolved. The levels
are:

Level 1 This issue will cause significant interruption to network services, and

there is no work-around.

Level 2 This issue will cause interruption to network service, however there

is a work-around.

Level 3 This issue will seldom appear, and will cause minor inconvenience.

Level 4 This issue represents a cosmetic change and does not affect network

operation.

From Patch 54266-02 onwards, issues for each patch are listed in severity order as per
the levels above. Enhancement PCRs are listed after Level 4 issues.

Features in 54266-02

Patch 54266-02 includes the following enhancements and resolved issues:

Level 1

PCR: 40660 Module: ATM Level: 1

When an L2TP call was activated over any ATM link (PPPoA, PPPoEoA,
IPoA e.t.c.) a router reboot would occur. This issue has been resolved.

Level 2

PCR: 40266 Module: IPSEC Level: 2

Out of sequence IPSEC packets could cause a router reboot. This issue has
been resolved.

PCR: 40272 Module: IPG Level: 2

The router learned an ARP entry for an IP address that was already
configured on one of its interfaces. This issue has been resolved, and the
receipt of spoofed ARP packets will now generate a log message.

PCR: 40284 Module: PIM Level: 2

When PIM-SM was configured and a very large number of IGMP v2 joins
were received, a router reboot would occur. This issue has been resolved.

PCR: 40311 Module: IPG Level: 2

A router reboot was observed when a large number of IP flows were being
deleted when an interface went down. This issue has been resolved.

Patch 54266-02

C613-10417-00 Rev B

Patch 54266-02 3

PCR: 40419 Module: OSPF, IPG Level: 2

If OSPF was configured using the command set ospf dyninterface=stub, to
advertise dynamic interfaces such as PPPoE interfaces as stub links, the
links were not being advertised as expected. This issue has been resolved.

PCR: 40442 Module: IPSEC Level: 2

When an IPSEC policy is used on a PPP link with iprequest=on, when the
PPP link goes down and IPSEC has traffic to transmit, IPSEC repeatedly
attempts to activate the PPP link again. The frequency of the reactivation
attempts has been reduced.

PCR: 40446 Module: DHCP Level: 2

In certain situations, if a DHCP client used a DHCP relay agent to request
IP addresses from the router acting as the DHCP server on a different
subnet, it was not be able to renew the IP address allocated to it. This issue
has been resolved.

PCR: 40450 Module: IPG Level: 2

IGMP entries were sometimes changed to static entries rather than being
deleted when IGMP leaves were received. This issue has been resolved.

PCR: 40451 Module: FIREWALL Level: 2

The "number of hits" counter in firewall's application rules was not
incremented correctly. This issue has been resolved.

PCR: 40453 Module: PIM Level: 2

Particular IP packets (unicast destination IP, but multicast destination MAC)
could result in a memory leak, which in some cases could cause the device to
stop responding to the command line. This issue has been resolved.

PCR: 40456 Module: IPG Level: 2

The enable switch learning command would fail if 802.1X port
authentication was enabled on any of the switch ports. This issue has been
resolved.

PCR: 40458 Module: IPG Level: 2

The router was accepting network RIP packets from foreign subnets. This
issue has been resolved.

Patch 54266-02
C613-10417-00 Rev B

PCR: 40465 Module: PIM6, PIM4 Level: 2

The router could reboot when a user changed the Rendezvous Point
Candidate (RPC) priority in the PIM6 module. This issue has been resolved.

4 Features in 54266-02 Patch Release Note

PCR: 40466 Module: ISAKMP Level: 2

When the router was the initiator in an ISAKMP Quick mode exchange with
a PC running Windows 2000 or Windows XP, the IPSEC communication
would not establish successfully. This was because the Windows PC set the
commit bit in the exchange, but sent the CONNECTED Notify payload in
the Quick mode exchange. However, the router was waiting for an
Informational Exchange containing a Notify payload (with the
CONNECTED Notify Message) as specified by RFC 2408. Because an
Informational message was expected, the device did not process the Quick
mode CONNECTED message, and so the exchange was never committed.

Although this behaviour is described as "not required by the IKE standard"
[http://www.microsoft.com/technet/community/columns/cableguy/
cg0602.mspx], the device will now process CONNECTED messages
received in Quick mode exchanges, to allow interoperability with other
vendors.

PCR: 40470 Module: BGP Level: 2

When BGP redistributed routes, locally imported routes were selected
rather than peer learnt routes. This issue has been resolved.

PCR: 40479 Module: OSPF Level: 2

For OSPF-originated routes, it was possible for a route to be deleted from
the IP routing table, but still be referenced by OSPF. This could cause a
router reboot when later generating a summary LSA that contained the old
route. This occurred using the reset ip command. This issue has been
resolved.

PCR: 40496 Module: DHCP Level: 2

When DHCP is enabled, it reclaims IP addresses at router startup to
determine if the addresses are in use or not. If, during this process, DHCP
was disabled then re-enabled, the router would not attempt to reclaim the
remaining IP address ranges. This would lead to the rejection of DHCP
requests for IP addresses that were still being reclaimed. This issue has been
resolved.

PCR: 40516 Module: DHCP Level: 2

While initialising a range, the router acting as a DHCP server may release a
dynamic entry incorrectly. This issue has been resolved.

PCR: 40520 Module: DVMRP Level: 2

Multicast data could not flow from PIM to DVMRP on a PIM/DVMRP
border router. This issue has been resolved.

PCR: 40530 Module: IPG Level: 2

When both Load Balancer and Firewall were configured, the very first TCP
session was established after rebooting. Subsequent TCP session startup
packets may have been routed out to an incorrect interface causing sessions
to not be established. This issue has been resolved.

Patch 54266-02

C613-10417-00 Rev B

Patch 54266-02 5

PCR: 40537 Module: BGP Level: 2

When the status of an interface changed, the BGP revaluation of IP routes
for redistribution (via the add bgp import or add bgp network commands)
was incorrect. This gave inconsistent BGP route tables depending on the
order of events. This issue has been resolved.

PCR: 40549 Module: SWI Level: 2

The receipt of two IP packets whose destination IP addresses were subnet
addresses caused the router to reboot. This issue has been resolved.

PCR: 40560 Module: DHCP Level: 2

A router reboot could occur when the DHCP server checked whether an IP
address was being used by other hosts, for example, after processing a
DHCP Discover message. This issue occurred if probe=arp was specified
for the DHCP range, and if DHCP had been disabled and then enabled. This
issue has now been resolved.

PCR: 40573 Module: LOG Level: 2

If the log module was configured to store a very large number of messages
(for example, more than 3000 messages), a watchdog timeout could occur
when the show debug command was executed. This issue has been
resolved.

PCR: 40587 Module: IPG, PIM, DVMRP Level: 2

When doing Layer 3 IP multicast routing, the router would flood traffic to
all ports in the downstream VLAN. This issue has been resolved, and now
the router will do the portmap calculation based on IGMP, PIM-SM, PIM­DM, DVMRP neighbour information, and forward the multicast traffic to
the calculated portmap.

PCR: 40588 Module: PPP, CC Level: 2

A toplogy change in a network could cause a router to attempt to activate
an ISDN call configured with direction=in when the call was already
activated. In this situation, the call was failing, and the PPP link over the call
would not come open. This issue has now been resolved.

PCR: 40592 Module: BOOTP Level: 2

If a timed-out ARP entry was renewed by BOOTP, the new entry be created
with no port association. This issue has been resolved.

PCR: 40599 Module: FIREWALL Level: 2

Patch 54266-02
C613-10417-00 Rev B

The add firewall apprule command did not correctly accept the port
parameter, so the port value was set to zero. This issue has been resolved,
and the port value is stored correctly.

PCR: 40612 Module: IPG, DNS Relay Level: 2

There was an issue in DNS Relay that resulted in a memory leak. The leak
occurred when a response to a relayed DNS request contained an
authoritative nameserver or additional information and the DNS request
was forwarded to one of those servers. There was also an issue whereby
DNS queries handled by DNS Relay would sometime result is corrupt
entries in the DNS cache. These issues have been resolved.