Patch | 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,
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
PCR: 40599 | Module: FIREWALL | Level: 2 |
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.
Patch
