Votos - 2, Puntuación media: 4.5
(
)
)
|
Resumen del manual
If the fragments could not be reassembled, the packet was dropped. Reassembly could only occur if the combined packet (IP header, and protocol header, and data) was no more than 1800 bytes. An additional limit of no more than eight fragments was also imposed. This PCR implements enhanced fragment handling for Firewall and IP NAT. Each module can now be configured to process fragmented packets of specified protocol types without needing to reassemble the packet. The number of fragments a packet may consist of is also configurable. This enhanced fragment handling is disabled by default. To enable enhanced fragmentation for Firewall, use the command: ENABLE FIREWALL POLICY=policy_name FRAGMENT={ICMP|UDP|OTHER} To enable enhanced fragmentation for IP NAT, use the command: ENABLE IP NAT FRAGMENT={ICMP|UDP|OTHER} To disable enhanced fragmentation for Firewall, use the command: DISABLE FIREWALL POLICY=policy_name FRAGMENT={ICMP|UDP|OTHER} Patch 86222-25 for Software Release 2.2.2 C613-10319-00 REV X Patch Release Note To disable enhanced fragmentation for IP NAT, use the command DISABLE IP NAT FRAGMENT={ICMP|UDP|OTHER} To configure the number of fragments permitted per packet for Firewall, use the command: SET FIREWALL FRAGMENT=8...50 To configure the number of fragments permitted per packet for IP NAT, use the command: SET IP NAT FRAGMENT=8...50 TCP has been excluded from this enhancement because TCP has the MSS (Maximum Segment Size) parameter for segment size control. Also, for PPPoE interfaces with a reduced MTU of 1492, a previous enhancement in PCR 02097 ensures that TCP MSS values in sessions carried by a PPPoE interface are clamped to a value that prevents fragmentation. PCR 02116 Module: IPG PING Network affecting: No When pinging to a remote IP address with two or more different cost routes, if the preferred route became unavailable, the ping failed to switch to the less preferred route until the ping was stopped and restarted. This issue has been resolved. PCR: 02371 Module: FIREWALL Network affecting: No When the system time was set to a time that was before or significantly after the current time, Firewall sessions were prematurely deleted. This issue has been resolved. PCR: 03011 Module: OSPF Network affecting: No When the router priority was changed on a dynamic OSPF interface, the new priority did not appear in the output of the SHOW OSPF NEIGHBOUR command on neighbouring routers. The new priority only showed after the RESET OSPF command was executed on the neighbouring routers. This issue has been resolved. PCR: 03026 Module: IPG Network affecting: No After setting the IGMP query timer with the SET IP IGMP command, and saving the configuration, the IGMP Other Querier timeout was not set to the correct value after a restart. This issue has been resolved. PCR: 03027 Module: DHCP Network affecting: No Entries in the process of being reclaimed as static entries (and waiting for the remote IP to become routable), were disrupting the reclaim process. This prevented further entries from being reclaimed. DHCP static entries are now fully subject to normal reclaim processing. PCR: 03032 Module: SWI Network affecting: No If the ENABLE IP IGMP command was executed before the ENABLE SWITCH L3FILTER command, Layer 3 filtering did not discard packets destined for the CPU. This issue has been resolved. PCR: 03035 Module: OSPF Network affecting: No Link state advertisements could incorrectly show an area as a stub area. This happened during the time when a Direct Route (DR) was removed from a configuration and before a Direct Backup Route (BDR), or an Other Direct Route (Other DR) was elected. This issue has been resolved. Patch 86222-25 for Software Release 2.2.2 C613-10319-00 REV X Patch 86222-25 For Rapier Switches and AR800 Series Modular Switching Routers PCR: 03040 Module: IPG Network affecting: No Sometimes IP flows were not deleted correctly when both directions of the flow were in use. This issue has been resolved. PCR: 03065 Module: SWI Level: 2 When the TX cable was unplugged from a fibre port the operating status was incorrectly reported as UP. This issue has been resolved. PCR: 03067 Module: DHCP Level: 1 When replying to a DHCP REQUEST that had passed through a DHCP relay, the broadcast bit of DHCP NAK messages was not being set. This issue has been resolved in accordance with RFC2131. PCR: 03080 Module: DVMRP DVMRP was not updating the downstream forwarding state correctly. This issue has been resolved. PCR: 03095 Module: DHCP Level: 2 DHCP policies are no longer stored in alphabetical order in the DYNAMIC CONFIGURATION script because this did not work when the DHCP INHERIT parameter was used. PCR: 03122 Module: SWI Level: 2 When a static ARP was added to a trunk group, a software restart could occur. This issue has been resolved. Features in 86222-23 Patch file details are listed in Table 3. Table 3: Patch file details for Patch 86222-23. Base Software Release File 86s-222.rez Patch Release Date 1...