Readme for system software 6.3.4 PATCH 4 ======================================== ======================================== The following changes have been made to our software since the release of system software 6.3.4. They have been included in system software 6.3.4 PATCH 4 which is available from BinTec's web server for all X-Generation Routers. 1. CAPI - Disconnect (ID 2587) ================================================================= During the establishment of an incoming CAPI call, the router sends an alert packet containing channel selection information. This should not be the case if the original channel selection is accepted and may cause the ISDN switch to disconnect the call. The problem has been solved. 2. CAPI - Wrong Window Size (ID 2729) ================================================================= During the establishment of an incoming CAPI call, the router sets the Window Size to a value of "0" and fails to accept the call. The problem has been solved. 3. CAPI - Wrong HLC Element (ID 2733) ================================================================= In some cases the HLC Element is transferred wrong by the remote CAPI. The problem has been solved. 4. PPP - biboDialLocalNumber is only used for X.25 (ID 2576) ================================================================= The Parameter biboDialLocalNumber of the bibodialtable is only used by connections with encapsulation X25. The problem has been solved. 5. PPP - MS-CHAP V2 RADIUS Authentication (ID 2323) ================================================================= Authentication with MS-Chap V2 via Radius Server is unseccessful. The problem has been solved. 6. PPTP - GRE Send Window Handling (ID 2623) ================================================================= After creating a VPN tunnel between a BinTec router and a Windows XP client, packets may be delayed for an exceptional long time. Some packets may be lost, also. The problem is due to a change in the handling of the GRE Send Window Size in the Microsoft GRE implementation. It has been solved. The PPTP Profile can now be configured to comply with the Microsoft implementation. For this, it is necessary to disable GRE Window Size Adaptation the pptpProfileTable by setting the variable GreWindowAdaption to "disabled". Additionally you should set the pptpProfileMaxSWin variable to a value of "256". 7. TCP - MSS Clamping not Functional (ID 2731 and 2792) ================================================================= TCP MSS (Maximum Segment Size) Clamping is not fully functional. This may significantly slow down data transfer, and may even lead to a connections being dropped because of a time out. The problem has been solved. !! Updating the system software alone does not change the active configuration. In order for the new MSS Clamping behavior to work in existing configurations, set the ipExtIfTcpMssClamping variable to a value of "-1" for all existing PPP interfaces. !! 8. IPSec - IPSec Callback Leads to Stack Trace (ID 2810) ================================================================= Using IPSec Callback can cause a stack trace on the responder (passive) side (this is the peer that reacts to an incoming ISDN call and that initiates the tunnel creation). The problem has been solved.