An engineer is deploying a wireless network. Portal authentication is used for guest access, the authentication point is the wireless controller, and the authentication server uses iMaster NCE…

Question

Exhibit

Options

• AThe port number for processing Portal protocol packets on the device is 50200.
• BThe IP address for communication between the device and the Portal server is 10.10.10.254
• CThe URL redirected to the user will contain the ssid name.
• DThe IP address of the Portal server is 10.23.200.1

• A
  17% (3)
• B
  83% (15)

Explanation

Options B, C, and D are correct because they accurately reflect standard Huawei Portal authentication configuration parameters visible in the wireless controller's Portal server template: the device source IP (10.10.10.254) is the wireless controller's interface address used for communicating with the Portal server, the Portal server IP (10.23.200.1) is the iMaster NCE-Campus address, and when SSID URL parameters are enabled in the template, the redirect URL dynamically appends the SSID name so the Portal page can customize the authentication experience.

Option A is wrong because 50200 is the Portal server's listening port (the port on iMaster NCE-Campus), not the port the device itself uses to process incoming Portal protocol packets - these are two distinct ports in the Huawei Portal architecture, and confusing server-side vs. device-side ports is a common trap.

Memory tip: Think of the Portal flow as a three-actor play - Device, Portal Server, Auth Server. For each config value, ask "whose address/port is this?" The device IP (B) belongs to the controller, the server IP (D) belongs to iMaster NCE-Campus, and URL parameters (C) are what the redirect carries to the Portal page. If an option flips ownership (like claiming the server's port belongs to the device), it's wrong.

No community discussion yet for this question.