Compare Products
Hide
VS
Testing Project | APP dummy provisioning |
Testing Purpose | EG quick setup configuration via Ruijie Cloud App, and online on Ruijie Cloud |
Testing procedure and expected results: | 1. Power on the EG, the AP connect to the EG LAN interface. 2. After AP power on, The AP will broadcast the default SSID name to RJ-xxxxxx (xxxxxx is the last six digits of EG2100-P SN) 3. Launch Ruijie Cloud APP and Tap Project menu, click Quick Setup to start configuration 4. App will open the EG2100-P initial configuration wizard and log in to the EG2100-P with default account (Username: admin, Password: admin).
5. Click Start, and set the network SSID. After the network is created, then enter the network and click Add Device to add AP and EG2100-P through scanning the QR code (AP SN/MAC) on the back of the device. Note: When adding an EG device, you need to enter the WEB management password of the EG device. |
Measured record: | |
Testing conclusion: |
|
Testing project: | DHCP server |
Testing purpose: | EG as DHCP Server, Clients can get DHCP IP from EG normally |
Testing procedure and expected results: | 1. Enable the DHCP server in EG and configure the DHCP pool for AP and STA with different VLANs. Add the sub interfaces with different VLAN in LAN Configure the DHCP pool 2. AP connect to the EG and configure the STA VLAN, AP and STAS can get the correct IP address. Configure the STA VLAN via Ruijie Cloud: Check the DHCP user list |
Measured record: | |
Testing conclusion: |
|
Testing project: | WAN uplink (This step is covered during App provisioning, at here you can change WAN Uplink with other ways, such as PPPoE or Static IP) |
Testing purpose: | WAN PPPoE, Static or DHCP IP as Internet Uplink |
Testing procedure and expected results: | 1. Configure the EG uplink connection mode (PPPoE/Static/DHCP) and connect it correctly. EG can access the Internet correctly.
2. Connect to EG with wireless and wire user, an access the Internet correctly. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Dual WAN uplink |
Testing purpose: | EG support two WAN Uplink to access internet, and load balance |
Testing procedure and expected results: | 1. Configure the EG uplink connection mode (PPPoE/Static/DHCP). 2. Add the sub interface with different vlan in the WAN, configure the account info in different sub interface. Add the sub interfaces and configure the username/password 3. Connect the WAN correctly and enable the load balance. Enable the load balance Set the interface’s weight Configure the default route Add the NAT outside interface and NAT rule 4. Monitor the load balance in Traffic Monitoring |
Measured record: | |
Testing conclusion: |
|
Testing project: | Internet connectivity |
Testing purpose: | Client should connect to Internet successfully |
Testing procedure and expected results: | 1. Make sure the EG uplink connection is ok. 2. The AP access to the EG, obtains an ip address from the EG, and releases the SSID. The STAs can browse the webpage and the video. 3. The PC accesses the EG to obtain an IP address, and can browse the webpage and the video normally. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Block access |
Testing purpose: | Block Facebook access |
Testing procedure and expected results: | 1. Add the Facebook Applications to App Blacklist 2. STA connect to EG access to the Facebook with APP and Website, it will be blocked, other websites can be accessed successfully. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Blacklist |
Testing purpose: | Add user(Name/IP) to blacklist |
Testing procedure and expected results: | 1. Add the users with name or IP range, then add the user to blacklist. 2. STA connect to EG with the user in blacklist and try access to the internet, he will be blocked. |
Measured record: | |
Testing conclusion: |
|
Testing project: | EG WEB configuration |
Testing purpose: | Cloud open EG WEB and access successfully |
Testing procedure and expected results: | 4 Make sure the EG online on Cloud.
5 Connect the eWeb in Ruijie Cloud, it will create the tunnel to EG from Ruijie Cloud.
6 Now you can configure the EG by eWeb from Ruijie Cloud. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Monitoring(Ruijie cloud) |
Testing purpose: | EG overview status and WAN/LAN status can be monitoring on Ruijie Cloud WEB |
Testing procedure and expected results: | 1. Ruijie cloud can monitor the device status, including device details, traffic information, current user, interface status and alarm. The CWMP interface can work normally. 2. Ruijie Cloud support grouping function, report log function is normal 3. Ruijie Cloud can upgrade the device version. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Monitoring(Ruijie cloud APP) |
Testing purpose: | Ruijie Cloud App(IOS or Android) monitoring EG status(IOS and Android) |
Testing procedure and expected results: | 1. Ruijie cloud can monitor the device info, system status, clients status, applications status and log. 2. Using the Ruijie Cloud APP to add, delete, and configure devices. You can synchronize them under the same account of the Ruijie Cloud. 3. Support IOS or Android version. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Synchronize Voucher/Account to EG |
Testing purpose: | Use Cloud Voucher Code to log in with Portal WiFi (SSID) |
Testing procedure and expected results: | 1. EG is installed and online on the Ruijie Cloud, the Ruijie Cloud operates the voucher user (addition and deletion), which can be correctly synchronized to the EG. Create the package Print voucher Enable the auth integration with Cloud Show the users synced from Cloud 2. Enable the local authentication on EG, The users can connect to external network by voucher authentication Add the authentication IP range Show the online info This voucher status is Actived |
Measured record: | |
Testing conclusion: |
|
Testing project: | Voucher |
Testing purpose: | Different Voucher Profile with different speed limit |
Testing procedure and expected results: | 1. Configure the different voucher profile with different speedlimit on Ruijie Cloud. Configure the speed limit 2. Sync the voucher account to EG. 3. STA access with different voucher code and check the speed test result whether the same as Voucher profile configured. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Seamless |
Testing purpose: | Enable and disable Seamless |
Testing procedure and expected results: | 1. EG is installed and online on the Ruijie Cloud, the Ruijie Cloud operates the Voucher user (addition and deletion), which can be correctly synchronized to the EG. 2. Enable and disable seamless on EG. Close means disable seamless, seamless MAC bypass means enable seamless with MAC 3. Test the seamless with different STAs, record the result. First time STA login to online, then next time STA come back the network (or you can kick out the user on EG), he will be online automatically. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Compatibility | |||||||||||||
Testing purpose: | Compatibility with STAs | |||||||||||||
Testing procedure and expected results: | 1. Configure the captive portal template on Cloud and synchronize it to EG 2. The user can select login options and customize the portal page 3. Enable local auth on EG, including account, voucher and one-click authentication 4. Use different STAs including laptop and mobile phone (iOS and Android), and make sure the portal page pops up automatically and is consistent with the template on Cloud | |||||||||||||
Measured record: |
| |||||||||||||
Measured record: | ||||||||||||||
Testing conclusion: |
| |||||||||||||
Testing project: | Log audit |
Testing purpose: | User access log (such as visited URL, source/dest IP, etc.) should send out via HTTP to Log Server |
Testing procedure and expected results: | 1. Enable the log policy on EG and set the log level. 2. Configure the log server (HTTP). 3. Monitor the log content on server. |
Measured record: | |
Testing conclusion: |
|
Testing project: | Establish VPN |
Testing purpose: | The HQ and branch gateways use static IP addresses. The HQ gateway needs to verify the IP address of the branch gateway. |
Testing procedure and expected results: | 1. Check the network topology. 2. Configure the branch. 1) Complete wizard-based setup to meet basic Internet access requirements of users in the HQ and branch. If the users can access the Internet, check whether the next hop address is configured for the WAN interface. 2) Configure IPsec for the branch. Choose Network > VPN and click Configure. Select Branch, and click Next.
3. Configure the HQ. 1) Complete wizard-based setup to implement basic Internet access service of the HQ router. 2) Configure IPsec for router A in the HQ. Choose Network > VPN and click Configure. Select Headquarter, and click Next.
Select Branch, and click Next. Select IPsec, and click Next.
4. Verification 1) Choose Network > VPN, and click the Topo tab to view the configuration.
|
Measured record: | |
Testing conclusion: |
|
Testing project: | Establish VPN |
Testing purpose: | Branch and clients create the L2TP over IPsec VPN with HQ. |
Testing procedure and expected results: | 1. Check the network topology. 2. Configure the branch. 1) Complete wizard-based setup to meet basic Internet access requirements of users in the HQ and branch. If the users can access the Internet, check whether the next hop address is configured for the WAN interface.
2) Configure IPsec for the branch. Choose Network > VPN and click Configure. Select Branch, and click Next.
3) Configure the HQ. Complete wizard-based setup to implement basic Internet access service of the HQ router. Configure L2TP IPsec for router A in the HQ. Choose Network > VPN and click Configure. Select Headquarter, and click Next.
Select Mobile User, and click Next.
Select L2TP IPsec, and click Next. Enter the basic information, client IP range and DNS Enable the branch and add the branch network Add the account
4) Verification Choose Network > VPN, and click the Topo tab to view the configuration. HQ review Branch review |
Measured record: | |
Testing conclusion: |
|
Testing project: | Mobile App Caching |
Testing purpose: | Resource cache refers to synchronizing resource from the specified server to a device. Afterwards, users can get the resource directly from the device without crossing WAN.
Resource cache can reduce bandwidth usage and save users from waiting for access. |
Testing procedure and expected results: | 1. Enable the cache function, the device will be restarted:
2. Enable resource cache:
3. Paste the download link of the resource to the “Resources Address1”:
4. Check the cache file:
5. Verification 1) Download the file via browser:
2) The file is downloaded within the LAN. |
Measured record: | |
Testing conclusion: |
|
Category | Test Item | Description | Pass | Fail |
1. Mobile App Provisioning | Mobile App Quick Provisioning | EG quick setup via Ruijie Cloud App, and device should online on Cloud |
|
|
2. Basic Network Testing | DHCP Sever | Enable service DHCP and create IP Pool Test from laptop or wifi |
| |
DHCP Client | Only apply on WAN interface |
|
| |
WAN Uplink | WAN PPPoE or DHCP as Internet Uplink |
|
| |
DNS Proxy | Enable EG as DNS Server |
|
| |
Dual WAN Uplink (Optional) | EG support two WAN Uplink to access internet, and load balance |
|
| |
Internet Connectivity | Client should connect to Internet successfully |
|
| |
3. Online Behavior Management | App Blacklist | Block Facebook Keyword : Facebook_Messenger |
|
|
| Block Youtube |
|
| |
Block User Access | Adding user (Name/IP) to blacklist |
|
| |
Block chat / messenger application | |
|
| |
| Login EG’s WEB via Cloud | Opening EG WEB via Ruijie Cloud Web UI and access successfully |
|
|
4. Cloud & App Monitoring | Cloud (Web UI) Monitoring | Monitoring EG device and WAN/LAN status on Ruijie Cloud WEB |
|
|
Ruijie Cloud App Monitoring | Monitoring EG device and WAN/LAN status Ruijie Cloud App (IOS or Android) |
|
| |
5. Authentication Acceleration (EG Offload) | Synchronize Voucher/Account to EG | Using Ruijie Cloud created Voucher to log in with Portal WiFi (SSID) |
|
|
Speed Limit | Using different Voucher Profile with varies speed limit, and create two Voucher code to log-in to get different speed control |
|
| |
Seamless Authentication | User can seamless online directly at next time connected WiFi without login again |
|
| |
Compatibility test of EG local authentication | Compatibility test of EG local authentication |
|
| |
6. Internet Access Log Audit | User internet access log checking | User access log (such as visited URL, source/dest IP, MAC, etc.) should send out via HTTP/FTP to Ruijie provided Log Server |
|
|
7. IPSEC VPN | IPSEC VPN | The HQ and branch gateway use static IP addresses. The HQ gateway needs to verify the IP address of the branch gateway. |
|
|
8. ResourceCache | Mobile App Caching | Resource cache can reduce bandwidth usage and save users from waiting for access. |
|
|
Note: Before PoC, please check whether theEG has been upgrade to the latest version by execute command “show version detail”, the example is shown asbelow:
How do you like this document ?
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?