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

    Help with Vlan

    Scheduled Pinned Locked Moved Routing and Multi WAN
    25 Posts 3 Posters 4.9k 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.
    • J
      Jamerson
      last edited by

      @johnpoz:

      keep in mind if your going to be running vlans on your vswitch you need to set it to 4095

      thanks john,
      creating a vlan 4095 on the vswitch , creating vlan on the pfsense , and vlan on the physique switch and I am set to go ?

      thank you

      1 Reply Last reply Reply Quote 0
      • J
        Jamerson
        last edited by

        John can you please help ?
        i am stuck here.
        i've bought the VLAN WLAN device
        http://www.peplink.com/products/enterprise-access-point/pepwave-ap-one/#enterprise

        VLAN is configured on the pfsense
        VLAN 20 is configured on the switch on port 20
        the AP is attached on port 20 on the switch.
        VLAN 20 on the pfsense is having DHCP enabled
        On the vSwitch i've created a port group with ALL (4095 ) but can't get it work

        **when a use is connected to the AP they don't receive IP of VLAN 20 but of Default VLAN

        what i am doing wrong ?

        thank you**

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

          Sounds like the AP is sending traffic to the switch untagged. Change your switch port to an untagged port on VLAN 20 and connect the AP to it.

          That's fine but you can only do one SSID. Else you have to figure out how to tell the AP to tag the traffic from that SSID with VLAN 20 and leave the switchport like it is.

          I notice you did not specify whether you made port 20 tagged or untagged on VLAN 20. It matters.

          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
          • J
            Jamerson
            last edited by

            @Derelict:

            Sounds like the AP is sending traffic to the switch untagged. Change your switch port to an untagged port on VLAN 20 and connect the AP to it.

            That's fine but you can only do one SSID. Else you have to figure out how to tell the AP to tag the traffic from that SSID with VLAN 20 and leave the switchport like it is.

            I notice you did not specify whether you made port 20 tagged or untagged on VLAN 20. It matters.

            thank you so much for your answer.
            the port 20 is untagged on the VLAN20 on the physical switch.
            attached is a picture

            PS : there is no cable right now just had to disaconnect it .

            from the vswitch is the settings correct ?

            V20.jpg
            V20.jpg_thumb

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

              The settings on the switch are wrong or it would be working. The switchport going to the AP needs to be configured to match whatever the AP is configured to do.  Sorry, I don't have time to research your AP. You'll need to find out its capabilities.

              A VLAN with only one port on it can't talk to anything else. Where is your tagged port going to pfSense?

              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
              • J
                Jamerson
                last edited by

                A VLAN with only one port on it can't talk to anything else. Where is your tagged port going to pfSense?

                sorry I didn't get the question,
                can you ask it again ?

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

                  The fastest way to solve your issues is probably to find a networking text written in your native language that explains all this.

                  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
                  • J
                    Jamerson
                    last edited by

                    @Derelict:

                    The fastest way to solve your issues is probably to find a networking text written in your native language that explains all this.

                    thank you for your answer.
                    the idea is to configure VLAN20 and VLAN 30 using pfsense as VM in the ESXI 6.0
                    on the physical switch configure two ports for VLAN 30 and 20
                    Connect the AP 20 in VLAN 20 on the physical switch  and AP 30 In VLAN 30 port on the switch.
                    each VLAN is delivering a DHCP server .

                    thank you

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

                      Right. And I am in no mood to write up exactly how to configure all that for someone who apparently doesn't know the difference between tagged and untagged switch ports.

                      I hate to be harsh, but no. Maybe someone else.

                      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
                      • J
                        Jamerson
                        last edited by

                        @Derelict:

                        Right. And I am in no mood to write up exactly how to configure all that for someone who apparently doesn't know the difference between tagged and untagged switch ports.

                        I hate to be harsh, but no. Maybe someone else.

                        thank you for your answer,
                        the issue here is not knowing the different between tag and untag is the explanation .
                        hopefully someone can be kind and help me here out .

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