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

    LAGG with VLAN configuration between Pfsense and Edgeswitch Lite

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    2 Posts 1 Posters 272 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.
    • A
      adelaide_guy
      last edited by

      Hi, Everyone.

      I am new with Pfsense and willing to learn. I am currently trying to setup a pfsense box connecting to a Edgeswitch Lite with LAGG and VLAN configured. But the two device seems do not sync to each (apologies if term I am using is not correct). Machine connected behind the switch cannot get DHCP or if setup a static address, it cannot reach the pfsense. Below is the configuration I did on both Pfsense and EdgeSwitch Lite:

      Here is my configuration in Pfsense

      • Under Interfaces > LAGGs: created LAGG0 and the members are igb2 and igb3
      • Under Interfaces > VLANs: created VLAN 10 to 50 binding to Interface lagg0
      • Under Interfaces > Interface Assignments: Added VLAN 10 to 50
      • Under Firewall > Rules > NameofeachVLANS: added the rule action: passsource:nameofvlan net port:any Destination:any
      • Under System > Advanced > System Tunables: added net.link.lagg.0.lacp.lacp_strict_mode with a value of 0

      Here are my configuration in EdgeSwitch Lite
      - Under Swtiching > Port Channel > Summary: made sure 0/23 and 0/24 is member of Interface 3/1
      - Under Swtiching > Port Channel > Summary: configured 3/1 to have Static Mode to disable
      - Under VLAN > Port Configurationy Interface 0/23, 0/24 and 3/1 (LAGG) are configured as Tagged on VLAN ID 10,20,30,40 and 50

      Please let me know what I did wrong or if you need more information I am willing to provide more information. Thank you in advance for the help.

      1 Reply Last reply Reply Quote 0
      • A
        adelaide_guy
        last edited by adelaide_guy

        I think setting the interface 3/1 to Trunk under Switching > VLAN > Switch Port Summary may have resolved the issue. It allowed my DHCP from the firewall to traverse to the VLAN. I will further test this when I get more time.

        This may have been a switch config issue and not the firewall. Apologies for posting this issue in the netgate forum.

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