Allied Telesis Patch 54266-02 Manual de usuario Pagina 8

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 16
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 7
8 Features in 54266-02 Patch Release Note
Patch 54266-03
C613-10417-00 Rev C
DM, DVMRP neighbour information, and forward the multicast traffic to
the calculated portmap.
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.
If a timed-out ARP entry was renewed by BOOTP, the new entry be created
with no port association. This issue has been resolved.
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.
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.
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.
For both RIP and OSPF, the router was adding a route with it own IP
address for NEXTHOP address. This issue has been resolved.
L2TP did not handle a change to its peer's UDP source port. If the tunnel
went through a NAT box and that NAT box was reset, then it was possible
for the remote port to change. L2TP should be able to handle this case and
update the tunnel accordingly. A similar problem occurs when a IPsec
NAT-T session (in transport mode) is re-negotiated. IPsec NAT-T uses port
translation to distinguish between multiple clients behind a NAT box. If the
IPsec session is renegotiated then the translated source port that IPsec
passes to L2TP will change. L2TP must be able to handle this case, if it
doesn't then the session will be lost. This issue has been resolved.
The router would not respond to the setting of the maxqueueseverity
parameter when configuring logging. This issue has been resolved.
PCR: 40588 Module: PPP, CC Level: 2
PCR: 40592 Module: BOOTP Level: 2
PCR: 40599 Module: FIREWALL Level: 2
PCR: 40612 Module: IPG, DNS Relay Level: 2
PCR: 40621 Module: PING Level: 2
PCR: 40646 Module: OSPF, IPG Level: 2
PCR: 40658 Module: L2TP Level: 2
PCR: 40668 Module: FFILE Level: 2
Vista de pagina 7
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Comentarios a estos manuales

Sin comentarios