Summary of the content on the page No. 1
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 Table 1.
Table 1: Patch file details for Patch 54266-02.
54-266.rez
Base Software Release File
Patch Release Date 9-Dec-2004
54266-02.paz
Compressed Patch File Name
246872 bytes
Compressed Patch File Size
This
Summary of the content on the page No. 2
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 iss
Summary of the content on the page No. 3
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 transmi
Summary of the content on the page No. 4
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 Notif
Summary of the content on the page No. 5
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 c
Summary of the content on the page No. 6
6 Features in 54266-02 Patch Release Note PCR: 40621 Module: PING Level: 2 In previous releases, ping poll commands only required entry of the first three characters of the Source IP Address (sipaddress) parameter. For example, add ping poll=1 ip=192.168.2.10 sip=192.168.2.1. Subsequent releases required entry of the first four parameters. This issue has been resolved, so that it is once again possible to enter just the first three characters. PCR: 40646 M
Summary of the content on the page No. 7
Patch 54266-02 7 PCR: 40417 Module: OSPF Level: 3 When LS Acks (Link State Advert acks) were received, they were compared against the transmitted LSA (Link State Advert). If it was the same, the LSA was removed from the re-transmission list. The algorithm used in this check has been changed to be compliant with the algorithm specified in section 13.1 of RFC2328, to determine if the LS Ack received is the instance as the LSA. PCR: 40428 Module: IP, FILTER
Summary of the content on the page No. 8
8 AR441S ADSL Router Hardware Platform Patch Release Note Level 4 PCR: 40441 Module: IPG, VRRP Level: 4 If VRRP was enabled and a reset ip command was issued followed by a disable vrrp command, then the device would still reply to pings, even though the device was no longer the VRRP master. Duplicate echo replies were seen on the device sending the pings. This issue has been resolved. Enhancements PCR: 40521 Module: TACACS+ T
Summary of the content on the page No. 9
Patch 54266-02 9 Main system Main features of the AR440S routers are: ■ 300 MHz RISC processor. ■ 64 MBytes of SDRAM. ■ 16 MBytes of flash memory (1 MByte reserved for boot block code). ■ 5 x 10/100 Mbps full duplex, Layer 2 switched Ethernet LAN ports. All LAN ports have Auto-MDI, however if Auto-MDI is turned off, then all ports are hardwired as MDI-X. Software can also force a port to either MDI or MDI-X. 802.1Q tagged VLANs are supported. ■ 1 x ADSL Annex B port ■ 1 x asynchronous DTE po
Summary of the content on the page No. 10
10 Features in 54266-01 Patch Release Note Table 2: Patch file details for Patch 54266-01. 54-266.rez Base Software Release File GUI Resource File Names d440Se14.rsc (AR440S) d441Se14.rsc (AR441S) 21-Oct-2004 Patch Release Date 54266-01.paz Compressed Patch File Name 161304 bytes Compressed Patch File Size Patch 54266-01 includes the following enhancements and resolved issues: PCR: 40563 Module: ADSL This patch, together with the base software release, supports
Summary of the content on the page No. 11
Patch 54266-02 11 Error (3005271): Internal Error: Failed to set interface This issue has been resolved. It is now possible to add an IP address to a VCMux encapsulated ATM interface with inversearp set to off. This is known as RFC 1483 routing. RFC 1577, classical IP and ARP over ATM, still requires the ATM interface to be LLCSNAP encapsulated. Patch 54266-02 C613-10417-00 Rev B
Summary of the content on the page No. 12
12 Features in 54266-01 Patch Release Note PCR: 40613 Module: SYN Level: 3 When the Test facility was used to test an AR023 synchronous PIC interface, it sent some debugging messages, "SYNCheckInterface", to the console port. This issue has been resolved: the Test facility no longer sends these messages. PCR: 40618 Module: Firewall Level: 3 When NAT was enabled and the router was configured to pass FTP requests to a server i
Summary of the content on the page No. 13
Patch 54266-02 13 PCR: 40647 Module: ETH Level: 2 When a virtual Eth interface was created over ATM, for example, using the command: create eth=0 over=atm=0.1 and a VPN configuration was applied directly to that Eth interface, the router ran out off buffers and caused a fatal exception under heavy reception load. This issue has been resolved: a limit has now been set so that the virtual Ethernet interfaces, like physical Eth interfaces, stop reception by dro
Summary of the content on the page No. 14
14 Features in 54266-01 Patch Release Note Patch 54266-02 C613-10417-00 Rev B
