[Contents] [Prev] [Next] [Index] [Report an Error]

# Configuring Next-Hop Actions (C-Web Interface)

Use this action for the ingress side of the interface to specify the next IP address where the classified packets should go. You can configure next-hop actions for JUNOS filters and JUNOSe policy rules.

The captive portal feature is used to intercept HTTP requests from a subscriber to an unauthorized Web resource and redirect the requests to a dedicated Web page, the captive portal page. See Overview of Traffic Redirection.

In a captive portal environment, you would typically set up a next-hop action on a subscriber’s interface that forwards traffic to the redirect engine. In this case, you would set the next-hop address to the address of the redirect server.

When you set up redirect server redundancy, both the active and redundant redirect servers share a virtual IP address so that subscribers can always reach the active redirect server. Subscribers send requests to the virtual IP address, and the router automatically sends the request to the active redirect server by means of a static route. In this case, you would set the next-hop address to the virtual IP address.

To configure a next-hop action:

1. In the side pane, select a JUNOS filters or JUNOSe policy rules.
2. From the Create new list, select Next Hop. Type a name for the action, and click OK.
3. Enter information as described in the Help text in the main pane, and click Apply.

#### Related Topics

- Configuring Next-Hop Actions (SRC CLI)
- Configuring Next-Interface Actions (C-Web Interface)
- Configuring Next-Rule Actions (C-Web Interface)

[Contents] [Prev] [Next] [Index] [Report an Error]