Administrator: /* Example */

2015-01-29T12:32:49Z

Example

← Older revision		Revision as of 12:32, 29 January 2015
Line 181:		Line 181:
	Now if you look at walled garden menu you will see dynamic entry for object we just added		Now if you look at walled garden menu you will see dynamic entry for object we just added
	<pre>		<pre>
	[admin@~~493G~~] /ip hotspot walled-garden> print detail		[admin@cablefree] /ip hotspot walled-garden> print detail
	Flags: X - disabled, D - dynamic		Flags: X - disabled, D - dynamic
	0 D ;;; www.paypalobject.com		0 D ;;; www.paypalobject.com

Administrator at 12:32, 29 January 2015

2015-01-29T12:32:31Z

← Older revision		Revision as of 12:32, 29 January 2015
Line 189:		Line 189:
	Also dynamic firewall and NAT rules are added to allow paypalobject.com resolved address		Also dynamic firewall and NAT rules are added to allow paypalobject.com resolved address
	<pre>		<pre>
	[admin@~~493G~~] /ip firewall filter> print dynamic		[admin@cablefree] /ip firewall filter> print dynamic
	Flags: X - disabled, I - invalid, D - dynamic		Flags: X - disabled, I - invalid, D - dynamic
	...		...
Line 200:		Line 200:
	</pre>		</pre>
	<pre>		<pre>
	[admin@~~493G~~] /ip firewall nat> print dynamic		[admin@cablefree] /ip firewall nat> print dynamic
	Flags: X - disabled, I - invalid, D - dynamic		Flags: X - disabled, I - invalid, D - dynamic
	...		...

Administrator: Created page with "{{Versions | v3, v4, v5+}} TOC ==Walled Garden==
Sub-menu: `/ip hotspot walled-garden`

HTTP walled-garden menu permits..."

2015-01-29T12:31:10Z

Created page with "{{Versions | v3, v4, v5+}} __TOC__ ==Walled Garden== Sub-menu: <code>/ip hotspot walled-garden</code> HTTP walled-garden menu permits..."

New page

{{Versions | v3, v4, v5+}}
__TOC__

==Walled Garden==

Sub-menu: <code>/ip hotspot walled-garden</code> 

 

HTTP walled-garden menu permits authentication bypass settings for HTTP and HTTPs resources.

Wildcard properties (dst-host and path) match a complete string (i.e., they will not match "example.com" if they are set to "example"). Available wildcards are '*' (match any number of any characters) and '?' (match any one character).
Regular expressions are also accepted here, but if the property should be treated as a regular expression, it should start with a colon (':').
To show that no symbols are allowed before the given pattern, we use ^ symbol at the beginning of the pattern.
To specify that no symbols are allowed after the given pattern, we use $ symbol at the end of the pattern.

===Example===

To only permit bypassed access in walled garden to "www.example.com/test" but not to "www.example.com/test/test.php" :

<pre>
/ip hotspot walled-garden
add dst-host=:^www.example.com path=":/test\$"
</pre>

(note the trailing $ requires the escape character '\' to stop it from be processed as an actual $ character in the url)

===Properties===

{{Mr-arg-table-h
|prop=Property
|desc=Description
}}

{{Mr-arg-table
|arg=action
|type=allow {{!}} deny
|default=allow
|desc=Action to perform, when packet matches the rule
*'''allow''' - allow access to the web-page without authorization
*'''deny''' - the authorization is required to access the web-page
}}

{{Mr-arg-table
|arg=server
|type=string
|default=
|desc=Name of the HotSpot server, rule is applied to.
}}

{{Mr-arg-table
|arg=src-address
|type=IP
|default=
|desc=Source address of the user, usually IP address of the HotSpot client
}}

{{Mr-arg-table
|arg=method
|type=string
|default=
|desc=HTTP method of the request
}}

{{Mr-arg-table
|arg=dst-host
|type=string
|default=
|desc=Domain name of the destination web-server
}}

{{Mr-arg-table
|arg=dst-port
|type=integer
|default=
|desc=TCP port number, client sends request to
}}

{{Mr-arg-table-end
|arg=path
|type=string
|default=
|desc=The path of the request, path comes after <nowiki>'''http://dst_host/'''</nowiki>
}}

'''Read-only properties'''
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}

{{Mr-arg-ro-table
|arg=dst-address
|type=IP
|desc=
}}

{{Mr-arg-ro-table-end
|arg=hits
|type=integer
|desc=
}}

==IP Walled Garden==

Sub-menu: <code>/ip hotspot walled-garden ip</code> 

 

Walled-garden menu for the IP requests (Winbox, SSH, Telnet, SIP, etc.)

===Properties===

{{Mr-arg-table-h
|prop=Property
|desc=Description
}}

{{Mr-arg-table
|arg=action
|type=allow {{!}} deny {{!}} reject
|default=allow
|desc=Action to perform, when packet matches the rule
*'''allow''' - allow access to the web-page without authorization
*'''deny''' - the authorization is required to access the web-page
*'''reject''' - the authorization is required to access the resource, ICMP reject message will be sent to client, when packet will match the rule
}}

{{Mr-arg-table
|arg=server
|type=string
|default=
|desc=Name of the HotSpot server, rule is applied to.
}}

{{Mr-arg-table
|arg=src-address
|type=IP
|default=
|desc=Source address of the user, usually IP address of the HotSpot client
}}

{{Mr-arg-table
|arg=dst-address
|type=IP
|default=
|desc=Destination IP address, IP address of the WEB-server. Ignored if '''dst-host''' is already specified.
}}

{{Mr-arg-table
|arg=dst-host
|type=string
|default=
|desc=Domain name of the destination web-server. When this parameter is specified dynamic entry is added to [[#Walled Garden | Walled Garden]]
}}

{{Mr-arg-table
|arg=dst-port
|type=integer
|default=
|desc=TCP port number, client sends request to
}}

{{Mr-arg-table-end
|arg=protocol
|type=integer {{!}} string
|default=
|desc=IP protocol
}}

==Example==

When adding walled garden IP entry several dynamic rules are created. For example, lets add ''www.paypalobject.com''

<pre>
/ip hotspot walled-garden ip
add action=accept disabled=no dst-host=www.paypalobject.com
</pre>

Now if you look at walled garden menu you will see dynamic entry for object we just added
<pre>
[admin@493G] /ip hotspot walled-garden> print detail
Flags: X - disabled, D - dynamic
0 D ;;; www.paypalobject.com
dst-address=68.178.232.99 action=allow hits=0
</pre>

Also dynamic firewall and NAT rules are added to allow paypalobject.com resolved address
<pre>
[admin@493G] /ip firewall filter> print dynamic
Flags: X - disabled, I - invalid, D - dynamic
...
7 D ;;; www.paypalobject.com
chain=hs-unauth action=return dst-address=68.178.232.99
...

10 D ;;; www.paypalobject.com
chain=hs-unauth-to action=return src-address=68.178.232.99
</pre>
<pre>
[admin@493G] /ip firewall nat> print dynamic
Flags: X - disabled, I - invalid, D - dynamic
...
8 D ;;; www.paypalobject.com
chain=hs-unauth action=return dst-address=68.178.232.99
...
</pre>

{{cont}}
[[Category:Manual|H]]
[[Category:Hotspot|H]]
[[Category:IP|H]]

Manual:IP/Hotspot/Walled Garden - Revision history

Administrator: /* Example */

Administrator at 12:32, 29 January 2015

Administrator: Created page with "{{Versions | v3, v4, v5+}} __TOC__ ==Walled Garden== Sub-menu: /ip hotspot walled-garden HTTP walled-garden menu permits..."

Administrator: Created page with "{{Versions | v3, v4, v5+}} TOC ==Walled Garden==
Sub-menu: `/ip hotspot walled-garden`

HTTP walled-garden menu permits..."