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

    Captive portal and idle timeout

    Scheduled Pinned Locked Moved Captive Portal
    5 Posts 3 Posters 1.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.
    • T
      ttsumak
      last edited by

      Hey,

      Idle timeout set to 8 hours, dhcp to 24 hours.

      What causes CP users not to timeout at all?

      Even if DHCP leases go up and down, CP users only go up.

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Idle timeout is the duration of zero traffic on the CP entry at all. Even so much as a DHCP release/renew or an ARP is enough to reset that timer.

        It is essentially used to see if a device has completely left the property. At that it excels.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • T
          ttsumak
          last edited by

          If DHCP release or renew is enough, why is there about 25% more CP users than dhcp leases? Seems like the CP user graph is just going up, but DHCP is fluctuating.

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

            @ttsumak:

            If DHCP release or renew is enough, why is there about 25% more CP users than dhcp leases?

            Don't know.
            I have a idle time : 60 minutes and a hard time auto : 6 hours - DHCP default ease time 86400 seconds or 24 hours.

            I know the idle-timer works : people leave the place, so "ghost-traffic" can't be possible.

            The hard timer is just a safety net.

            Seems like the CP user graph is just going up, but DHCP is fluctuating.

            Mine looks like this https://www.test-domaine.fr/munin/brit-hotel-fumel.net/pfsense.brit-hotel-fumel.net/portalusers.html

            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
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              Every wifi device that joins your network takes a DHCP lease whether they go through your portal or not.

              The pool size needs to be sized to accommodate your device churn and your lease times and your portal timeouts, hard or idle.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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