Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    No logout window

    Scheduled Pinned Locked Moved Captive Portal
    5 Posts 3 Posters 2.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      DyJ_athan
      last edited by

      Hi im a noob in pfsense im just wondering why the log out popout window does not appear. I have enable the logout feat. I am using Local user as my authentication. pls enlighten me on this thanks ???

      1 Reply Last reply Reply Quote 0
      • H
        hoba
        last edited by

        If your browser has a popupblocker it won't open the logout popup. This is most likely what is happening.

        1 Reply Last reply Reply Quote 0
        • D
          DyJ_athan
          last edited by

          thanks I can see the logout window now. added the address on popup blocker exemption. Im wondering is there a way that logout window is not a popup window so that I wont manually put each the address on each client browser. Client will go to a local site then they can logout there. Please help me this is a tedious work.  :'(

          1 Reply Last reply Reply Quote 0
          • H
            hoba
            last edited by

            The mainproblem with this is that there are not too many other options to make this work. The only option (that would need some code changes) would be to display a small frame at the top of the site that you originally wanted to go to after redirection with an "open logout-popup" link. As the user actively clicks this link the popup-blocker will allow this popup to open then. Not sure if anybody is interested in implementing such a change or how many work that would produce. It for sure would cause issues with syncing the captive portal against m0n0wall code later as we more or less only reuse the m0n0wallcode here. Maybe you can ask them to integrate this feature so we can stay syncable.

            1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan
              last edited by

              Just a side thought here.

              This 'problem' could be solved more radical - and more logical.

              If we presume that hotspot IP's, like the disconnect window, are always local LAN IP's, it would be nice to say to your browser "do not accept popups from the Internet…..' but popus coming from the LAN range should be accepted (always ?).

              Popups from a local source can’t be really annoying, because YOU, or the one that gave you YOUR connection, controls them.

              So: browsers should accept, or handle at a second level, popus coming from local IP’s (gateway in this case).
              On the Firefox feature request list this item exists.
              IE: keep on dreaming….

              When the gateway isn’t local, the problem is solved otherwise: users are asked to keep the main login windows open, so they can disconnect (they have to open a second browser window!).  This is important because many are actually billing for their ‘wifi/network’ usage. Loosing the disconnect windows/button introduces the opportunity for the operator to take another hour, or more, before disconnection for ‘non-usage’.

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.