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

    Problem with captive portal on a non-nated interface

    Scheduled Pinned Locked Moved Captive Portal
    4 Posts 2 Posters 2.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.
    • P
      paketdos
      last edited by

      I am trying to set up a captive portal on an interface that does not have nat
      it use routable address

      i am using the 1.2.3 RC1 version.

      if i set the portal on OPT1 (a nated interface) everything works fine.
      if i switch frome OPT1 to OPT2 (a non-nated interace). the portal web page
      appear and i can loggin to it (i see my user in status page), but i cannot go any further

      i tried to run ipfw show, and i see automatic rule created for my IP, and i can see traffic
      going thru those rule (not blocked by the 19904 rule) but nothing come back to my internal
      machines

      i have searched the forum and web site. for similar case. but did not find any

      Is the captive portal compatible with non-nated interface?  has anyone succeeded in a
      similar configuration ?

      i will try different version, in a vmware lab i am setting up. but i was wondering if anybody knew
      something about this problem

      Thank for your reply
      Math

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

        Give more detials.
        This is just telling nothing!

        1 Reply Last reply Reply Quote 0
        • P
          paketdos
          last edited by

          Thanks for your interest.

          I was just wondering if my problem was a "known limitation" or
          if i have hit a bug\misconfiguration.

          the firewall is sort of a departemental-firewall, the organisation use a large
          10.x.y.z network. and the departement is a subnet of that large network.
          i cannot use NAT for that firewall.

          my WAN is a large 10.x.y.z
          my LAN is a 192.168.x.y (for testing with NAT activated)
          my OPT1 is a subnet of the large 10.x.y.z

          i started by setting up the captive portal on the LAN "testing" network
          and it worked fine.
          than i switched from LAN to OPT1 "production" network
          and all my traffic was blocked.

          this is firewall is now in production (without the portal) so i cannot do many test on it
          i will settup a test lab to reproduce the problem

          1 Reply Last reply Reply Quote 0
          • P
            paketdos
            last edited by

            So i did set up a lab

            and the captive portal works well with non-nated interface

            it is probably a misconfiguration on my part, i still dont know why
            it is not working in the production firewall. but i know it is possible.

            i will probably have to redo the whole configuration from scratch.

            thanks for your interrest
            Math

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