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

    "Can't ping new VLAN Interface" (Bis)

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    22 Posts 4 Posters 2.0k 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.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator @cdarsac
      last edited by

      @cdarsac said in "Can't ping new VLAN Interface" (Bis):

      but it doesn’t work for me.

      Well post up your switch config as I did so we can see where your going wrong.. Looks to me like you just setup a tagged vlan on "all" of the lan ports.

      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.8, 24.11

      C 1 Reply Last reply Reply Quote 0
      • C
        cdarsac @johnpoz
        last edited by cdarsac

        @johnpoz

        This is:

        4666a9a6-2f06-4f9d-bf0e-7cf0f4490994-image.png


        c08626bf-0018-4efc-aec6-43e504d4b28c-image.png


        1cf4a862-4d2b-4a55-b388-8056e3e8b6e2-image.png


        H 1 Reply Last reply Reply Quote 0
        • H
          heper @cdarsac
          last edited by

          @cdarsac
          so you didn't set the pvid, members & untagged for port 1 to function with vlan40 ?

          C 1 Reply Last reply Reply Quote 0
          • C
            cdarsac @heper
            last edited by cdarsac

            @heper

            No, I haven’t done any of that yet.

            So I affect VLAN40 to Member "1".

            I suppose that it means VLAN40 is on "LAN 1".

            Is it correct for you ? ☺

            41bd27e8-8f40-4434-b914-359d9de25d22-image.png

            H 1 Reply Last reply Reply Quote 0
            • H
              heper @cdarsac
              last edited by

              @cdarsac no it's not correct. you are missing lots of things

              look at @johnpoz reply from 6 days ago (the one with the screenshots of his switch config)

              1)connect your laptop or pc to any lan-port except port1
              2)group vlan 0: remove port1 from the membres list
              3) group vlan 1: add port5, check 'tagged'
              4) goto interfaces->switch->ports (or interfaces->changer->ports for french)
              -----------> edit port 1 pvid & set it to 40

              above is a recap of https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/switch-overview.html
              step 15->26 are relevent ou applicable

              if nothing else is wrong, then that should be sort of work.
              if not. post more screenshots

              1 Reply Last reply Reply Quote 1
              • C
                cdarsac
                last edited by

                @heper said in "Can't ping new VLAN Interface" (Bis):

                @cdarsac no it's not correct. you are missing lots of things

                look at @johnpoz reply from 6 days ago (the one with the screenshots of his switch config)

                1)connect your laptop or pc to any lan-port except port1
                It's ok.

                2)group vlan 0: remove port1 from the membres list
                59d1e748-83f3-46f8-b8c1-dd06cf0f32f8-image.png

                1. group vlan 1: add port5, check 'tagged'
                  9ef6fb98-e470-4aba-8a47-dfcd5beec29d-image.png

                2. goto interfaces->switch->ports (or interfaces->changer->ports for french)
                  -----------> edit port 1 pvid & set it to 40
                  335f20ed-649a-4935-85ef-80520054c5b9-image.png

                above is a recap of https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/switch-overview.html
                step 15->26 are relevent ou applicable

                if nothing else is wrong, then that should be sort of work.
                if not. post more screenshots

                I have reboot the PC and the Nertgate.
                The PC can't ping the interface VLAN 140 (192.168.40.1). 😟

                H 1 Reply Last reply Reply Quote 0
                • H
                  heper @cdarsac
                  last edited by

                  @cdarsac said in "Can't ping new VLAN Interface" (Bis):

                  group vlan 1: add port5, check 'tagged'

                  i asked to ADD port 5 to "group vlan 1": good you did that
                  i did not ask to REMOVE port 1 from "groupe vlan 1": add it back
                  "groupe vlan 1" should have both port1 untagged & port5 tagged

                  C 2 Replies Last reply Reply Quote 1
                  • C
                    cdarsac @heper
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • C
                      cdarsac @heper
                      last edited by

                      @heper said in "Can't ping new VLAN Interface" (Bis):

                      @cdarsac said in "Can't ping new VLAN Interface" (Bis):

                      group vlan 1: add port5, check 'tagged'

                      i asked to ADD port 5 to "group vlan 1": good you did that
                      i did not ask to REMOVE port 1 from "groupe vlan 1": add it back
                      "groupe vlan 1" should have both port1 untagged & port5 tagged

                      Ok,I have come to understand: 😌
                      86cbe71c-eca6-45aa-8904-0587e950b248-image.png

                      NB: My unknown pb was that when I added member 5t to VLAN group 1, "5t" have automatically replaced "1".
                      So "1" was gone, without me erasing it.
                      I had to add it in a second time.
                      Sorry about this. 😕

                      1 Reply Last reply Reply Quote 0
                      • C
                        cdarsac
                        last edited by

                        And now, Interface VLAN40 responds to my ping (192.168.40.1).

                        Thank you very very much for your help ! 👍

                        1 Reply Last reply Reply Quote 0
                        • C
                          cdarsac
                          last edited by

                          Now, I wondered:

                          Why port5 must be tagged, and not the others ? 🙂

                          H 1 Reply Last reply Reply Quote 0
                          • H
                            heper @cdarsac
                            last edited by

                            @cdarsac i guess you should start by learning about vlans in general.
                            I don't have any links to any good tutorials / courses that go down to the basics of vlans

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