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

    No access to network due to captive portal on other interface

    Captive Portal
    1
    1
    172
    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
      Ehtor
      last edited by

      Hey there,

      I just startet using VLANs on my network and ran into a problem I couldn't solve so far. I created a new VLAN that is working, but only gets network access if I put the IP range of the VLAN into the "Allowed IP Addresses" of a captive portal that's only active (and reachable) on my "main" interface/VLAN. Is there any way around this or do I have to create another captive portal zone and allow the IP range like that. (Which seems a bit odd to me)

      If I only have captive portals on the vlans of the interface, everything seems to work fine. But as soon as there is a cp on the interface itself the vlans go crazy.

      My ideal setup would be:

      LAN = vtnet2 (with Captive Portal)
      WiFi = VLAN 100 on vtnet2 (with CP)
      Servers = VLAN 200 on vtnet2 (without CP)

      Currently using pfSense 2.6.0.

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