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

    SG-3100: all communication dropped when enabling 802.1q VLAN mode

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    2 Posts 2 Posters 1.2k 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.
    • B
      border
      last edited by

      Hi,

      Trying to implement some suggestions from the forum for configuring a VLAN on port #2 of the SG-3100 device, I understood that first I have to "Enable 802.1q VLAN mode" in order to change port settings (indeed: I cannot change any port settings under Interfaces/Switch/Ports). However, as soon as I enabled this option (with the default settings that are set in my current version 2.4.3-RELEASE) all communication is dropped. Using the console mode I could restore the latest backup and get back into the device.

      My intention is to have (besides the current LAN) a VLAN.
      I have been able to configure pfSense in the past using a managed switch but now I would like to use the extra LAN ports on the device for this.

      Unfortunately there is no info in the SG-3100 manual for these settings…

      Any step-by-step advice?

      regards.

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

        First off, configuring a switch you are connected to is going to be painful.

        Configure OPT1 with another network numbering scheme, firewall rule, and possibly DHCP server and connect to that.

        Then you can configure the switch without worrying about getting locked out.

        Then see this thread:

        https://forum.pfsense.org/index.php?topic=142311.msg776145#msg776145

        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.