We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

This Firmware Version Is End-Of-Support

Documentation for this product is no longer updated. Please see End-of-Support for CloudGen Firewall Firmware for further information on our EoS policy.

How to Configure Wi-Fi Guest Access

  • Last updated on

Wi-Fi guest access can only be used for Wi-Fi users. For a more generic guest access configuration (ticketing and confirmation page), see Firewall Authentication and Guest Access.

You can configure a fully customizable web-based portal that displays a disclaimer and requests login credentials from users when they first try to access the Internet or special network segments. For example, you can configure a Guest Access that looks similar to the following page: 

GuestAccess01.png

To administer tickets for the Guest Access, you can also enable a web-based backend user interface for creating, deleting, managing, or printing tickets. 

In this article:

Step 1. Enable Guest Access

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > Wi-Fi > Wi-Fi AP Configuration.
  2. Click Lock.
  3. From the Guest Access list, select either Confirmation or Ticketing. If you want to disable the Guest Access, select None.
  4. Click Send Changes and Activate.

Step 2. Configure Guest Access

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > Firewall > Forwarding Settings.
  2. In the left menu, select Guest Access.
  3. Click Lock.

  4. You can specify the following settings for the Guest Access:

    SectionSettingDescription
    TimingRenew Confirmation After (min.)

    The time period after which users must re-enter their login credentials. 

    When deleting ticketing users, the user can still access the guest network for the duration of this value. To force a user to be blocked immediately you must delete the ticketing or confirmation user in FIREWALL > Users and terminate all existing firewall sessions in FIREWALL > Live for that user.

    Auto. Renew ConfirmationConfirmation is automatically renewed within this time period, after the last confirmation has timed out. The user does not need to re-enter login credentials.
    Customization (Confirmation)Custom Text

    Custom text that is displayed on the confirmation window. If left blank, the default Barracuda Networks disclaimer is displayed.

    Header Logo(Only visible in advanced view) The customizable header image for confirmation Guest Access.
    Before specifying an image in this field, you must upload it. From the Configuration menu in the left navigation pane, click Authentication Messages. Add the picture to the Custom HTML Files table within the lP subdirectory.
    Custom Page

    (Only visible in advanced view) A custom index.html file for the Guest Access. See the description below this table to learn how to configure the custom HTML code.
    Before specifying an index.html page in this field, you must upload it. From the Configuration menu in the left navigation pane, click Authentication Messages. Add the file to the Custom HTML Files table.

    Customization (Ticketing)Custom TextCustom text that is displayed on the confirmation window. If left blank, the default Barracuda Networks disclaimer is displayed.
    Header Logo(Only visible in advanced view) The custimizable header image for ticketing Guest Accesss. From the Configuration menu in the left navigation pane, click Authentication Messages. Add the picture to the Custom HTML Files table within the lP subdirectory.
    Custom Page(Only visible in advanced view) A custom index.html file for the Guest Access. See the description below this table to learn how to configure the custom HTML code.
    Before specifying an index.html page in this field, you must upload it. From the Configuration menu in the left navigation pane, click Authentication Messages. Add the file to the Custom HTML Files table.

    Ticketing Administration User

    Username

    The username for the administrator of the ticketing list backend page.

    PasswordThe password for the administrator of the ticketing list backend page.
    Additional Guest Access NetworksNetwork

    Defines additional network segments (except the Wi-Fi network where Guest Accesss are served to clients). You can select a network object or manually enter a network segment.

    Type

    The type of Guest Access for the additional network segments. You can select Confirmation or Ticketing.


    The customizable index.html page mentioned above is also the HTML template for the Next TokenNew Pin, Accept New Pin and One-time Password Authentication pages. You can use special tags in HTML comments within the index.html to enter content to be displayed only on the respective pages. The following tags are available:

  • Next token: %%NEXTTOKENMSG-BEGIN%% %%NEXTTOKENMSG-END%%
  • New pin: %%NEWPIN-BEGIN%% %%NEWPIN-END%%
  • Accept new server-generated PIN: %%ACCEPTNEWPIN-BEGIN%% %%ACCEPTNEWPIN-END%%
  • One-time password authentication: %%OTP-BEGIN%% %%OTP-END%%
    Start your conditional HTML code block with a comment tag (<!–) directly followed by the respective special opening tag, and end it with a closing comment tag (-->) directly preceded by the respective special ending tag.


<!--

%%NEXTTOKENMSG-BEGIN%%

<div id="twofactorinfo">

<p>RSA ACE server requires a<br><strong>Next token authentication</strong>.<br>

Please enter the next token as Password.<br>

</div>

%%NEXTTOKENMSG-END%%

-->
The following code block writes the token ID into a hidden form field and is therefore always required. Copy and paste it into your HTML page.

<!--

%%NEXTTOKEN-BEGIN%%

<input

type=hidden

name="nexttoken"

value="%%NEXTTOKEN%%"/>

%%NEXTTOKEN-END%%

-->

View Authenticated Users

To see a list of authenticated users, go to the FIREWALL > Users page. On this page, successfully authenticated users are listed with either the LP- or TKT- prefix, followed by the IP address of the client.

Authenticated Users in Access Rule

Using the IP addresses on the FIREWALL > Users page, you can create access rules to regulate network access for authenticated users. In the rule editor window, specify the authenticated users in the Authenticated User field.

For example, a user is successfully authenticated from the Guest Access on a client with the IP address of 172.16.10.100. On the FIREWALL > Users page, the authenticated user is displayed with the following identity: LP-172.16.10.100. In the following access rule example, this identity string is used to allow Internet access for users that are authenticated on the Guest Access in the 172.16.10.0/24 network: 

Wifi_GA_02.png

The user=LP-172.16.10 string indicates that this access rule only applies to users who are residing in the 172.16.10.0/24 network and are currently authenticated through the Guest Access.

For more information on creating access rules, see Firewall Access Rules.

Guest Access Ticketing System

To administer tickets for the Guest Access, the Barracuda NextGen Firewall F-Series offers a web-based backend user interface for creating, deleting, managing, or printing tickets.

ticket_admin_3.PNG

Access to the Admin Ticket Interface

HTTP requests (port 80/443) that are addressed to the system that is running the Guest Access must be forwarded to the local web server of the system. Create a access rule that forwards these HTTP requests to the local web server.

It is recommended that you use TCP port 8080 (or similar). For more information, see How to Create an App Redirect Access Rule.

Wifi_GA_01.png

Ticketing Next Steps

After you create a access rule that grants access to the ticket system, you can connect to the ticketing interface from a web browser.

  1. In a web browser, enter: http://<IP:port>/lp/cgi-bin/ticketing
  2. On the ticketing system login page, enter the login credentials that you specified in the Ticketing Administration User section when configuring the Guest Access.

For more information, see How to Manage Guest Tickets - User's Guide.

Last updated on