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

    Cannot save WAN interface settings, "PPP Password and confirmed password …"

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 3.8k 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.
    • M
      mkudlacek
      last edited by

      Hello,
      I have a fresh installation of pfSense 2.3 for testing purposes. WAN interface has address from DHCP on network 192.168.4.0/24. LAN interface has static IP 192.168.66.254/24 with DHCP server on it. I want to remove the "Block private networks and loopback addresses" rule from WAN interface, so I could login from my network.
      When I uncheck the rule and try to save the new setting, this error message comes up:

      The following input errors were detected:
      PPP Password and confirmed password must match!

      I can't see any settings related to PPP and I'm pretty sure I haven't touch anything related to PPP anywhere else. Heck, I don't even need this functionality.

      Thanks for help in advance. Other than this error, pfSense looks great.

      1 Reply Last reply Reply Quote 0
      • S
        Steve_B Netgate
        last edited by

        Thanks for testing before you deploy :)

        The error is not immediately obvious since the password is only checked if mode == PPPoE or PPP. I was not able to reproduce the problem either. Would you please select PPPoE from the "Configuration type" selector(s) so that you can see what the passwords are currently set to? (No need to save) Same for PPP.

        If they are not blank, please clear both fields before switching back to DHCP and saving.

        Als ik kan

        1 Reply Last reply Reply Quote 2
        • M
          mkudlacek
          last edited by

          Steve,
          your suggestion worked like a charm. I feel a bit stupid for not figuring this on my own.

          Anyway, maybe it is a bug after all. When user configures interface to get IP from DHCP, it shouldn't take any other settings into consideration, doesn't it?

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