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

    Something goes wrong with i change LAN IP

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 1.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.
    • I
      itson
      last edited by

      Hi, I have a up and running PFSense with lan ip of 192.168.1.1 with captive portal running with vouchers for my hotel.
      as of right now, EVERYTHING is working perfect EXCEPT when i change LAN ip from 192.168.1.1 to 192.168.0.1
      I also change the DHCP Server range from 192.168.1.10 - 254 TO 192.168.0.10 - 254

      so when i click save and apply changes,
      MY PC gets ip of the new range of the 0.x
      when i try to access internet it opens captive portal voucher auth
      when i type the voucher it just seems like refreshes the page doesnt redirect and doesnt let me connect to the internet.
      after trying to figure out what it could be and started getting calls from customers that they cant connect, i quickly had to change ip and dhcp ips back to 192.168.1.1 range

      what do u guys think i missed?

      Change LAN IP from 192.168.1.1 to 192.168.0.1
      Change DHCP IP Range from 192.168.1.10-254 to 192.168.0.10-254

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        It has been my experience that some major configuration changes to pfSense don't correctly clear the old values so that new values can properly take effect. I suggest you save (but not apply) the LAN IP subnet change then reboot for it to take effect.

        @itson:

        when i type the voucher it just seems like refreshes the page doesnt redirect and doesnt let me connect to the internet.

        I would be helpful to know what the browser did do (for example, what was shown in the location bar? did the browser report a name resolution problem?) as well as what it didn't do.

        @itson:

        after trying to figure out what it could be and started getting calls from customers that they cant connect, i quickly had to change ip and dhcp ips back to 192.168.1.1 range

        PERHAPS some of these customers still had DHCP leases for IP addresses in the 192.168.1.x range.

        PERHAPS you needed to restart Captive Portal (Disable then enable) after the IP address change.

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