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

    SG-1000 VLANS don't seem to work.

    Scheduled Pinned Locked Moved
    Official Netgate® Hardware
    7
    21
    4.9k
    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.
    • ?
      A Former User
      last edited by

      Hi Everyone,

      I bought a SG-1000 a few months ago and am now getting around to setting it up and having a really hard time getting VLANs to work.

      Steps:

      • After factory reset or flash
      • Go through wizzard and everything works with the LAN interface configured on the cpsw1 port, can get DHCP address, can get to webgui, can ping from a laptop connected to the device directly or through a switch.
      • Create a new vlan in "Interfaces" -> "Assignments" -> "VLANs"
      • Parent interface is cpsw1
      • VLAN tag is "10"
      • Name is "LAN"
      • On the "Interface Assignments" tab
      • Move the "LAN" interface to "VLAN 10 on cpsw1"
      • Wait for all the settings to apply
      • Move the laptop to a port on the switch on VLAN 10 and nothing, no DHCP, assigned manually, no ping, cannot load webui.
      • Using the console cable, connect to the SG, I can start a packet capture and once I do, everything starts working, stop the packet capture, and it stops working again. I can see on the packet capture the switch is tagging it with the correct number.

      18:18:53.197593 00:90:f5:fb:f0:8d (oui Unknown) > ec:11:27🇩🇪38:7c (oui Unknown), ethertype 802.1Q (0x8100), length 102: vlan 10, p 0, ethertype IPv4, 10.5.1.100 > pfSense.localdomain: ICMP echo request, id 13465, seq 3, length 64
      18:18:53.197955 ec:11:27🇩🇪38:7c (oui Unknown) > 00:90:f5:fb:f0:8d (oui Unknown), ethertype 802.1Q (0x8100), length 102: vlan 10, p 0, ethertype IPv4, pfSense.localdomain > 10.5.1.100: ICMP echo reply, id 13465, seq 3, length 64

      I am just not sure what to do since I can't just keep a packet capture running permanently.

      Am I missing something or is this a known issue?

      Thank you,

      Robbert

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

        Are you changing the switch port connected to pfSense to a tagged port for vlan 10?

        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
        • ?
          A Former User
          last edited by

          Yes as you can see in the two lines from the packet capture the firewall sees the packets as coming in tagged, the weird part is that it works when doing a packet capture through the serial console.

          Thanks,

          Robbert

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

            Is the parent interface cpsw1 assigned to any pfSense interfaces? Is that interface enabled?

            If it is not can you try assigning it to an OPTX interface and enabling it? Just set both IPv4 and IPv6 types to None.

            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
            • ?
              A Former User
              last edited by

              I tried with:

              The parent interface with no IP assigned
              The parent interface with an IP setup as the native VLAN (PVID 1) the parent interface worked but no vlan interfaces.
              The parent interface undefined.

              Regards,

              Robbert

              1 Reply Last reply Reply Quote 0
              • P
                phil.davis
                last edited by

                This is likely related to MAC spoofing - read about that and promiscuous mode at https://doc.pfsense.org/index.php/Interface_Settings
                Have you specified the MAC address for either the "real" interface or the VLAN interface?

                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                1 Reply Last reply Reply Quote 0
                • ?
                  A Former User
                  last edited by

                  I will try setting the promiscuous mode permanently through the link you provided.

                  I have however not done any configuration on the MAC address side at all.

                  Thanks,

                  Robbert

                  1 Reply Last reply Reply Quote 0
                  • P
                    phil.davis
                    last edited by

                    It should not be necessary to set promiscuous mode, but it would be interesting to know if that makes it work. Then search for the real reason why it is needed.

                    As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                    If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                      I just tried this and could not duplicate it…

                      Tagged switchport for 1311 to SG-1000 LAN (cpsw1).

                      Client on untagged 1311 port on switch working fine.

                      ![Screen Shot 2017-06-13 at 11.20.21 AM.png](/public/imported_attachments/1/Screen Shot 2017-06-13 at 11.20.21 AM.png)
                      ![Screen Shot 2017-06-13 at 11.20.21 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2017-06-13 at 11.20.21 AM.png_thumb)

                      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
                      • ?
                        A Former User
                        last edited by

                        I set the interface to promiscuous mode and it has been working fine for a few hours now.

                        The configuration that is working with promisc turned on is attached. I am not sure why but as soon as I turn promisc off it stops working.

                        Thanks,

                        Robbert

                        ![Screenshot from 2017-06-13 14-45-02.png](/public/imported_attachments/1/Screenshot from 2017-06-13 14-45-02.png)
                        ![Screenshot from 2017-06-13 14-45-02.png_thumb](/public/imported_attachments/1/Screenshot from 2017-06-13 14-45-02.png_thumb)

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

                          My snapshot might not be current enough to see what you're seeing.

                          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
                          • ?
                            A Former User
                            last edited by

                            I'm on the latest snapshot and even did a full flash with an SD card. If you have a chance let me know if you see the same thing with the latest version.

                            Robbert

                            1 Reply Last reply Reply Quote 0
                            • P
                              phil.davis
                              last edited by

                              @JimP has logged an issue with this https://redmine.pfsense.org/issues/7645 at priority "Very High". So it is recognised as a problem that appears to be a recent regression.

                              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                              1 Reply Last reply Reply Quote 0
                              • ?
                                A Former User
                                last edited by

                                Thanks, I'll follow that bug report, and I can test any fixes if needed.

                                Robbert

                                1 Reply Last reply Reply Quote 0
                                • D
                                  dancwilliams
                                  last edited by

                                  Glad I found this thread.  I am having the same issue.  Promiscuous mode fixed the issue for now.  Thanks for the info!

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

                                    This is fixed on current snapshots. Actually the last few. I have updated the one I have with a VLAN for WAN a couple days in a row without any problems.

                                    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
                                    • S
                                      strigona
                                      last edited by

                                      Hi jimp - thanks for the update!

                                      Would you suggest updating pfSense prior to disabling promiscuous mode on the interface with VLANs or vise-versa?

                                      To confirm, disabling promiscuous mode is:

                                      /sbin/ifconfig cpsw0 -promisc
                                      1 Reply Last reply Reply Quote 0
                                      • jimpJ
                                        jimp Rebel Alliance Developer Netgate
                                        last edited by

                                        Just update, don't touch promisc manually. That will go away when the device reboots anyhow.

                                        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
                                        • S
                                          strigona
                                          last edited by

                                          Got it - thanks again!

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

                                            After upgrading to

                                            2.4.0-RC (arm)
                                            built on Thu Oct 05 21:17:11 CDT 2017
                                            FreeBSD 11.1-RELEASE-p1

                                            I seem to be seeing this problem, previous releases had been fine. Anyone else experiencing issues with the latest build ?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post