Based on NBR_RGOS 11.9(6)B17P2, this version resolves the following issues.
Bug ID |
Description |
After a user is authenticated and goes online, the traffic is reported to Ruijie Cloud. When the authenticated user is still online, used traffic data displayed on Ruijie Cloud is occasionally cleared. |
|
When the configuration of an L2TP IPsec hub site is modified, the configuration displayed on the web UI is incorrect. |
|
When a VPN spoke site is added, the password prompt is inconsistent with the actual password requirement. |
|
The device cannot execute the show content-audit syslog status command. As a result, the syslog server configuration displayed on the web UI is incorrect. |
|
In a DHCP DDI relay scenario, IPAM static address binding does not take effect. The DHCP server does not deliver the IP address to the terminal based on the static binding but allocates another address to the terminal. |
|
The verification code image and password change button are not displayed on the RG-SSLVPN login page. |
|
After an IP address is configured for port 8F on an RG-NBR6200 series product, the port configuration on the Interface Conversion page still indicates that no address is configured. |
|
During SMS two-factor authentication on RG-SSLVPN, SMS messages cannot be received due to an incompatible password format. |
|
Backend VPN configurations cannot be obtained in a batch on the web UI, and the VPN configuration of the hub site cannot be displayed. |
|
When the SIP server is deployed on an extranet, the client cannot make a call. |
|
In an L2TP VPN hub-spoke scenario, the command syntaxes for configuring L2TP tunnel authentication passwords in the new and old versions are incompatible, resulting in an L2TP tunnel negotiation failure. (Old version: RGOS 11.9(6)B17P1 or earlier; new version: later than RGOS 11.9(6)B17P1.) |
|
After the authentication password on the spoke side of an L2TP IPsec/L2TP VPN tunnel is changed to the correct value, tunnel negotiation still fails. |
|
After the L2TP tunnel authentication password is configured on the web UI, an exception occurs in underlying system configuration. |
|
The router does not support voucher authentication and rate limiting on Ruijie Cloud. |
|
The switch components of some batches of devices are abnormal, which may incur unexpected device restart. |
|
1125717 |
If voucher and account user information is imported from Ruijie Cloud to the device, an exception occurs on Ruijie Cloud, and the voucher and account user information is inconsistent. As a result, voucher user information is lost after the import. |
1110132 |
The historical traffic report does not display data of external users and user groups. |
1117710 |
After DHCP static binding is configured and the secondary DNS is modified, the secondary DNS configuration is not displayed on the web page. |
1114082 |
The logic for delivering the interfaces configuration is optimized. |
1112587 |
The user management module of the device has high requirements on password strength by default. As a result, voucher users with weak passwords on Ruijie Cloud cannot be imported to the device. |
1111996 |
When IPv6 traffic is used to access the local device, the device buffer leaks after the IPv6 fragmented packet reassembly times out. |
1111230 |
The device does not have an automatic aging mechanism for flows with inconsistent forward and return paths. |
1109831 |
The gateway is deployed at the intranet border, and PCs on the intranet use the active mode to connect to an external FTP server. In this case, files cannot be downloaded. |
1108038 |
The Prevent Share function does not take effect. |
1104362 |
The display of the DHCP IPAM page on the web UI is incorrect. |
1094055 |
The IPv4 or IPv6 protocol type needs to be set for the web ping function to take effect. |
1109268 |
If the data directory of the RG-NBR2100G-E is fully occupied by the database logDhcp.db of the DHCP module, an exception occurs on the device. |
1079601 |
The device does not support multiple LAN interfaces on the same network segment. |
1093951 |
The device needs to support WiFiDog authentication. |
1114874 |
The IPv6 ping function is abnormal. |
1111171, 1129600 |
After the voucher rate limit function is configured, if the length of the user group information delivered by Ruijie Cloud is longer than 32 bytes, a core dump occurs on the flow control component. |
1095370 |
The web operation logs cannot be retained for six months. |
1163802 |
Some YouTube traffic cannot be properly identified. |
1171495 |
The configuration item name displayed on the web-based authentication configuration page is incorrect. |
1204797 |
After the DHCP service is manually disabled, the DHCP service is automatically enabled again upon interface configuration modification. |
1208231, 1207728 |
A command injection vulnerability exists in CLI commands. |
1208467 |
The function of identifying QUIC traffic is disabled by default. A CLI command needs to be added to enable the function of identifying QUIC traffic. |
1207687 |
The device restarts or crashes due to a QUIC packet processing exception. |
1160308 |
After a blocklisted website is configured in a behavior management policy, Google Chrome of the latest version is used to access the blocklisted website. In this case, URL/domain name blocking does not take effect. |
1226563, 1226562, 1215846, 1212615 |
Security vulnerabilities exist. |
1222084 |
The DHCP server should support Option 43 delivery in ASCII format. |
1219552 |
The Blocked Record page needs to be added for displaying detailed blocking records of specific behavior management policies based on the specified IP address. |
1213345 |
On a device that functions as both the VPN hub site and VPN spoke site, when the peer address of the IPsec tunnel is set to a domain name for the VPN spoke site, the IPsec tunnel fails to be established. |
1210449 |
When a domain name is configured for link detection, a domain name with a hyphen (-) cannot be configured, and the prompt message is unclear. |
1210336 |
For RG-NBR6200 series devices, when a core dump occurs on the QUIC identification module of application identification, the crash stack information cannot be recorded. |
Ruijie Networks websites use cookies to deliver and improve the website experience.
See our cookie policy for further details on how we use cookies and how to change your cookie settings.
Cookie Manager
When you visit any website, the website will store or retrieve the information on your browser. This process is mostly in the form of cookies. Such information may involve your personal information, preferences or equipment, and is mainly used to enable the website to provide services in accordance with your expectations. Such information usually does not directly identify your personal information, but it can provide you with a more personalized network experience. We fully respect your privacy, so you can choose not to allow certain types of cookies. You only need to click on the names of different cookie categories to learn more and change the default settings. However, blocking certain types of cookies may affect your website experience and the services we can provide you.
Through this type of cookie, we can count website visits and traffic sources in order to evaluate and improve the performance of our website. This type of cookie can also help us understand the popularity of the page and the activity of visitors on the site. All information collected by such cookies will be aggregated to ensure the anonymity of the information. If you do not allow such cookies, we will have no way of knowing when you visited our website, and we will not be able to monitor website performance.
This type of cookie is necessary for the normal operation of the website and cannot be turned off in our system. Usually, they are only set for the actions you do, which are equivalent to service requests, such as setting your privacy preferences, logging in, or filling out forms. You can set your browser to block or remind you of such cookies, but certain functions of the website will not be available. Such cookies do not store any personally identifiable information.
Contact Us
How can we help you?