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

    VLAN's not working with pfSense and HP1810-24G Switch.

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    39 Posts 7 Posters 3.7k 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.
    • DerelictD
      Derelict LAYER 8 Netgate
      last edited by

      Tagged VLAN 1 😱

      Chattanooga, Tennessee, USA
      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
      Do Not Chat For Help! NO_WAN_EGRESS(TM)

      HermanH 1 Reply Last reply Reply Quote 0
      • HermanH
        Herman @Derelict
        last edited by Herman

        @derelict said in VLAN's not working with pfSense and HP1810-24G Switch.:

        Tagged VLAN 1 😱

        @Derelict, you are screaming... Please tell me why?

        Limburg | The Netherlands.
        It is nice to be important. But it is more important to be nice! | Failure, the best teacher it is!

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

          And again.. If vlan 1 is native and default which is almost always is.. Since its the default vlan it would be untagged.

          There is ZERO reason to tag vlan 1 as you have it designed. That its working is telling me the hyper-v setting is stripping it so pfsense sees it as untagged. Or it wouldn't work.

          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

          HermanH 1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by Derelict

            Depending on tagged VLAN 1 will cause you grief from now until forever because vendors do not agree on how that should be handled.

            In your position I would fix Hyper-V to understand that VLAN 1 is the untagged, default VLAN.

            Or I would cease using VLAN 1 with Hyper-V.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • HermanH
              Herman
              last edited by

              @johnpoz @Derelict

              Sorry guys, I do not understand it completely. Are you guys saying I should not use VLAN1 (default) at all? Because when I set port 1 in VLAN1 to Untagged, port 1 on VLAN10 will automatically switch to Exclude! When I create an additional VLAN20, then I am able to set port 1 for VLAN10 and 20 to Untagged. Could you please en light me here?

              Gr. Herman

              Limburg | The Netherlands.
              It is nice to be important. But it is more important to be nice! | Failure, the best teacher it is!

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

                You can use vlan 1 all you want as native untagged vlan - this is the default vlan on all switches.. But you wouldn't tag it..

                Please post the output of
                Get-VMnetworkAdaptersVlan

                And the exact setup of pfsense.. Do you have more than 1 vm interface in pfsense? What vswitches is it connected too.. You have different types of vswitches in hyper-v.. Do I really need to fire that crap they call hyper-v back up? ;)

                You can use any vlans you want on your switch for your connections to pfsense.. Does not have to be vlan 1..

                Derelicts point is you almost never vlan 1 tagged... Why do you think you should tagg it in your switch if you set it as native (or untagged) in your vswitch settings? And how do you have it setup in pfsense.. I you do not have it tagged in pfsense, and you don't have it tagged in your vswitch... Why would you tag it on your physical switch?

                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

                1 Reply Last reply Reply Quote 0
                • HermanH
                  Herman @johnpoz
                  last edited by Herman

                  @johnpoz said in VLAN's not working with pfSense and HP1810-24G Switch.:

                  And again.. If vlan 1 is native and default which is almost always is.. Since its the default vlan it would be untagged.

                  There is ZERO reason to tag vlan 1 as you have it designed. That its working is telling me the hyper-v setting is stripping it so pfsense sees it as untagged. Or it wouldn't work.

                  Sorry Johnpoz, I don't understand. On the HP switch I only can both vlans set to tagged. When I set vlan1 to untagged, vlan10 is set to exclude...

                  The output results of Get-VMNetworkAdapterVlan ;
                  This is the LAN interface of the pfSense box.

                  0_1552416277390_ad0839df-1504-491c-bb43-365ce392e3a5-image.png

                  My setup of pfsense box;

                  Both interfaces are Hyper-V virtual switches.
                  0_1552417053772_d21410d1-23d9-4d4e-a07d-da80f4b9efd5-image.png

                  0_1552416607139_56410e5b-b99a-4e49-a74a-4c94c53ad913-image.png

                  0_1552416647868_8d4e40cd-e335-4d8a-a80a-73ad72c97c42-image.png

                  Hope this helps? Let me know if you need more input.

                  Gr. Herman

                  Limburg | The Netherlands.
                  It is nice to be important. But it is more important to be nice! | Failure, the best teacher it is!

                  1 Reply Last reply Reply Quote 0
                  • DerelictD
                    Derelict LAYER 8 Netgate
                    last edited by Derelict

                    As far as I know, the HP switches were derived from Brocade.

                    On the Brocade, if you wish to mix tagged and untagged traffic on a switch port you would set the port to dual-mode.

                    If you want the PVID to be the default VLAN 1, you would do this:

                    # vlan 223
                    #  tagged eth 1/1/6
                    # int eth 1/1/6
                    #  dual-mode
                    

                    VLAN 1 is now the untagged PVID and 223 is tagged

                    If you want the PVID to be other than VLAN 1, you would do this:

                    # vlan 223
                    #  tagged eth 1/1/6
                    # vlan 224
                    #  tagged eth 1/1/6
                    # int eth 1/1/6
                    #  dual-mode 224
                    

                    VLAN 224 is now the untagged PVID and 223 is tagged.

                    Both configurations assume a starting point of eth 1/1/6 being a member of only the default VLAN 1.

                    This is an example of why mixing tagged and untagged traffic on an interface always contains disclaimers stating that different vendors handle things in different ways there.

                    Chattanooga, Tennessee, USA
                    A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                    DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                    Do Not Chat For Help! NO_WAN_EGRESS(TM)

                    1 Reply Last reply Reply Quote 1
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by Derelict

                      As an aside, adding ports, tagged or untagged, to VLAN 1 is not allowed at all on that switch. A port is a member of untagged VLAN 1 if it is not a member of any other VLAN, or if dual-mode is set as in example 1 above. As far as I know there is no way to tag VLAN 1 at all.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      HermanH 1 Reply Last reply Reply Quote 0
                      • HermanH
                        Herman @Derelict
                        last edited by

                        @derelict said in VLAN's not working with pfSense and HP1810-24G Switch.:

                        As an aside, adding ports, tagged or untagged, to VLAN 1 is not allowed at all on that switch. A port is a member of untagged VLAN 1 if it is not a member of any other VLAN, or if dual-mode is set as in example 1 above. As far as I know there is no way to tag VLAN 1 at all.

                        Hi Derelict,

                        Thaks for your input. Please have patience with me. I am not a guru like you guys. I wish to have all that knowledge!

                        This is how I configured the HP switch.

                        0_1552418696434_dfdba960-c52c-4f0e-907d-093b5e4dbe8e-image.png

                        0_1552418735392_c57d07df-ea8f-4db5-b3f1-2c7f48f25c79-image.png

                        Gr. Herman

                        Limburg | The Netherlands.
                        It is nice to be important. But it is more important to be nice! | Failure, the best teacher it is!

                        1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          What port are we talking about?

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                          HermanH 1 Reply Last reply Reply Quote 0
                          • HermanH
                            Herman @Derelict
                            last edited by

                            @derelict said in VLAN's not working with pfSense and HP1810-24G Switch.:

                            What port are we talking about?

                            Port 1 is connected to the LAN interface of the pfSense. Is that what you mean?

                            Limburg | The Netherlands.
                            It is nice to be important. But it is more important to be nice! | Failure, the best teacher it is!

                            1 Reply Last reply Reply Quote 0
                            • DerelictD
                              Derelict LAYER 8 Netgate
                              last edited by

                              So set VLAN 1 on port 1 to Untagged.

                              Chattanooga, Tennessee, USA
                              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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