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

    pfsense stopped at vlan and interface prompt on every reboot

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    6 Posts 2 Posters 225 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.
    • D
      DaveQB
      last edited by

      Re: pfsense stopped at vlan and interface prompt on every reboot

      I have read this thread, but I am not using Tailscale. I have, what I thought, was a straight forward setup:

      WAN (wan) -> mvneta0 -> v4: 192.168.0.2/30
      LAN (lan) -> mvneta1 -> v4: 10.2.2.1/24
      BACKUPWAN (opt1) -> mvneta1.99 -> v4/DHCP4: 192.168.175.118/24

      But I can't reboot my SG-2100 without needing to plug a Micro USB cable and access the console to assign VLANs.

      Side note, the dialogue asks Should VLANs be set up now [y|n]? but proceeds to ask questions to configure them if you answer y or n

      Just upgraded to 23.09-RELEASE
      Previously 23.01

      Thank you.

      johnpozJ 1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator @DaveQB
        last edited by

        @DaveQB why would you not be running 24.11 - which is current?

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

        D 1 Reply Last reply Reply Quote 0
        • D
          DaveQB @johnpoz
          last edited by

          @johnpoz I didn't know this. 23.09 was all that was available in the web GUI. Either that or 23.05.

          johnpozJ 1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator @DaveQB
            last edited by

            @DaveQB I would upgrade to the current 24.11 or beta is 25.03 - and if still seeing the problem it will be easier to help you figure out what is going on.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.7.2, 24.11

            D 1 Reply Last reply Reply Quote 0
            • D
              DaveQB @johnpoz
              last edited by

              @johnpoz Thank you. I agree. 🤞 That resolves it.

              D 1 Reply Last reply Reply Quote 0
              • D
                DaveQB @DaveQB
                last edited by

                All upgraded to 24.11 yet issue remains unfortunately.

                Here's the output I am seeing on a reboot over serial. I think the key is this line:

                Warning: Configuration references interfaces that do not exist: mvneta1.99

                I am not sure why this is the case exactly. Is there anything from the config

                Welcome to Netgate pfSense Plus 24.11-RELEASE...
                
                ...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg /usr/local/lib/ipsec /usr/local/lib/perl5/5.36/mach/CORE
                32-bit compatibility ldconfig path:
                done.
                2880
                >>> Removing vital flag from php83...done.
                External config loader 1.0 is now starting...
                Launching the init system... done.
                Initializing.................... done.
                Starting device manager (devd)...2025-03-22T21:35:48.582133+11:00 - php-fpm 465 - - /rc.linkup: Ignoring link event during boot sequence.
                2025-03-22T21:35:48.591626+11:00 - php-fpm 466 - - /rc.linkup: Ignoring link event during boot sequence.
                2025-03-22T21:35:48.708691+11:00 - php-fpm 465 - - /rc.linkup: Ignoring link event during boot sequence.
                2025-03-22T21:35:48.758862+11:00 - php-fpm 1181 - - /rc.linkup: Ignoring link event during boot sequence.
                done.
                Loading configuration...2025-03-22T21:35:48.835769+11:00 - php-fpm 466 - - /rc.linkup: Ignoring link event during boot sequence.
                done.
                Updating configuration...done.
                Warning: Configuration references interfaces that do not exist: mvneta1.99
                
                Network interface mismatch -- Running interface assignment option.
                mvneta0: link state changed to DOWN
                
                Valid interfaces are:
                
                mvneta0 90:ec:77:0d:c5:b0 (down) NETA controller
                mvneta1 90:ec:77:0d:c5:b1   (up) NETA controller
                
                Do VLANs need to be set up first?
                If VLANs will not be used, or only for optional interfaces, it is typical to
                say no here and use the webConfigurator to configure VLANs later, if required.
                
                Should VLANs be set up now [y|n]? 2025-03-22T21:35:50.446791+11:00 - php-fpm 466 - - /rc.linkup: Ignoring link event during boot sequence.
                n
                
                
                VLAN interfaces:
                
                mvneta1.99      VLAN tag 99, parent interface mvneta1
                
                If the names of the interfaces are not known, auto-detection can
                be used instead. To use auto-detection, please disconnect all
                interfaces before pressing 'a' to begin the process.
                
                Enter the WAN interface name or 'a' for auto-detection
                (mvneta0 mvneta1 mvneta1.99 or a): mvneta0
                
                Enter the LAN interface name or 'a' for auto-detection
                NOTE: this enables full Firewalling/NAT mode.
                (mvneta1 mvneta1.99 a or nothing if finished): mvneta1
                
                Optional interface 1 description found: BACKUPWAN
                Enter the Optional 1 interface name or 'a' for auto-detection
                (mvneta1.99 a or nothing if finished): mvneta1.99
                
                The interfaces will be assigned as follows:
                
                WAN  -> mvneta0
                LAN  -> mvneta1
                OPT1 -> mvneta1.99
                
                Do you want to proceed [y|n]? y
                mvneta1: link state changed to DOWN
                Setting up gateway monitors...done.
                Setting up gateway monitors...done.
                
                Writing configuration...done.
                One moment while the settings are reloading... done!
                
                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.