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

    Login is working but no Internet Access on some devices

    Scheduled Pinned Locked Moved Captive Portal
    11 Posts 5 Posters 2.3k 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.
    • N
      NickM
      last edited by

      Works fine for me.
      I have the same version. Are you running any other packages? Squid?

      1 Reply Last reply Reply Quote 0
      • L
        lugaru
        last edited by

        Okay now it gets strange.

        Reinstalled 2.2.5 fresh -> loaded config -> same Error
        Reinstalled 2.2.3 again -> loaded config -> same Error

        I dont have any additional Pakets installed.
        Authentication is done over Radius Server. As it seems the Problem only occurs over WLAN. We're using Ubiquiti Unifi APs there with an external controller. But there were no changes on this system.

        I really don't have any more Ideas how to fix this or find out where the Problem is… Also my own devices are all working fine.

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          Some mobie devices being Bitten Fruit (TM)? Yeah, they've broken RADIUS with latest IOS update. Has nothing to do with pfSense upgrade.

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

            Unless you are using EAP on the wifi there is no difference between a RADIUS backend and local user manager, etc, Apple device or not.

            What is the nature of the failure? No DNS? No layer 2? no layer 3? Is it all wi-fi or just some?

            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
            • L
              lugaru
              last edited by

              @doktornotor - this doesnt matter here. The Radius is only communicating with the pfsense box.

              @Derelict
              -nature: I don't know :(
              -DNS is working on the client. Pinging any Site gives me the correct IP, but a timeout.
              -Just some wifi devices. My Laptop and Phone is working, for 70-80% of the users it is working but for some it is not.
              -Layer 2 and 3 seems to be okay.

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

                Then it's your firewall rules on the captive portal interface.

                What is the IP scheme of your interface and what are the rules?

                Most captive portal failures (given a proerly-configured captive portal/network) are:

                Failure to bring up the CP login page - usually caused by initial navigation to an HTTPS site. http://10.10.10.10/ in a browser will always get the CP login page.
                Client not configured for DHCP.
                Client configured for DHCP but with static DNS servers.
                A proxy set in the client device.

                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
                • L
                  lugaru
                  last edited by

                  Okay, we've got new Hardware with a lot more of Power and a Fresh configuration. But now it is even worse and some Clients cant even connect to the login Page. (The ones which had Problems before). But now this happens even with deactivated CP.

                  Most Times it is an DNS Error now (wasn't before)… and you cant even ping 8.8.8.8.

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

                    @lugaru:

                    Okay, we've got new Hardware with a lot more of Power and a Fresh configuration. But now it is even worse and some Clients cant even connect to the login Page. (The ones which had Problems before). But now this happens even with deactivated CP.
                    Most Times it is an DNS Error now (wasn't before)… and you cant even ping 8.8.8.8.

                    The questions stays up:
                    @Derelict:

                    Then it's your firewall rules on the captive portal interface [interface].
                    What is the IP scheme of your interface and what are the rules?
                    …..

                    How is your firewall set up ?
                    The NIC is LAN or a OPT1 interface ?

                    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

                      I'm guessing a subnet mismatch somewhere - like /24 on the interface and /22 on the DHCP server.

                      Or a /22 on the interface and /24 in the firewall pass rules.

                      Or ???.

                      Post your interface config and your rules.

                      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
                      • L
                        lugaru
                        last edited by

                        Strange…

                        some hours later everything just worked fine on the new Machine... Until now there are no more problems.

                        I have multiple Nets...

                        Opt1, Opt2, Opt3, WAN -> Wan Connections
                        LAN -> Management Interface 192.168.30.0/24
                        Opt4 -> VLAN Interface for:
                        VLAN 31 -> WLAN 192.168.31.0/24
                        VLAN 32-36 -> Different LAN Vlans 192.168.32-36.0/24

                        I think that there was a Problem with the Multi WAN and the configured DHCP Servers...

                        Thanks @ all for the support ;) Hope that everything works now as expected.

                        Cheers

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