RUT850 Hotspot: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Template: Networking_rutxxx_manual_fw_disclosure | |||
| fw_version = RUT850_R_00.01.04 | |||
}} | |||
==Summary== | ==Summary== | ||
Wireless '''Hotspots''' are essentially Wireless Access Points - they provide network and/or internet access to other | Wireless '''Hotspots''' are essentially Wireless Access Points - they provide network and/or internet access to other WiFi devices. The difference is that Hotspots are a lot more versatile when it comes to managing, monitoring and authenticating the wireless network's users. For example, while Wireless APs can be password protected, with Hotspots you can configure different users with different names, passwords, even data limits and data speeds and more. This chapter is an overview of the '''Wireless Hotspot''' function in RUT routers. | ||
==General== | ==General== | ||
| Line 11: | Line 14: | ||
'''External Radius''' authentication mode uses an external Radius server, to which you have to provide an address to, instead of using the router's internal Radius server. | '''External Radius''' authentication mode uses an external Radius server, to which you have to provide an address to, instead of using the router's internal Radius server. | ||
[[ | [[File:Services hotspot configuration external v 2.PNG]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | |||
<tr> | |||
<td>Configuration profile</td> | |||
<td>Custom | Cloud4wi | Hotspotsystem; default: '''Custom'''</td> | |||
<td>If not set to '''Custom''', Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the '''Walled Garden''' section. Used only with '''External radius''' Authentication mode. </td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles Wi-Fi Hotspot ON or OFF</td> | <td>Toggles Wi-Fi Hotspot ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AP IP</td> | <td>AP IP</td> | ||
<td>ip; | <td>ip; default: '''192.168.2.254/24'''</td> | ||
<td>Access Point IP address defines the IP address of your Hotspot's network</td> | <td>Access Point IP address defines the IP address of your Hotspot's network</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Logout address</td> | <td>Logout address</td> | ||
<td>host | ip; | <td>host | ip; default: '''1.1.1.1'''</td> | ||
<td>An address that can be used by users to logout from the Hotspot session</td> | <td>An address that can be used by users to logout from the Hotspot session</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication mode</td> | <td>Authentication mode</td> | ||
<td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; | <td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: '''Without radius'''</td> | ||
<td>Authentication mode defines how users will connect to the Hotspot</td> | <td>Authentication mode defines how users will connect to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication protocol</td> | <td>Authentication protocol</td> | ||
<td>PAP | CHAP; | <td>PAP | CHAP; default: '''PAP'''</td> | ||
<td>Authentication protocol used to authenticate new connections on the Hotspot</td> | <td>Authentication protocol used to authenticate new connections on the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Terms of service</td> | <td>Terms of service</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | <td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>RADIUS server #1 | RADIUS server #2</td> | <td>RADIUS server #1 | RADIUS server #2</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td>The IP address of the RADIUS server that is to be used for Authenticating your wireless clients </td> | <td>The IP address of the RADIUS server that is to be used for Authenticating your wireless clients </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication port</td> | <td>Authentication port</td> | ||
<td>integer [0..65535]; | <td>integer [0..65535]; default: '''1812'''</td> | ||
<td>RADIUS server authentication port</td> | <td>RADIUS server authentication port</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Accounting port</td> | <td>Accounting port</td> | ||
<td>integer [0..65535]; | <td>integer [0..65535]; default: '''1813''' </td> | ||
<td>RADIUS server accounting port</td> | <td>RADIUS server accounting port</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Radius secret key</td> | <td>Radius secret key</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>The secret key is a password used for authentication with the RADIUS server</td> | <td>The secret key is a password used for authentication with the RADIUS server</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>UAM port</td> | <td>UAM port</td> | ||
<td>integer [0..65535]; | <td>integer [0..65535]; default: '''3990'''</td> | ||
<td>Port to bind for authenticating clients</td> | <td>Port to bind for authenticating clients</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>UAM UI port</td> | <td>UAM UI port</td> | ||
<td>integer [0..65535]; | <td>integer [0..65535]; default: '''4990'''</td> | ||
<td>UAM User Interface port</td> | <td>UAM User Interface port</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>UAM secret</td> | <td>UAM secret</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>Shared secret between the UAM server and the Hotspot</td> | <td>Shared secret between the UAM server and the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>NAS identifier</td> | <td>NAS identifier</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>NAS-Identifier is one of the basic RADIUS attributes</td> | <td>NAS-Identifier is one of the basic RADIUS attributes</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Swap octets</td> | <td>Swap octets</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Swaps the meaning of input octets and output as it relates to RADIUS attributes</td> | <td>Swaps the meaning of input octets and output as it relates to RADIUS attributes</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Location name</td> | <td>Location name</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>Custom location name for your Hotspot</td> | <td>Custom location name for your Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>External landing page</td> | <td>External landing page</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of an external landing page</td> | <td>Enables the use of an external landing page</td> | ||
</tr> | |||
<tr> | |||
<td>Landing page address</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A custom Hotspot's external landing page</td> | |||
</tr> | |||
<tr> | |||
<td>Success URL</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A custom redirect URL after successful Hotspot login</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Protocol</td> | <td>Protocol</td> | ||
<td>HTTP | HTTPS; | <td>HTTP | HTTPS; default: '''HTTP'''</td> | ||
<td>Connection protocol of your Hotspot</td> | <td>Connection protocol of your Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>HTTPS redirect</td> | <td>HTTPS to landing page redirect</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Redirects HTTP pages to landing page</td> | <td>Redirects HTTP pages to landing page</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL key file</td> | <td>SSL key file</td> | ||
<td>.key file; | <td>.key file; default: <b>none</b></td> | ||
<td>SSL key file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL key file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL certificate file</td> | <td>SSL certificate file</td> | ||
<td>.crt file; | <td>.crt file; default: <b>none</b></td> | ||
<td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Use custom DNS</td> | <td>Use custom DNS</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of custom DNS servers instead of your regular DNS</td> | <td>Enables the use of custom DNS servers instead of your regular DNS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>DNS server 1 | DNS server 2</td> | <td>DNS server 1 | DNS server 2</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | <td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | ||
</tr> | </tr> | ||
| Line 138: | Line 156: | ||
===Internal Radius=== | ===Internal Radius=== | ||
---- | ---- | ||
'''Internal Radius''' is Authentication mode that uses the router's internal RADIUS server for authentication. Teltonika routers' RADIUS server has RFC 2866 RADIUS Accounting and RFC 2869 RADIUS Extensions implemented | '''Internal Radius''' is Authentication mode that uses the router's internal RADIUS server for authentication. Teltonika routers' RADIUS server has RFC 2866 RADIUS Accounting and RFC 2869 RADIUS Extensions implemented. | ||
[[ | [[File:Services hotspot configuration internal v 2.PNG]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | |||
<tr> | |||
<td>Configuration profile</td> | |||
<td>Custom | Cloud4wi | Hotspotsystem; default: '''Custom'''</td> | |||
<td>If not set to '''Custom''', Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the '''Walled Garden''' section. Used only with '''External radius''' Authentication mode.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles Wi-Fi Hotspot ON or OFF</td> | <td>Toggles Wi-Fi Hotspot ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AP IP</td> | <td>AP IP</td> | ||
<td>ip; | <td>ip; default: '''192.168.2.254/24'''</td> | ||
<td>Access Point IP address defines the IP address of your Hotspot's network</td> | <td>Access Point IP address defines the IP address of your Hotspot's network</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Logout address</td> | <td>Logout address</td> | ||
<td>host | ip; | <td>host | ip; default: '''1.1.1.1'''</td> | ||
<td>An address that can be used by users to logout from the Hotspot session</td> | <td>An address that can be used by users to logout from the Hotspot session</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication mode</td> | <td>Authentication mode</td> | ||
<td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; | <td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: '''Without radius'''</td> | ||
<td>Authentication mode defines how users will connect to the Hotspot</td> | <td>Authentication mode defines how users will connect to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Terms of service</td> | <td>Terms of service</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | <td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>External landing page</td> | <td>External landing page</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of an external landing page</td> | <td>Enables the use of an external landing page</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td> | <td>Landing page address</td> | ||
<td> | <td>string; default: <b>none</b></td> | ||
<td> | <td>A custom Hotspot's external landing page</td> | ||
</tr> | |||
<tr> | |||
<td>Success URL</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A custom redirect URL after successful Hotspot login</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>HTTPS redirect</td> | <td>HTTPS to landing page redirect</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Redirects HTTP pages to landing page</td> | <td>Redirects HTTP pages to landing page</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL key file</td> | <td>SSL key file</td> | ||
<td>.key file; | <td>.key file; default: <b>none</b></td> | ||
<td>SSL key file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL key file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL certificate file</td> | <td>SSL certificate file</td> | ||
<td>.crt file; | <td>.crt file; default: <b>none</b></td> | ||
<td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Use custom DNS</td> | <td>Use custom DNS</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of custom DNS servers instead of your regular DNS</td> | <td>Enables the use of custom DNS servers instead of your regular DNS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>DNS server 1 | DNS server 2</td> | <td>DNS server 1 | DNS server 2</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | <td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | ||
</tr> | </tr> | ||
| Line 216: | Line 244: | ||
'''Without Radius''' Authentication doesn't use a Radius server to authenticate users connecting to the Hotspot, instead it gives you the possibility to configure different users with different password and session parameters. | '''Without Radius''' Authentication doesn't use a Radius server to authenticate users connecting to the Hotspot, instead it gives you the possibility to configure different users with different password and session parameters. | ||
[[ | [[File:Services hotspot configuration without v 2.PNG]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | |||
<tr> | |||
<td>Configuration profile</td> | |||
<td>Custom | Cloud4wi | Hotspotsystem; default: '''Custom'''</td> | |||
<td>If not set to '''Custom''', Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the '''Walled Garden''' section. Used only with '''External radius''' Authentication mode.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles Wi-Fi Hotspot ON or OFF</td> | <td>Toggles Wi-Fi Hotspot ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AP IP</td> | <td>AP IP</td> | ||
<td>ip; | <td>ip; default: '''192.168.2.254/24'''</td> | ||
<td>Access Point IP address defines the IP address of your Hotspot's network</td> | <td>Access Point IP address defines the IP address of your Hotspot's network</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Logout address</td> | <td>Logout address</td> | ||
<td>host | ip; | <td>host | ip; default: '''1.1.1.1'''</td> | ||
<td>An address that can be used by users to logout from the Hotspot session</td> | <td>An address that can be used by users to logout from the Hotspot session</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication mode</td> | <td>Authentication mode</td> | ||
<td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; | <td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: '''Without radius'''</td> | ||
<td>Authentication mode defines how users will connect to the Hotspot</td> | <td>Authentication mode defines how users will connect to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Terms of service</td> | <td>Terms of service</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | <td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>External landing page</td> | <td>External landing page</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of an external landing page</td> | <td>Enables the use of an external landing page</td> | ||
</tr> | |||
<tr> | |||
<td>Landing page address</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A custom Hotspot's external landing page</td> | |||
</tr> | |||
<tr> | |||
<td>Success URL</td> | |||
<td>string; default: <b>none</b></td> | |||
<td>A custom redirect URL after successful Hotspot login</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Protocol</td> | <td>Protocol</td> | ||
<td>HTTP | HTTPS; | <td>HTTP | HTTPS; default: '''HTTP'''</td> | ||
<td>Connection protocol of your Hotspot</td> | <td>Connection protocol of your Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>HTTPS redirect</td> | <td>HTTPS to landing page redirect</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Redirects HTTP pages to landing page</td> | <td>Redirects HTTP pages to landing page</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL key file</td> | <td>SSL key file</td> | ||
<td>.key file; | <td>.key file; default: <b>none</b></td> | ||
<td>SSL key file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL key file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL certificate file</td> | <td>SSL certificate file</td> | ||
<td>.crt file; | <td>.crt file; default: <b>none</b></td> | ||
<td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Use custom DNS</td> | <td>Use custom DNS</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of custom DNS servers instead of your regular DNS</td> | <td>Enables the use of custom DNS servers instead of your regular DNS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>DNS server 1 | DNS server 2</td> | <td>DNS server 1 | DNS server 2</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td> Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | <td> Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | ||
</tr> | </tr> | ||
| Line 290: | Line 334: | ||
The '''Users Configuration''' tab is used to create new, unique users that can connect to the Hotspot. | The '''Users Configuration''' tab is used to create new, unique users that can connect to the Hotspot. | ||
[[ | [[File:Services hotspot configuration user.PNG]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Username</td> | <td>Username</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>A custom user name used to authenticate clients connecting to the Hotspot</td> | <td>A custom user name used to authenticate clients connecting to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Password</td> | <td>Password</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>A custom password for the specified user name</td> | <td>A custom password for the specified user name</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Session Template</td> | <td>Session Template</td> | ||
<td>string; | <td>string; default: '''unlimited'''</td> | ||
<td>Session templates define session settings for different users. The '''unlimited''' Session Template is a default template with no restrictions. More on Session Template in the next section</td> | <td>Session templates define session settings for different users. The '''unlimited''' Session Template is a default template with no restrictions. More on Session Template in the next section</td> | ||
</tr> | </tr> | ||
| Line 319: | Line 363: | ||
A '''Session Template''' is a set of rules that can be prescribed to a Hotspot user. A default template named '''unlimited''' is present in the router, but it has no configured restrictions. You can edit the default template or you can create a custom template and configure it. | A '''Session Template''' is a set of rules that can be prescribed to a Hotspot user. A default template named '''unlimited''' is present in the router, but it has no configured restrictions. You can edit the default template or you can create a custom template and configure it. | ||
[[ | [[File:Services hotspot configuration session template.PNG| border |class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Idle timeout</td> | <td>Idle timeout</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A timeout in seconds after which idle users are automatically disconnected from the Hotspot. 0 means unlimited</td> | <td>A timeout in seconds after which idle users are automatically disconnected from the Hotspot. 0 means unlimited</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Session timeout</td> | <td>Session timeout</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A timeout in seconds after users are automatically disconnected from the Hotspot. The timeout countdown begins when a user is authenticated to the Hotspot and, after an amount of time specified in this field, the user gets disconnected from the Hotspot. 0 means unlimited</td> | <td>A timeout in seconds after users are automatically disconnected from the Hotspot. The timeout countdown begins when a user is authenticated to the Hotspot and, after an amount of time specified in this field, the user gets disconnected from the Hotspot. 0 means unlimited</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Download bandwidth</td> | <td>Download bandwidth</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td> Maximum download bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s | <td> Maximum download bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s, Gbit/s</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Upload bandwidth</td> | <td>Upload bandwidth</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>Maximum upload bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s or | <td>Maximum upload bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s or Gbit/s</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Download limit</td> | <td>Download limit</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A received data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Download limit is specified in MB</td> | <td>A received data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Download limit is specified in MB</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Upload limit</td> | <td>Upload limit</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A sent data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Upload limit is specified in MB</td> | <td>A sent data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Upload limit is specified in MB</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Period</td> | <td>Period</td> | ||
<td>Month | Week | Day; | <td>Month | Week | Day; default: '''Month'''</td> | ||
<td>The beginning of the period during which the restriction specified in this section will apply. After the period is over, all specified limits are reset </td> | <td>The beginning of the period during which the restriction specified in this section will apply. After the period is over, all specified limits are reset </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Start day | Start hour</td> | <td>Start day | Start hour</td> | ||
<td>integer [1..31] | Monday..Sunday | integer [1..24]; | <td>integer [1..31] | Monday..Sunday | integer [1..24]; default: '''day 1'''</td> | ||
<td>Specifies which day of the month, week or hour of the day the limits will be reset</td> | <td>Specifies which day of the month, week or hour of the day the limits will be reset</td> | ||
</tr> | </tr> | ||
| Line 373: | Line 417: | ||
The '''Advertisement''' Authentication mode doesn't use any kind of actual authentication. Instead when a user connects to the Hotspot he first gets redirected to a specified advertisement page. After that the user is free to use the Hotspot. | The '''Advertisement''' Authentication mode doesn't use any kind of actual authentication. Instead when a user connects to the Hotspot he first gets redirected to a specified advertisement page. After that the user is free to use the Hotspot. | ||
[[ | [[File:Services_hotspot_configuration_advertisement_v3.PNG|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | |||
<tr> | |||
<td>Configuration profile</td> | |||
<td>Custom | Cloud4wi | Hotspotsystem; default: '''Custom'''</td> | |||
<td>If not set to '''Custom''', Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the '''Walled Garden''' section. Used only with '''External radius''' Authentication mode.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles Wi-Fi Hotspot ON or OFF</td> | <td>Toggles Wi-Fi Hotspot ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AP IP</td> | <td>AP IP</td> | ||
<td>ip; | <td>ip; default: '''192.168.2.254/24'''</td> | ||
<td>Access Point IP address defines the IP address of your Hotspot's network</td> | <td>Access Point IP address defines the IP address of your Hotspot's network</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication mode</td> | <td>Authentication mode</td> | ||
<td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; | <td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: '''Without radius'''</td> | ||
<td>Authentication mode defines how users will connect to the Hotspot</td> | <td>Authentication mode defines how users will connect to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Advertisement address</td> | <td>Advertisement address</td> | ||
<td>host | ip; | <td>host | ip; default: <b>none</b></td> | ||
<td>The address of the advertisement page that newly connected users will be redirected to</td> | <td>The address of the advertisement page that newly connected users will be redirected to</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>HTTPS redirect</td> | <td>HTTPS to landing page redirect</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Redirects HTTP pages to landing page</td> | <td>Redirects HTTP pages to landing page</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL key file</td> | <td>SSL key file</td> | ||
<td>.key file; | <td>.key file; default: <b>none</b></td> | ||
<td>SSL key file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled </td> | <td>SSL key file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL certificate file</td> | <td>SSL certificate file</td> | ||
<td>.crt file; | <td>.crt file; default: <b>none</b></td> | ||
<td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Use custom DNS</td> | <td>Use custom DNS</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of custom DNS servers instead of your regular DNS</td> | <td>Enables the use of custom DNS servers instead of your regular DNS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>DNS server 1 | DNS server 2</td> | <td>DNS server 1 | DNS server 2</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | <td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | ||
</tr> | </tr> | ||
| Line 430: | Line 479: | ||
===MAC auth=== | ===MAC auth=== | ||
---- | ---- | ||
'''MAC auth''' Authentication mode authenticates users by their MAC address. A list of accepted or unaccepted MAC addresses can be configured in the router's WebUI's Wireless section under Interface Configuration->[[ | '''MAC auth''' Authentication mode authenticates users by their MAC address. A list of accepted or unaccepted MAC addresses can be configured in the router's WebUI's Wireless section under Interface Configuration->[[RUT850_Wireless#MAC_Filter|MAC Filter]] | ||
[[ | [[File:Services hotspot configuration mac v 2.PNG| border | class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | |||
<tr> | |||
<td>Configuration profile</td> | |||
<td>Custom | Cloud4wi | Hotspotsystem; default: '''Custom'''</td> | |||
<td>If not set to '''Custom''', Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the '''Walled Garden''' section. Used only with '''External radius''' Authentication mode.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles Wi-Fi Hotspot ON or OFF</td> | <td>Toggles Wi-Fi Hotspot ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AP IP</td> | <td>AP IP</td> | ||
<td>ip; | <td>ip; default: '''192.168.2.254/24'''</td> | ||
<td>Access Point IP address defines the IP address of your Hotspot's network</td> | <td>Access Point IP address defines the IP address of your Hotspot's network</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Logout address</td> | <td>Logout address</td> | ||
<td>host | ip; | <td>host | ip; default: '''1.1.1.1'''</td> | ||
<td>An address that can be used by users to logout from the Hotspot session</td> | <td>An address that can be used by users to logout from the Hotspot session</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication mode</td> | <td>Authentication mode</td> | ||
<td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; | <td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: '''Without radius'''</td> | ||
<td>Authentication mode defines how users will connect to the Hotspot</td> | <td>Authentication mode defines how users will connect to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Terms of service</td> | <td>Terms of service</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | <td>If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the '''Landing Page''' section</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Password protection</td> | <td>Password protection</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables Hotspot password protection</td> | <td>Enables Hotspot password protection</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Password</td> | <td>Password</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>A password used to authenticate connecting clients to the Hotspot</td> | <td>A password used to authenticate connecting clients to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Website access link</td> | <td>Website access link</td> | ||
<td>Link | Auto redirect | Custom address; | <td>Link | Auto redirect | Custom address; default: '''Link'''</td> | ||
<td>Requested website access mode</td> | <td>Requested website access mode</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Protocol</td> | <td>Protocol</td> | ||
<td>HTTP | HTTPS; | <td>HTTP | HTTPS; default: '''HTTP'''</td> | ||
<td>Connection protocol of your Hotspot</td> | <td>Connection protocol of your Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>HTTPS redirect</td> | <td>HTTPS to landing page redirect</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Redirects HTTP pages to landing page</td> | <td>Redirects HTTP pages to landing page</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL key file</td> | <td>SSL key file</td> | ||
<td>.key file; | <td>.key file; default: <b>none</b></td> | ||
<td>SSL key file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL key file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL certificate file</td> | <td>SSL certificate file</td> | ||
<td>.crt file; | <td>.crt file; default: <b>none</b></td> | ||
<td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Use custom DNS</td> | <td>Use custom DNS</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of custom DNS servers instead of your regular DNS</td> | <td>Enables the use of custom DNS servers instead of your regular DNS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>DNS server 1 | DNS server 2</td> | <td>DNS server 1 | DNS server 2</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | <td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | ||
</tr> | </tr> | ||
| Line 516: | Line 570: | ||
With '''SMS OTP''' Authentication mode connecting users are prompted to enter their phone number. After that, the router sends and SMS message containing a code to the specified number. Users then authenticate themselves to the Hotspot using this code. | With '''SMS OTP''' Authentication mode connecting users are prompted to enter their phone number. After that, the router sends and SMS message containing a code to the specified number. Users then authenticate themselves to the Hotspot using this code. | ||
[[ | [[File:Services hotspot configuration sms v 2.PNG |border| class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | |||
<tr> | |||
<td>Configuration profile</td> | |||
<td>Custom | Cloud4wi | Hotspotsystem; default: '''Custom'''</td> | |||
<td>If not set to '''Custom''', Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the '''Walled Garden''' section. Used only with '''External radius''' Authentication mode.</td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles Wi-Fi Hotspot ON or OFF</td> | <td>Toggles Wi-Fi Hotspot ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>AP IP</td> | <td>AP IP</td> | ||
<td>ip; | <td>ip; default: '''192.168.2.254/24'''</td> | ||
<td>Access Point IP address defines the IP address of your Hotspot's network</td> | <td>Access Point IP address defines the IP address of your Hotspot's network</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication mode</td> | <td>Authentication mode</td> | ||
<td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; | <td>External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: '''Without radius'''</td> | ||
<td>Authentication mode defines how users will connect to the Hotspot</td> | <td>Authentication mode defines how users will connect to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Protocol</td> | <td>Protocol</td> | ||
<td>HTTP | HTTPS; | <td>HTTP | HTTPS; default: '''HTTP'''</td> | ||
<td>Connection protocol of your Hotspot</td> | <td>Connection protocol of your Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>HTTPS redirect</td> | <td>HTTPS to landing page redirect</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Redirects HTTP pages to landing page</td> | <td>Redirects HTTP pages to landing page</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL key file</td> | <td>SSL key file</td> | ||
<td>.key file; | <td>.key file; default: <b>none</b></td> | ||
<td>SSL key file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL key file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>SSL certificate file</td> | <td>SSL certificate file</td> | ||
<td>.crt file; | <td>.crt file; default: <b>none</b></td> | ||
<td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS redirect''' is enabled</td> | <td>SSL certificate file used for authentication. This field becomes visible only if '''HTTPS to landing page redirect''' is enabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Use custom DNS</td> | <td>Use custom DNS</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Enables the use of custom DNS servers instead of your regular DNS</td> | <td>Enables the use of custom DNS servers instead of your regular DNS</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>DNS server 1 | DNS server 2</td> | <td>DNS server 1 | DNS server 2</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | <td>Additional DNS servers that are to be used by the Hotspot. These fields become visible only if '''Use custom DNS''' is enabled</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
=== | ===Walled Garden=== | ||
---- | ---- | ||
You can configure a list of addresses that users connected to the Hotspot will be able to reach without any authentication. By default this list is empty. Click the '''Add''' button to add a new address. | You can configure a list of addresses that users connected to the Hotspot will be able to reach without any authentication. By default this list is empty. Click the '''Add''' button to add a new address. | ||
[[ | [[File:Services hotspot configuration walled garden.png| border| class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''yes'''</td> | ||
<td>Enables or disables an entry of the list</td> | <td>Enables or disables an entry of the list</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Address</td> | <td>Address</td> | ||
<td>host | ip; | <td>host | ip; default: <b>none</b></td> | ||
<td>An address that users connected to the Hotspot can reach without authentication</td> | <td>An address that users connected to the Hotspot can reach without authentication</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Port</td> | <td>Port</td> | ||
<td>integer [0..65535]; | <td>integer [0..65535]; default: <b>none</b></td> | ||
<td>Specifies the port through which the user can connect to the provided address. This field becomes visible only if '''Allow subdomains''' is disabled</td> | <td>Specifies the port through which the user can connect to the provided address. This field becomes visible only if '''Allow subdomains''' is disabled</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Allow subdomains</td> | <td>Allow subdomains</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>If checked, users can connect to the specified address and all of its subdomains</td> | <td>If checked, users can connect to the specified address and all of its subdomains</td> | ||
</tr> | </tr> | ||
| Line 609: | Line 668: | ||
The '''Restricted Internet Access''' page provides you with the possibility to restrict internet access on Hotspot on specified hours. Blue squares represent restricted access, white squares - allowed access. Bellow is an example of a configuration that restricts internet access outside of working hours. | The '''Restricted Internet Access''' page provides you with the possibility to restrict internet access on Hotspot on specified hours. Blue squares represent restricted access, white squares - allowed access. Bellow is an example of a configuration that restricts internet access outside of working hours. | ||
[[ | [[File:Services hotspot restricted list.PNG|border|class=tlt-border]] | ||
==Logging== | ==Logging== | ||
The Hotspot '''Logging''' section is used to send Hotspot or Wireless information to an FTP or Syslog server. | |||
[[File:Services hotspot logging configuration logging.PNG|border| class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th>Field</th> | |||
<th>Value</th> | |||
<th>Description</th> | |||
</tr> | |||
<tr> | |||
<td>Enable</td> | |||
<td>yes | no; default: '''no'''</td> | |||
<td> Enables or disables whole logging section's fuctionality </td> | |||
</tr> | |||
</table> | |||
[[File:Services hotspot logging configuration syslog.PNG|border| class=tlt-border]] | |||
<table class="nd-mantable"> | |||
<tr> | |||
<th>Field</th> | |||
<th>Value</th> | |||
<th>Description</th> | |||
</tr> | |||
<tr> | |||
<td>Enable</td> | |||
<td>yes | no; default: '''no'''</td> | |||
<td>Toggles logging to Syslog ON or OFF </td> | |||
</tr> | |||
<tr> | |||
<td>Server address</td> | |||
<td>host | ip; default: '''" "'''</td> | |||
<td>Syslog server address</td> | |||
</tr> | |||
<tr> | |||
<td>Port</td> | |||
<td>integer [0..65535]; default: '''" "'''</td> | |||
<td>Syslog server port</td> | |||
</tr> | |||
<tr> | |||
<td>Protocol</td> | |||
<td>UDP|TCP default: '''TCP'''</td> | |||
<td>Protocol of the syslog server</td> | |||
</tr> | |||
<tr> | |||
<td>Prefix text</td> | |||
<td>string; default: '''" "''' </td> | |||
<td>Prefix custom text to streamed messages</td> | |||
</tr> | |||
<tr> | |||
<td>Protocol filter</td> | |||
<td>UDP|TCP|Any; default: '''Any'''</td> | |||
<td>Filter log messages depending on protocol</td> | |||
</tr> | |||
<tr> | |||
<td>Port filter </td> | |||
<td>integer [0..65535]; default: '''" "'''</td> | |||
<td>Filter log messages depending on port of port range</td> | |||
</tr> | |||
</table> | |||
[[ | [[File:Services hotspot logging configuration ftp.PNG|border| class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles logging to FTP ON or OFF</td> | <td>Toggles logging to FTP ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Server address</td> | <td>Server address</td> | ||
<td>host | ip; | <td>host | ip; default: '''your.ftp.server'''</td> | ||
<td>FTP server address.</td> | <td>FTP server address.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>User name</td> | <td>User name</td> | ||
<td>string; | <td>string; default: '''username'''</td> | ||
<td>User name used for authentication when logging into an FTP server</td> | <td>User name used for authentication when logging into an FTP server</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Password</td> | <td>Password</td> | ||
<td>string; | <td>string; default: '''password'''</td> | ||
<td>Password used for authentication when logging into an FTP server</td> | <td>Password used for authentication when logging into an FTP server</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Port</td> | <td>Port</td> | ||
<td>integer [0..65535]; | <td>integer [0..65535]; default: '''21''' </td> | ||
<td>FTP server port</td> | <td>FTP server port</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>File name extras</td> | <td>File name extras</td> | ||
<td>No extra information | MAC address | Serial number | Custom string; | <td>No extra information | MAC address | Serial number | Custom string; default: '''No extra information'''</td> | ||
<td>Extra information to be added to the log filename</td> | <td>Extra information to be added to the log filename</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
===FTP Upload Settings=== | ===FTP Upload Settings=== | ||
| Line 660: | Line 775: | ||
Here you can configure your timing settings for the log upload via FTP feature. | Here you can configure your timing settings for the log upload via FTP feature. | ||
[[ | [[File:Services hotspot logging configuration ftp set.PNG|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Mode</td> | <td>Mode</td> | ||
<td>Fixed | Interval; | <td>Fixed | Interval; default: '''Fixed'''</td> | ||
<td>The scheduling mode to be used for uploading to FTP server</td> | <td>The scheduling mode to be used for uploading to FTP server</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Hours | <td>Hours</td> | ||
<td>time; | <td>time; default: '''8 hours'''</td> | ||
<td>Time interval when the uploads will take place</td> | <td>Time interval when the uploads will take place</td> | ||
</tr> | |||
<tr> | |||
<td>Minutes</td> | |||
<td>time;default: '''15 minutes'''</td> | |||
<td>Time interval when the uploads will take place</td> | |||
</tr> | |||
<td>Days</td> | |||
<td>time;default: '''Monday, Tuesday, Wednesday, Thursday, Friday'''</td> | |||
<td>On which day upload will take place</td> | |||
<tr> | |||
</tr> | </tr> | ||
</table> | </table> | ||
| Line 683: | Line 809: | ||
---- | ---- | ||
WiFi and SMS OTP logs show information about connections to your WiFi Hotspot. FTP logging has to be enabled. | WiFi and SMS OTP logs show information about connections to your WiFi Hotspot. FTP logging has to be enabled. | ||
[[File:Services hotspot logging configuration Wifi log.PNG|border|class=tlt-border]] | |||
[[File:Services hotspot logging configuration SMS OTP log.PNG|border|class=tlt-border]] | |||
==Landing Page== | ==Landing Page== | ||
| Line 688: | Line 816: | ||
This section is used to define how your Hotspot's Landing Page will look like. | This section is used to define how your Hotspot's Landing Page will look like. | ||
[[ | [[File:Services hotspot landing page general.PNG|border|class=tlt-border]] | ||
===Template=== | ===Template=== | ||
| Line 694: | Line 822: | ||
This is a template based on the default landing page. You can edit its HTML code to make it look however you want! | This is a template based on the default landing page. You can edit its HTML code to make it look however you want! | ||
[[ | [[File:Services hotspot landing page template.PNG|border|class=tlt-border]] | ||
===Custom Landing Page=== | |||
---- | |||
==Radius Server== | ==Radius Server== | ||
| Line 700: | Line 831: | ||
This section is used to configure your '''Radius Server''' for use with '''[[#Internal_Radius|Internal radius]]''' Authentication mode | This section is used to configure your '''Radius Server''' for use with '''[[#Internal_Radius|Internal radius]]''' Authentication mode | ||
[[ | [[File:Services hotspot radius server.PNG|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles Radius Server ON or OFF</td> | <td>Toggles Radius Server ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Remote access</td> | <td>Remote access</td> | ||
<td>yes | no; | <td>yes | no; default: '''no'''</td> | ||
<td>Toggles remote access to the Radius Server ON or OFF.</td> | <td>Toggles remote access to the Radius Server ON or OFF.</td> | ||
</tr> | |||
<tr> | |||
<td>Accounting port</td> | |||
<td>integer [0..65535]; default: '''1813'''</td> | |||
<td>Radius server accounting port </td> | |||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Authentication port</td> | <td>Authentication port</td> | ||
<td>integer [0..65535]; | <td>integer [0..65535]; default: '''1812'''</td> | ||
<td>Radius server authentication port</td> | <td>Radius server authentication port</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
===Session Settings=== | ===Session Settings=== | ||
| Line 734: | Line 866: | ||
A '''Session Template''' is a set of rules that can be prescribed to a Hotspot user. A default template named '''unlimited''' is present in the router, but it has no configured restriction. You can edit the default template or you can create a custom template and configure it. | A '''Session Template''' is a set of rules that can be prescribed to a Hotspot user. A default template named '''unlimited''' is present in the router, but it has no configured restriction. You can edit the default template or you can create a custom template and configure it. | ||
[[ | [[File:Services hotspot configuration session template.PNG|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Idle timeout</td> | <td>Idle timeout</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A timeout in seconds after which idle users are automatically disconnected from the Hotspot. 0 means unlimited</td> | <td>A timeout in seconds after which idle users are automatically disconnected from the Hotspot. 0 means unlimited</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Session timeout</td> | <td>Session timeout</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A timeout in seconds after users are automatically disconnected from the Hotspot. The timeout countdown begins when a user is authenticated to the Hotspot and, after an amount of time specified in this field, the user gets disconnected from the Hotspot. 0 means unlimited</td> | <td>A timeout in seconds after users are automatically disconnected from the Hotspot. The timeout countdown begins when a user is authenticated to the Hotspot and, after an amount of time specified in this field, the user gets disconnected from the Hotspot. 0 means unlimited</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Download bandwidth</td> | <td>Download bandwidth</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>Maximum download bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s or | <td>Maximum download bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s or Gbit/s</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Upload bandwidth</td> | <td>Upload bandwidth</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>Maximum upload bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s or | <td>Maximum upload bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s or Gbit/s</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Download limit</td> | <td>Download limit</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A received data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Download limit is specified in MB</td> | <td>A received data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Download limit is specified in MB</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Upload limit</td> | <td>Upload limit</td> | ||
<td>integer; | <td>integer; default: <b>none</b></td> | ||
<td>A sent data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Upload limit is specified in MB</td> | <td>A sent data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Upload limit is specified in MB</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Period</td> | <td>Period</td> | ||
<td>Month | Week | Day; | <td>Month | Week | Day; default: '''Month'''</td> | ||
<td>The beginning of the period during which the restriction specified in this section will apply. After the period is over, all specified limits are reset </td> | <td>The beginning of the period during which the restriction specified in this section will apply. After the period is over, all specified limits are reset </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Start day | Start hour</td> | <td>Start day | Start hour</td> | ||
<td>integer [1..31] | Monday..Sunday | integer [1..24]; | <td>integer [1..31] | Monday..Sunday | integer [1..24]; default: '''day 1'''</td> | ||
<td>Specifies which day of the month, week or hour of the day the limits will be reset</td> | <td>Specifies which day of the month, week or hour of the day the limits will be reset</td> | ||
</tr> | </tr> | ||
| Line 788: | Line 920: | ||
The '''Users Configuration''' tab is used to create new, unique users that can connect to the Hotspot. | The '''Users Configuration''' tab is used to create new, unique users that can connect to the Hotspot. | ||
[[ | [[File:Services hotspot configuration user.PNG]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Username</td> | <td>Username</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>A custom user name used to authenticate clients connecting to the Hotspot</td> | <td>A custom user name used to authenticate clients connecting to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Password</td> | <td>Password</td> | ||
<td>string; | <td>string; default: <b>none</b> </td> | ||
<td>A custom password for the specified user name</td> | <td>A custom password for the specified user name</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Session Template</td> | <td>Session Template</td> | ||
<td>string; | <td>string; default: '''unlimited'''</td> | ||
<td>Session templates define session settings for different users. The '''unlimited''' Session Template is a default template with no restrictions. More on Session Template in the next section</td> | <td>Session templates define session settings for different users. The '''unlimited''' Session Template is a default template with no restrictions. More on Session Template in the next section</td> | ||
</tr> | </tr> | ||
| Line 815: | Line 947: | ||
===Clients Configuration Settings=== | ===Clients Configuration Settings=== | ||
---- | ---- | ||
[[ | [[File:Services hotspot radius server clients.PNG|border|class=tlt-border]] | ||
<table class="nd-mantable"> | <table class="nd-mantable"> | ||
<tr> | <tr> | ||
<th> | <th>Field</th> | ||
<th> | <th>Value</th> | ||
<th> | <th>Description</th> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
<td>yes | no; | <td>yes | no; default: '''yes'''</td> | ||
<td>Toggles Clients Configuration ON or OFF</td> | <td>Toggles Clients Configuration ON or OFF</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Client name</td> | <td>Client name</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>A custom user name used to authenticate clients connecting to the Hotspot</td> | <td>A custom user name used to authenticate clients connecting to the Hotspot</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>IP address</td> | <td>IP address</td> | ||
<td>ip; | <td>ip; default: <b>none</b></td> | ||
<td>The IP address of the client </td> | <td>The IP address of the client </td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Netmask</td> | <td>Netmask</td> | ||
<td>integer [0..32]; | <td>integer [0..32]; default: <b>none</b></td> | ||
<td>The netmask of the client</td> | <td>The netmask of the client</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Radius shared secret</td> | <td>Radius shared secret</td> | ||
<td>string; | <td>string; default: <b>none</b></td> | ||
<td>Radius shared secret used for communication between the client/NAS and the radius server</td> | <td>Radius shared secret used for communication between the client/NAS and the radius server</td> | ||
</tr> | </tr> | ||
| Line 852: | Line 984: | ||
==Statistics== | ==Statistics== | ||
The '''Statistics''' page shows statistics about connections to the hotspot. | The '''Statistics''' page shows statistics about connections to the hotspot. '''Reminder: Statistics page becomes visible only when device is connected to the hotspot.''' | ||
[[ | [[File:Services hotspot stats.PNG|border|class=tlt-border]] | ||
==Manage== | ==Manage== | ||
| Line 929: | Line 992: | ||
With the help of the '''Manage''' page you manage the users that are connected to your Hotspot. To reach the '''Manage''' window, go to Services->Hotspot. The '''Manage''' button will be located next to your Hotspot instance. | With the help of the '''Manage''' page you manage the users that are connected to your Hotspot. To reach the '''Manage''' window, go to Services->Hotspot. The '''Manage''' button will be located next to your Hotspot instance. | ||
[[ | [[File:Services hotspot manage reach.PNG|border|class=tlt-border]] | ||
[[ | [[File:Services hotspot manage.PNG|border|class=tlt-border]] | ||
[[Category:RUT850 Services section]] | [[Category:RUT850 Services section]] | ||
Latest revision as of 09:21, 10 December 2020
Main Page > EOL Products > RUT850 > RUT850 Manual > RUT850 WebUI > RUT850 Services section > RUT850 HotspotThe information in this page is updated in accordance with the RUT850_R_00.01.04 firmware version.
Summary
Wireless Hotspots are essentially Wireless Access Points - they provide network and/or internet access to other WiFi devices. The difference is that Hotspots are a lot more versatile when it comes to managing, monitoring and authenticating the wireless network's users. For example, while Wireless APs can be password protected, with Hotspots you can configure different users with different names, passwords, even data limits and data speeds and more. This chapter is an overview of the Wireless Hotspot function in RUT routers.
General
The General tab is where most of the Hotspot configurations take place. This section will be divided into six sub-sections - one for each Authentication mode, since the chosen Authentication mode will define how the Hotspot will be configured in general.
External Radius
External Radius authentication mode uses an external Radius server, to which you have to provide an address to, instead of using the router's internal Radius server.
| Field | Value | Description |
|---|---|---|
| Configuration profile | Custom | Cloud4wi | Hotspotsystem; default: Custom | If not set to Custom, Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the Walled Garden section. Used only with External radius Authentication mode. |
| Enable | yes | no; default: no | Toggles Wi-Fi Hotspot ON or OFF |
| AP IP | ip; default: 192.168.2.254/24 | Access Point IP address defines the IP address of your Hotspot's network |
| Logout address | host | ip; default: 1.1.1.1 | An address that can be used by users to logout from the Hotspot session |
| Authentication mode | External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: Without radius | Authentication mode defines how users will connect to the Hotspot |
| Authentication protocol | PAP | CHAP; default: PAP | Authentication protocol used to authenticate new connections on the Hotspot |
| Terms of service | yes | no; default: no | If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the Landing Page section |
| RADIUS server #1 | RADIUS server #2 | ip; default: none | The IP address of the RADIUS server that is to be used for Authenticating your wireless clients |
| Authentication port | integer [0..65535]; default: 1812 | RADIUS server authentication port |
| Accounting port | integer [0..65535]; default: 1813 | RADIUS server accounting port |
| Radius secret key | string; default: none | The secret key is a password used for authentication with the RADIUS server |
| UAM port | integer [0..65535]; default: 3990 | Port to bind for authenticating clients |
| UAM UI port | integer [0..65535]; default: 4990 | UAM User Interface port |
| UAM secret | string; default: none | Shared secret between the UAM server and the Hotspot |
| NAS identifier | string; default: none | NAS-Identifier is one of the basic RADIUS attributes |
| Swap octets | yes | no; default: no | Swaps the meaning of input octets and output as it relates to RADIUS attributes |
| Location name | string; default: none | Custom location name for your Hotspot |
| External landing page | yes | no; default: no | Enables the use of an external landing page |
| Landing page address | string; default: none | A custom Hotspot's external landing page |
| Success URL | string; default: none | A custom redirect URL after successful Hotspot login |
| Protocol | HTTP | HTTPS; default: HTTP | Connection protocol of your Hotspot |
| HTTPS to landing page redirect | yes | no; default: no | Redirects HTTP pages to landing page |
| SSL key file | .key file; default: none | SSL key file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| SSL certificate file | .crt file; default: none | SSL certificate file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| Use custom DNS | yes | no; default: no | Enables the use of custom DNS servers instead of your regular DNS |
| DNS server 1 | DNS server 2 | ip; default: none | Additional DNS servers that are to be used by the Hotspot. These fields become visible only if Use custom DNS is enabled |
Internal Radius
Internal Radius is Authentication mode that uses the router's internal RADIUS server for authentication. Teltonika routers' RADIUS server has RFC 2866 RADIUS Accounting and RFC 2869 RADIUS Extensions implemented.
| Field | Value | Description |
|---|---|---|
| Configuration profile | Custom | Cloud4wi | Hotspotsystem; default: Custom | If not set to Custom, Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the Walled Garden section. Used only with External radius Authentication mode. |
| Enable | yes | no; default: no | Toggles Wi-Fi Hotspot ON or OFF |
| AP IP | ip; default: 192.168.2.254/24 | Access Point IP address defines the IP address of your Hotspot's network |
| Logout address | host | ip; default: 1.1.1.1 | An address that can be used by users to logout from the Hotspot session |
| Authentication mode | External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: Without radius | Authentication mode defines how users will connect to the Hotspot |
| Terms of service | yes | no; default: no | If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the Landing Page section |
| External landing page | yes | no; default: no | Enables the use of an external landing page |
| Landing page address | string; default: none | A custom Hotspot's external landing page |
| Success URL | string; default: none | A custom redirect URL after successful Hotspot login |
| HTTPS to landing page redirect | yes | no; default: no | Redirects HTTP pages to landing page |
| SSL key file | .key file; default: none | SSL key file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| SSL certificate file | .crt file; default: none | SSL certificate file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| Use custom DNS | yes | no; default: no | Enables the use of custom DNS servers instead of your regular DNS |
| DNS server 1 | DNS server 2 | ip; default: none | Additional DNS servers that are to be used by the Hotspot. These fields become visible only if Use custom DNS is enabled |
Information on how to configure Internal radius server can be found here.
Without Radius
Without Radius Authentication doesn't use a Radius server to authenticate users connecting to the Hotspot, instead it gives you the possibility to configure different users with different password and session parameters.
| Field | Value | Description |
|---|---|---|
| Configuration profile | Custom | Cloud4wi | Hotspotsystem; default: Custom | If not set to Custom, Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the Walled Garden section. Used only with External radius Authentication mode. |
| Enable | yes | no; default: no | Toggles Wi-Fi Hotspot ON or OFF |
| AP IP | ip; default: 192.168.2.254/24 | Access Point IP address defines the IP address of your Hotspot's network |
| Logout address | host | ip; default: 1.1.1.1 | An address that can be used by users to logout from the Hotspot session |
| Authentication mode | External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: Without radius | Authentication mode defines how users will connect to the Hotspot |
| Terms of service | yes | no; default: no | If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the Landing Page section |
| External landing page | yes | no; default: no | Enables the use of an external landing page |
| Landing page address | string; default: none | A custom Hotspot's external landing page |
| Success URL | string; default: none | A custom redirect URL after successful Hotspot login |
| Protocol | HTTP | HTTPS; default: HTTP | Connection protocol of your Hotspot |
| HTTPS to landing page redirect | yes | no; default: no | Redirects HTTP pages to landing page |
| SSL key file | .key file; default: none | SSL key file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| SSL certificate file | .crt file; default: none | SSL certificate file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| Use custom DNS | yes | no; default: no | Enables the use of custom DNS servers instead of your regular DNS |
| DNS server 1 | DNS server 2 | ip; default: none | Additional DNS servers that are to be used by the Hotspot. These fields become visible only if Use custom DNS is enabled |
Users Configuration
The Users Configuration tab is used to create new, unique users that can connect to the Hotspot.
| Field | Value | Description |
|---|---|---|
| Username | string; default: none | A custom user name used to authenticate clients connecting to the Hotspot |
| Password | string; default: none | A custom password for the specified user name |
| Session Template | string; default: unlimited | Session templates define session settings for different users. The unlimited Session Template is a default template with no restrictions. More on Session Template in the next section |
Session Templates
A Session Template is a set of rules that can be prescribed to a Hotspot user. A default template named unlimited is present in the router, but it has no configured restrictions. You can edit the default template or you can create a custom template and configure it.
| Field | Value | Description |
|---|---|---|
| Idle timeout | integer; default: none | A timeout in seconds after which idle users are automatically disconnected from the Hotspot. 0 means unlimited |
| Session timeout | integer; default: none | A timeout in seconds after users are automatically disconnected from the Hotspot. The timeout countdown begins when a user is authenticated to the Hotspot and, after an amount of time specified in this field, the user gets disconnected from the Hotspot. 0 means unlimited |
| Download bandwidth | integer; default: none | Maximum download bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s, Gbit/s |
| Upload bandwidth | integer; default: none | Maximum upload bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s or Gbit/s |
| Download limit | integer; default: none | A received data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Download limit is specified in MB |
| Upload limit | integer; default: none | A sent data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Upload limit is specified in MB |
| Period | Month | Week | Day; default: Month | The beginning of the period during which the restriction specified in this section will apply. After the period is over, all specified limits are reset |
| Start day | Start hour | integer [1..31] | Monday..Sunday | integer [1..24]; default: day 1 | Specifies which day of the month, week or hour of the day the limits will be reset |
Advertisement
The Advertisement Authentication mode doesn't use any kind of actual authentication. Instead when a user connects to the Hotspot he first gets redirected to a specified advertisement page. After that the user is free to use the Hotspot.
| Field | Value | Description |
|---|---|---|
| Configuration profile | Custom | Cloud4wi | Hotspotsystem; default: Custom | If not set to Custom, Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the Walled Garden section. Used only with External radius Authentication mode. |
| Enable | yes | no; default: no | Toggles Wi-Fi Hotspot ON or OFF |
| AP IP | ip; default: 192.168.2.254/24 | Access Point IP address defines the IP address of your Hotspot's network |
| Authentication mode | External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: Without radius | Authentication mode defines how users will connect to the Hotspot |
| Advertisement address | host | ip; default: none | The address of the advertisement page that newly connected users will be redirected to |
| HTTPS to landing page redirect | yes | no; default: no | Redirects HTTP pages to landing page |
| SSL key file | .key file; default: none | SSL key file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| SSL certificate file | .crt file; default: none | SSL certificate file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| Use custom DNS | yes | no; default: no | Enables the use of custom DNS servers instead of your regular DNS |
| DNS server 1 | DNS server 2 | ip; default: none | Additional DNS servers that are to be used by the Hotspot. These fields become visible only if Use custom DNS is enabled |
MAC auth
MAC auth Authentication mode authenticates users by their MAC address. A list of accepted or unaccepted MAC addresses can be configured in the router's WebUI's Wireless section under Interface Configuration->MAC Filter
| Field | Value | Description |
|---|---|---|
| Configuration profile | Custom | Cloud4wi | Hotspotsystem; default: Custom | If not set to Custom, Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the Walled Garden section. Used only with External radius Authentication mode. |
| Enable | yes | no; default: no | Toggles Wi-Fi Hotspot ON or OFF |
| AP IP | ip; default: 192.168.2.254/24 | Access Point IP address defines the IP address of your Hotspot's network |
| Logout address | host | ip; default: 1.1.1.1 | An address that can be used by users to logout from the Hotspot session |
| Authentication mode | External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: Without radius | Authentication mode defines how users will connect to the Hotspot |
| Terms of service | yes | no; default: no | If enabled, users have to agree to the Terms of service before logging in. Custom Terms of service can be defined in the Landing Page section |
| Password protection | yes | no; default: no | Enables Hotspot password protection |
| Password | string; default: none | A password used to authenticate connecting clients to the Hotspot |
| Website access link | Link | Auto redirect | Custom address; default: Link | Requested website access mode |
| Protocol | HTTP | HTTPS; default: HTTP | Connection protocol of your Hotspot |
| HTTPS to landing page redirect | yes | no; default: no | Redirects HTTP pages to landing page |
| SSL key file | .key file; default: none | SSL key file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| SSL certificate file | .crt file; default: none | SSL certificate file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| Use custom DNS | yes | no; default: no | Enables the use of custom DNS servers instead of your regular DNS |
| DNS server 1 | DNS server 2 | ip; default: none | Additional DNS servers that are to be used by the Hotspot. These fields become visible only if Use custom DNS is enabled |
SMS OTP
With SMS OTP Authentication mode connecting users are prompted to enter their phone number. After that, the router sends and SMS message containing a code to the specified number. Users then authenticate themselves to the Hotspot using this code.
| Field | Value | Description |
|---|---|---|
| Configuration profile | Custom | Cloud4wi | Hotspotsystem; default: Custom | If not set to Custom, Configuration profile selections will automatically fill all the fields in accordance with the chosen profile. It also automatically adds an exception for the chosen service in the Walled Garden section. Used only with External radius Authentication mode. |
| Enable | yes | no; default: no | Toggles Wi-Fi Hotspot ON or OFF |
| AP IP | ip; default: 192.168.2.254/24 | Access Point IP address defines the IP address of your Hotspot's network |
| Authentication mode | External radius | Internal radius | Without radius | Advertisement | MAC auth | SMS OTP; default: Without radius | Authentication mode defines how users will connect to the Hotspot |
| Protocol | HTTP | HTTPS; default: HTTP | Connection protocol of your Hotspot |
| HTTPS to landing page redirect | yes | no; default: no | Redirects HTTP pages to landing page |
| SSL key file | .key file; default: none | SSL key file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| SSL certificate file | .crt file; default: none | SSL certificate file used for authentication. This field becomes visible only if HTTPS to landing page redirect is enabled |
| Use custom DNS | yes | no; default: no | Enables the use of custom DNS servers instead of your regular DNS |
| DNS server 1 | DNS server 2 | ip; default: none | Additional DNS servers that are to be used by the Hotspot. These fields become visible only if Use custom DNS is enabled |
Walled Garden
You can configure a list of addresses that users connected to the Hotspot will be able to reach without any authentication. By default this list is empty. Click the Add button to add a new address.
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; default: yes | Enables or disables an entry of the list |
| Address | host | ip; default: none | An address that users connected to the Hotspot can reach without authentication |
| Port | integer [0..65535]; default: none | Specifies the port through which the user can connect to the provided address. This field becomes visible only if Allow subdomains is disabled |
| Allow subdomains | yes | no; default: no | If checked, users can connect to the specified address and all of its subdomains |
Restricted Internet Access
The Restricted Internet Access page provides you with the possibility to restrict internet access on Hotspot on specified hours. Blue squares represent restricted access, white squares - allowed access. Bellow is an example of a configuration that restricts internet access outside of working hours.
Logging
The Hotspot Logging section is used to send Hotspot or Wireless information to an FTP or Syslog server.
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; default: no | Enables or disables whole logging section's fuctionality |
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; default: no | Toggles logging to Syslog ON or OFF |
| Server address | host | ip; default: " " | Syslog server address |
| Port | integer [0..65535]; default: " " | Syslog server port |
| Protocol | UDP|TCP default: TCP | Protocol of the syslog server |
| Prefix text | string; default: " " | Prefix custom text to streamed messages |
| Protocol filter | UDP|TCP|Any; default: Any | Filter log messages depending on protocol |
| Port filter | integer [0..65535]; default: " " | Filter log messages depending on port of port range |
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; default: no | Toggles logging to FTP ON or OFF |
| Server address | host | ip; default: your.ftp.server | FTP server address. |
| User name | string; default: username | User name used for authentication when logging into an FTP server |
| Password | string; default: password | Password used for authentication when logging into an FTP server |
| Port | integer [0..65535]; default: 21 | FTP server port |
| File name extras | No extra information | MAC address | Serial number | Custom string; default: No extra information | Extra information to be added to the log filename |
FTP Upload Settings
Here you can configure your timing settings for the log upload via FTP feature.
| Field | Value | Description |
|---|---|---|
| Mode | Fixed | Interval; default: Fixed | The scheduling mode to be used for uploading to FTP server |
| Hours | time; default: 8 hours | Time interval when the uploads will take place |
| Minutes | time;default: 15 minutes | Time interval when the uploads will take place |
| Days | time;default: Monday, Tuesday, Wednesday, Thursday, Friday | On which day upload will take place |
Wifi Log/SMS OTP Log
WiFi and SMS OTP logs show information about connections to your WiFi Hotspot. FTP logging has to be enabled.
Landing Page
This section is used to define how your Hotspot's Landing Page will look like.
Template
This is a template based on the default landing page. You can edit its HTML code to make it look however you want!
Custom Landing Page
Radius Server
This section is used to configure your Radius Server for use with Internal radius Authentication mode
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; default: no | Toggles Radius Server ON or OFF |
| Remote access | yes | no; default: no | Toggles remote access to the Radius Server ON or OFF. |
| Accounting port | integer [0..65535]; default: 1813 | Radius server accounting port |
| Authentication port | integer [0..65535]; default: 1812 | Radius server authentication port |
Session Settings
A Session Template is a set of rules that can be prescribed to a Hotspot user. A default template named unlimited is present in the router, but it has no configured restriction. You can edit the default template or you can create a custom template and configure it.
| Field | Value | Description |
|---|---|---|
| Idle timeout | integer; default: none | A timeout in seconds after which idle users are automatically disconnected from the Hotspot. 0 means unlimited |
| Session timeout | integer; default: none | A timeout in seconds after users are automatically disconnected from the Hotspot. The timeout countdown begins when a user is authenticated to the Hotspot and, after an amount of time specified in this field, the user gets disconnected from the Hotspot. 0 means unlimited |
| Download bandwidth | integer; default: none | Maximum download bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s or Gbit/s |
| Upload bandwidth | integer; default: none | Maximum upload bandwidth that the users assigned to this template can achieve. Bandwidth can be specified in Kbit/s, Mbit/s or Gbit/s |
| Download limit | integer; default: none | A received data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Download limit is specified in MB |
| Upload limit | integer; default: none | A sent data limit that the users assigned to this template can reach. After the data limit is reached, the user will lose data connection. Upload limit is specified in MB |
| Period | Month | Week | Day; default: Month | The beginning of the period during which the restriction specified in this section will apply. After the period is over, all specified limits are reset |
| Start day | Start hour | integer [1..31] | Monday..Sunday | integer [1..24]; default: day 1 | Specifies which day of the month, week or hour of the day the limits will be reset |
Users Configuration Settings
The Users Configuration tab is used to create new, unique users that can connect to the Hotspot.
| Field | Value | Description |
|---|---|---|
| Username | string; default: none | A custom user name used to authenticate clients connecting to the Hotspot |
| Password | string; default: none | A custom password for the specified user name |
| Session Template | string; default: unlimited | Session templates define session settings for different users. The unlimited Session Template is a default template with no restrictions. More on Session Template in the next section |
Clients Configuration Settings
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; default: yes | Toggles Clients Configuration ON or OFF |
| Client name | string; default: none | A custom user name used to authenticate clients connecting to the Hotspot |
| IP address | ip; default: none | The IP address of the client |
| Netmask | integer [0..32]; default: none | The netmask of the client |
| Radius shared secret | string; default: none | Radius shared secret used for communication between the client/NAS and the radius server |
Statistics
The Statistics page shows statistics about connections to the hotspot. Reminder: Statistics page becomes visible only when device is connected to the hotspot.
Manage
With the help of the Manage page you manage the users that are connected to your Hotspot. To reach the Manage window, go to Services->Hotspot. The Manage button will be located next to your Hotspot instance.
