In that type of situation, all users behind a router will show up to the portal with the MAC address of the intermediate router. If this option is set, the portal will not attempt to ensure that the MAC address of clients stay the same while they are logged into the portal.
In certain use cases, users may only need to authenticate once per device, and then the client should not see the portal login again unless they change devices. Setting up pass-through MAC entries can automatically achieve this goal. If this option is set, the portal automatically adds a MAC passthrough entry after the user has successfully authenticated.
Users of that MAC address will never have to authenticate again unless so long as the entry is present in the configuration. If this option is set, the portal saves the username used during authentication along with the pass-through MAC entry.
Captive Portal can also optionally rate-limit users to keep them from using too much bandwidth. The Default download and Default upload fields define the default values for user bandwidth, specified in Kilobits per second.
If the fields are blank or set to 0 , then users have unlimited bandwidth. When set, enables upload controls for manually crafted portal pages. When unset, simple portal page customization controls are available Captive Portal Login Page. These simple customization controls enable small changes to the portal page without writing custom HTML. When set, the portal page includes the custom image from Logo Image instead of the default logo. When set, the portal page includes the custom image from Background Image instead of the default background.
Text displayed by the portal to the user to which the user must agree before they are permitted to login. This section configures authentication for Captive Portal.
This option allows users to authenticate with a username and password or vouchers. The authentication is handled by the local user database User Management and Authentication or an authentication server Authentication Servers. Vouchers are pre-generated access codes which grant short-term access to users. Vouchers may be used in addition to, or instead of, user authentication.
For more information on using vouchers, see Vouchers later in this section. The portal only requires users to click through the login page for access. The form must still be submitted, but it does not need to have any user entry fields, only a submit button. Users must still attempt an HTTP connection so the portal will see the attempt and perform the initial authentication.
A multi-select control where one or more primary authentication servers, or the local database, can be set for use by the portal. See Primary Authentication Source for more information.
Additionally, the Local Authentication Privileges option can limit access to only users who possess the proper access privileges. When an LDAP server is active in the control, it is used by the portal for authentication as-is. There are no additional options for LDAP server behavior.
Similar to Authentication Server , but sets up an additional separate means of authentication using distinct fields. See Secondary Authentication Source for more information.
If the first server is down, the portal will attempt authentication using the other servers in the list, in order top down. The secondary authentication source defines a completely separate authentication setup from the primary. For example, the primary source could be traditional usernames and passwords, while the secondary could be pre-paid card numbers or PINs.
The privilege can be directly on their account or inherited via group membership.. Upload the 'error. Upload the rest of the files with the pre-fix 'captiveportal-' into the File Manager.
Proposed Updates Variety of authentication pages to match different usages. When Logout button was clicked the client was disconnected from the portal. Infact I have tried the code provided by fhaeberle also. The Logout button doesn't disconnect the client from the portal. Thanks Gertjan Logout is working with that change.
Hi Daniel, Did you able to do that modification in the end? I'm on the same boat with exactly the same target in mind; any help would be very much appreciated!! Get the source of the default html page. Remove the lines that reference the User and password entry boxes. TEST - and loop to start if errors. Sort of figured that out after posting.
Made a custom captive-portal suit, which I'm going to put that in github, for anyone likes to replace the stock pages. Register Login. Reply Reply as topic. This topic has been deleted. Only users with topic management privileges can see it.
Awesome pfsense login pages template for your captive portal! GitHub Link Supports latest version of pfsense. The login sites are based on google material thinking, full responsive and support all modern browsers. Wow, the new CP looks great! Best regards Daniel. Skip to content. Star View license. Branches Tags. Could not load branches. Could not load tags.
0コメント