Kind of "reverse" Captive Portal ?

  • Sirs,

    I'm thinking about this:  A way to ALLOW access, AFTER authentication, TO an IP camera stream located at a DMZ network FROM users located at internet

    I know that captive portal is designed to work the opposite way, but do you guys have any hint ?

    I thought using RADIUS to create users and/or groups, but I can't figure out how to create firewall rules to allow the access after the successful authentication occurs.

    Regards from Rio de Janeiro, Brazil.

  • @

    Captive Portal

    Captive portal allows you to force authentication, or redirection to a click through page for network access. This is commonly used on hot spot networks, but is also widely used in corporate networks for an additional layer of security on wireless or Internet access. For more information on captive portal technology in general, see the Wikipedia article on the topic. The following is a list of features in the pfSense Captive Portal.

    * Maximum concurrent connections - Limit the number of connections to the portal itself per client IP. This feature prevents a denial of service from client PCs sending network traffic repeatedly without authenticating or clicking through the splash page.
        * Idle timeout - Disconnect clients who are idle for more than the defined number of minutes.
        * Hard timeout - Force a disconnect of all clients after the defined number of minutes.
        * Logon pop up window - Option to pop up a window with a log off button.
        * URL Redirection - after authenticating or clicking through the captive portal, users can be forcefully redirected to the defined URL.
        * MAC filtering - by default, pfSense filters using MAC addresses. If you have a subnet behind a router on a captive portal enabled interface, every machine behind the router will be authorized after one user is authorized. MAC filtering can be disabled for these scenarios.
        * Authentication options - There are three authentication options available.
              o No authentication - This means the user just clicks through your portal page without entering credentials.
              o Local user manager - A local user database can be configured and used for authentication.
              o RADIUS authentication - This is the preferred authentication method for corporate environments and ISPs. It can be used to authenticate from Microsoft Active Directory and numerous other RADIUS servers.
        * RADIUS capabilities
              o Forced re-authentication
              o Able to send Accounting updates
              o RADIUS MAC authentication allows captive portal to authenticate to a RADIUS server using the client's MAC address as the user name and password.
              o Allows configuration of redundant RADIUS servers.
        * HTTP or HTTPS - The portal page can be configured to use either HTTP or HTTPS.
        * Pass-through MAC and IP addresses - MAC and IP addresses can be white listed to bypass the portal. Any machines with NAT port forwards will need to be bypassed so the reply traffic does not hit the portal. You may wish to exclude some machines for other reasons.
        * File Manager - This allows you to upload images for use in your portal pages.


    * Can only run on one interface simultaneously.
        * "Reverse" portal, i.e. capturing traffic originating from the Internet and entering your network, is not possible.
        * Only entire IP and MAC addresses can be excluded from the portal, not individual protocols and ports.
        * Currently not compatible with multi-WAN rules. We hope this will be resolved in 2.0.

Log in to reply