Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Boot Environment naming

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 119 Views 2 Watching
    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 Offline
      mvikman
      last edited by mvikman

      Documentation on Boot environments states that BE name must only contain characters from the set a-z, A-Z, 0-9 and _
      I've seen dot used in the BE name on FreeBSD articles/forum posts and also on some pfSense related videos.
      I have previously used a dot in the BE name myself and everything has been working ok, but now upon making a clean install, I noticed that there's an "allowed character set".
      Is there a reason why a dot shouldn't be used?

      pfSense Plus 26.07-RELEASE (amd64)
      Dell Optiplex 7040 SFF
      Core i5-6500, 24GB RAM, 2x 240GB SSD (ZFS Mirror)
      HPE 561T (X540-AT2), 2-port 10Gb RJ45
      HPE 562SFP+ (X710-DA2), 2-port 10Gb SFP+

      1 Reply Last reply Reply Quote 0
      • stephenw10S Offline
        stephenw10 Netgate Administrator
        last edited by

        Hmm, interesting question. The gui allows a dot and it boots into it fine. But I have lingering memory about excluding it specifically. 🤔

        I can only recommend not using it.

        1 Reply Last reply Reply Quote 0
        • stephenw10S Offline
          stephenw10 Netgate Administrator
          last edited by

          Mmm, I think I was recalling this: https://forum.netgate.com/topic/197423/after-upgrading-to-25-03_beta-cloned-boot-environment-now-have-php-fatal-error-code-and-blank-blue-page-when-attempting-to-access-boot-environments

          Which unfortunately never really reached a satisfactory conclusion.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
          Privacy Policy · Cookie Policy