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.
    • JKnottJ
      JKnott @cdarsac
      last edited by

      @cdarsac

      That would tend to indicate a routing problem, but routing should happen automagically with direct connected networks. Try Packet Capture on both interfaces to see what turns up.

      PfSense running on Qotom mini PC
      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
      UniFi AC-Lite access point

      I haven't lost my mind. It's around here...somewhere...

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

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

        But the PC on the Vlan inferface can't ping this interface

        Lets see these rules.. Users are always saying they did X, when they really did (Y+42/pi)*1.6

        Connecting a device to a port you put on vlan in pfsense has zero to do with that client supports vlans or not.. Unless you were tagging the traffic leaving pfsense.. If that was the case your client wouldn't get an IP in the correct vlan space.

        Show your switch config on the 2100, show your rules on this vlan interface.

        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

          @johnpoz
          you’re right, I should have started with this. 🙂

          6417d1ec-f399-4f2b-a1ca-25370132739c-image.png

          7fbe07a1-dd25-453f-9df2-1a2d289a6de8-image.png

          a3d692a1-e369-46c1-b645-6557301fa353-image.png

          7da2f563-3659-4c29-b460-88756f745d06-image.png

          6f0552db-f4d2-4ec6-ba98-011e576b40e6-image.png

          7205868f-0a29-4e24-a9c6-22b29ac5bc2f-image.png

          da151e20-90b4-4dc5-b9dc-6ebb118a005a-image.png

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

            @cdarsac

            i don't have a netgate device at hand so i don't know the switch "menu" - but where did you set the port to untagged & specify the pvid ?

            something like here:
            https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/switch-overview.html

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

              @cdarsac

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

              When I ping the VLAN140 from console Putty session, it's ok 🙂
              57410350-42a4-4261-811b-6fad9e78fa61-image.png

              But when I ping the VLAN140 from my PC who is connected on LAN1 port, it's not ok. 🙁
              76d8ec14-57d9-44be-a5f8-c19b0701f54c-image.png

              Plan d'adressage IP:
              192.168.001.001-------- LiveBox @IP privée
              xxx.xxx.xxx.xxx---------- LiveBox @IP publique
              192.168.002.001-------- pfSense administration
              192.168.040.001-------- pfSence OPT1 Lan 40

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

                where is your switch config?

                Here is some ports on vlans (untagged) on one of my 3100s

                vlans.jpg

                Have you read
                https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/switch-overview.html

                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

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

                  Have you read
                  https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/switch-overview.html

                  Yes, I have read and execute https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/switch-overview.html, but it doesn’t work for me.
                  I don’t have to do it right

                  johnpozJ 1 Reply Last reply Reply Quote 0
                  • 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.