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

    How to trunk the OPT interface on SG-1100.

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    10 Posts 3 Posters 1.7k Views 5 Watching
    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.
    • D Offline
      delinobersmhield
      last edited by

      I am new with PFsense, i just got my SG-1100 last week.
      I want to use SG-1100 LAN and OPT physical interfaces independently:
      On the physical LAN interface, i will use a single network: 192.168.88.0 /24 (this one is OK)
      On the physical OPT interface, i want to use 2 networks: vlan100 et vlan200 (192.168.100.0 and 192.168.200.0) /24

      I believe i'm missing a configuration in the: interfaces/switch/VLAN since I did not understand how does the "Members" feature works in PFsense...
      lab_berm.jpg

      1 Reply Last reply Reply Quote 0
      • S Offline
        SteveITS Rebel Alliance
        last edited by

        Did you create the VLANs and assign them to new interfaces? https://docs.netgate.com/pfsense/en/latest/book/vlan/pfsense-vlan-configuration.html (they are treated as separate interfaces so have their own firewall rules)

        Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
        Upvote 👍 helpful posts!

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

          This is no different than any other trunk port to any other switch except that the switch is built-in to the SG-1100.

          Make the VLANs on mvneta0

          Assign them to pfSense interfaces. That will cause that traffic to be tagged to the internal switch on port 0 (The uplink interface from the switch chip to pfSense).

          Then, on the internal switch, create the VLANs. Make them tagged on ports 0 (the uplink) and 1 (The OPT1 port).

          Set the switch to tag the same VLANs and cross-connect it to the OPT1 port.

          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)

          D 1 Reply Last reply Reply Quote 0
          • D Offline
            delinobersmhield @SteveITS
            last edited by

            @teamits I adjusted the firewall rules for each VLAN + I did add DHCP services for each VLAN. I think I did correctly the VLAN \ interface assignments but not sure of the procedure. I have a hard time understanding the Member meaning...
            I did not yet go to console mode, just stayed on the GUI, is it easier from the console?

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

              No it's not easier from the console. If you do it from the console the changes won't stick anyway.

              In your case the VLAN membership needs to be 0 tagged and 1 tagged.

              This is just like adding member ports to any VLAN on any switch in the world. It is just 802.1q.

              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)

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                delinobersmhield @Derelict
                last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • D Offline
                  delinobersmhield @Derelict
                  last edited by

                  @Derelict Thanks for your reply. Does that make sense:
                  Capture d’écran 2020-04-27 à 20.11.26.png

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

                    Looks fine. Is the switch connected to OPT set to tag VLANs 100 and 200?

                    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)

                    D 1 Reply Last reply Reply Quote 0
                    • D Offline
                      delinobersmhield @Derelict
                      last edited by

                      @Derelict It all works now! thank you, your "Make them tagged on ports 0 (the uplink) and 1 (The OPT1 port)." line made that possible.

                      What is this 4090,4091 and 4092 VLANs? Is their any packet tagged with those ? Can we remove it?

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

                        If you do not need 4092 on switchport 1 (OPT) it can be removed. 4090 and 4091 are the untagged VLANs for the WAN and LAN ports. You probably want to leave them alone.

                        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
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.