Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Example: Walled Garden as an HTTP Service Rule

    HTTP service rule configuration resides under the services hierarchy and uses the captive portal and content delivery (captive-portal-content-delivery) service. The following example shows a walled garden configured as an HTTP service rule:

    [edit services captive-portal-content-delivery]
    rule walled-garden {match-direction input-outputterm 1 {from {destination-address 100.20.2.3/32; ## captive portaldestination-port 80;}then {accept;}}}

    When a remote HTTP redirect server is used, you need to configure an HTTP service rule to rewrite the IP-DA of incoming HTTP requests on the service router so that the requests reach the remote HTTP redirect server before being redirected to a captive portal. If the destination port is not specified, the default behavior is determined by the rewrite configuration. If no rewrite configuration is available, the destination port is not rewritten. The following example shows a configuration for IP-DA rewrite:

    [edit services captive-portal-content-delivery]
    rule ipda-rewrite {match-direction input-output;term 1 {from {applications junos-http;}then {rewrite destination-address 100.20.2.10; # this is the remote# redirect server.}}}

    Published: 2013-02-11