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

    Vlan Interface listed wrong, als listed wrong for netif

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 3 Posters 2.1k 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.
    • B
      bbehrendt
      last edited by

      I am trying to figure out a issue where only Vlan1 can access the internet (see previous post).  One thing I noticed is that when I look at the interface listing, it lists the wrong VLAN to description.  Also looking at the route table it has a colum netif, that looks like a vlan label but it too is not correct.

      I double checked the assignment page and I have all the vlans listed as they should.  The only thing I can tell, is that on the interface=>vlans page the vlans listed on the interface sheet match the order they were entered in, and not the tags I gave them.

      screenshots attached.

      -bj
      interface.png
      interface.png_thumb
      ![route table.png](/public/imported_attachments/1/route table.png)
      ![route table.png_thumb](/public/imported_attachments/1/route table.png_thumb)
      vlan.png
      vlan.png_thumb
      vlan2.png
      vlan2.png_thumb

      1 Reply Last reply Reply Quote 0
      • N
        Nachtfalke
        last edited by

        you can fix the order in the config.xml by editing the file and then restore it to pfsense.

        1 Reply Last reply Reply Quote 0
        • B
          bbehrendt
          last edited by

          brand new to pfsense, how do I edit the config.xml file?

          1 Reply Last reply Reply Quote 0
          • N
            Nachtfalke
            last edited by

            diagnostics -> backup/restore

            backup the config.xml file.

            after this, use and editor like notepad++ (windows) and search the config file for you vlans
            then you will see some blocks which you coukld rearrange with cut and paste.

            after this go to
            diagnostics -> backup/restore
            restore the modified config.xml

            1 Reply Last reply Reply Quote 0
            • B
              bbehrendt
              last edited by

              The backup restore didn't work as expected so I just wiped the vlan interfaces and started over.  I am still getting the issue.  Right now I entered Vlan1 and it shows up correctly on the interfaces menu, but under Status Interfaces it shows up as Vlan0.

              I attached screenshots.

              -bj

              interface.png
              interface.png_thumb
              ![vlan assign.png](/public/imported_attachments/1/vlan assign.png)
              ![vlan assign.png_thumb](/public/imported_attachments/1/vlan assign.png_thumb)
              ![vlan tag.png](/public/imported_attachments/1/vlan tag.png)
              ![vlan tag.png_thumb](/public/imported_attachments/1/vlan tag.png_thumb)

              1 Reply Last reply Reply Quote 0
              • B
                bbehrendt
                last edited by

                This must be a bug in the system.    What I wound up having to do is to enter each Vlan in starting with Vlan0 in order that they needed to go in under Interface Vlan (Entering in the Vlan ID did nothing).  Then just add the opt interfaces that matched the vlans I wanted.

                -bj

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  The vlan interface names on 1.2.3 (vlan1, vlan2, etc) have no correlation to the vlan tag. If you have four VLAN tags setup, you'll have vlan0..vlan3.

                  On pfSense 2.0 the interfaces are renamed to reflect the proper tag and parent interface. For example if you have vlan tag 20 set on bge0, it gets named bge0_vlan20.

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

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