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

    Captive Portal still error

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    12 Posts 5 Posters 4.0k 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.
    • Z
      zchellpy
      last edited by

      pfSense 2.0 snapshot for April 15, is still problematic for captive portal, is there any solution …???

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        Just add a firewall rule to allow port 80 from any to any TCP and it will work out.

        1 Reply Last reply Reply Quote 0
        • Z
          zchellpy
          last edited by

          @ermal:

          Just add a firewall rule to allow port 80 from any to any TCP and it will work out.

          I Get some errors again in snapshot 20 April….
          php[24906]: /services_captiveportal.php: The command '/sbin/ipfw table all flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available'

          U have solution sir ermal….

          1 Reply Last reply Reply Quote 0
          • E
            eri--
            last edited by

            Update your snapshot because ipfw is failing to load for you.

            1 Reply Last reply Reply Quote 0
            • Z
              zchellpy
              last edited by

              hello ermal.

              i have update with 21 snapshot but result it same, not change n still have problem

              php: /services_captiveportal.php: The command '/sbin/ipfw table all flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available'

              kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled

              please help me…

              1 Reply Last reply Reply Quote 0
              • S
                Slam
                last edited by

                I've upgraded to pfSense-Full-Update-2.0-BETA1-20100421-2213 + gitsync'd and also seeing the same error reported by zchellpy.

                Thanks

                Slam

                1 Reply Last reply Reply Quote 0
                • J
                  jamesclements
                  last edited by

                  php: /services_captiveportal.php: The command '/sbin/ipfw table all flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available'

                  21st of April snapshot, same issue here.

                  1 Reply Last reply Reply Quote 0
                  • Z
                    zchellpy
                    last edited by

                    Only 1 April snapshot is good and no problem with captive portal.

                    1 Reply Last reply Reply Quote 0
                    • Z
                      zchellpy
                      last edited by

                      ermal in snapshot 23 I have same issue errors

                      php: : The command '/sbin/ipfw table all flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available'

                      what is different in captive portal beetween snapshot 1 April with 23 April….???

                      Thanks Before,

                      Ermal

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        The date on FreeBSD RELENG_8 was bumped, which broke some things related to ipfw that Ermal fixed late today. 24th snapshots will have that.

                        1 Reply Last reply Reply Quote 0
                        • Z
                          zchellpy
                          last edited by

                          In 24 snapshot is still have same log in system logs

                          php: : The command '/sbin/ipfw table all flush' returned exit code '71', the output was 'ipfw: Warn: Failed to get the max tables number via sysctl. Using the compiled in defaults. The reason was: No such file or directory ipfw: setsockopt(IP_FW_TABLE_FLUSH): Protocol not available'

                          but captive portal can run so well….

                          sir Dev can I know what happaned....????

                          1 Reply Last reply Reply Quote 0
                          • E
                            eri--
                            last edited by

                            Nothing to worry is innocuous error, i see if it can be masked out totally.

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