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

    Working but no redirect

    Scheduled Pinned Locked Moved Captive Portal
    5 Posts 4 Posters 1.9k 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.
    • E
      Evilgoat
      last edited by

      Have two identical machines here running Captive portal, we are migrating to a new machine and ye olde PFsense box is getting upgraded a little. We have both running side by side. Both are on the latest stable releases however one is AMD64 and one is i386

      i386 machine - ye olde faithful, CP works as it always have, no issues at all.
      AMD64 Machine, CP sort of works but the redirect page is never shown.

      Both are configured identically. I'm still digging at the moment but has anyone had any luck with the AMD64 stable and CP?

      i386 machine is a Sempron/HD, New machine is an Athlon X2/SSD, identical in every other respect, same board etc. I'm just gonna try a fresh i386 install and see what happens.

      Progressively rolled forward to 2.1-beta and it wont work. going to pfsense:8000 gets a login window, then loging in gets you access to the outside world as it should. However www.google.com just times out.  The working system is 2.0.2-RC3 and does what it says on the tin.

      Is this a dns redirect? Eg if I do nslookup www.google.com on the interface behind the CP what should I be seeing?

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

        Not sure if it is related, but 2.0.2 seems to swallow the first forward slash '/' in the redirect url, so if the redirect url was originally "www.google.com/images", the CP tries to redirect the client to "www.google.comimages".

        1 Reply Last reply Reply Quote 0
        • N
          Nachtfalke
          last edited by

          I had sometimes problems if the redirect URL was just:
          www.google.com
          I renamed it to:
          http://www.google.com
          and it worked.

          1 Reply Last reply Reply Quote 0
          • E
            Evilgoat
            last edited by

            Sorry that wasnt clear. Going direct to the login page works, but the redirect to the login doesnt. eg go to http://www.google.com/ and you SHOULD get a login page, however you dont and the session times out. Go to the login page direct and its fine.

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

              likely you're breaking DNS by not using the DNS forwarder or permitting the DNS server IPs

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