Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All
Example: HTTP Service Attached to a Static Interface
The following example shows an HTTP service set attached to a static interface:
[edit interfaces ge-1/0/1]root@hostr# show
unit 0 {family inet {service {input {service-set http-redirect-walled;}output {service-set http-redirect-walled;}}address 10.1.3.2/24;}}
The following example uses a service filter as a walled garden by defining a rule named redirect, referencing the rule in a profile named http-redirect, configuring a service set named http-redirect that references the http-redirect captive portal content delivery profile, and attaching the http-redirect service set to static interface ge-1/0/1.0.
[edit services]
captive-portal-content-delivery {rule redirect {match-direction input;term t1 {from {destination-address {100.0.1.1/32;}}then {redirect http://www.google.com;}}}profile http-redirect {cpcd-rules redirect;}}
service-set http-redirect {captive-portal-content-delivery-profile http-redirect;interface-service {service-interface ms-1/0/0;}}
[edit interfaces ge-1/0/1]
unit 0 {family inet {service {input {service-set http-redirect service-filter walled;}output {service-set http-redirect;}}address 10.1.3.2/24;}}
The following example shows an IPv6 static service attachment:
[edit interfaces ge-1/0/1]
unit 0 {family inet6 {service {input {service-set http-redirect6 service-filter walled6;}output {service-set http-redirect6 service-filter walled6;}}address 2001:2002::1;}}
This example configures the service filter for walled6:
firewall {family inet6 {service-filter walled6 {term google {from {destination-prefix-list {google6;}}then skip;}term http {from {destination-port [ 80 8080 443 ];}then service;}term skip {then skip;}}}}
