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

    Traffic limiter on multiple VLANS

    Scheduled Pinned Locked Moved Traffic Shaping
    4 Posts 3 Posters 2.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.
    • K
      kaioh
      last edited by

      Hi, we have multiple VLANs, one for each virtual server. We have one pfSense interface per VLAN.
      We need to give 5Mbps up / down for each VLAN.

      I created one in/out pipe and set it for each VLAN firewall rule (internet rule). Is this the correct configuration? Will I get 5Mbps for each VLAN or I'm going to get 5Mbps for ALL the VLANs together?

      Thanks for your support.

      .: Kaioh :.

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

        The way I would recommend to set this up is to make pipes for each VLAN interface and set them that way.  The pipe is shared if you use the same queues for all of them.  I have done a similar set up, with dual WAN interfaces going to the PFsense and being used on two seperate VLANs.  It works properly for each limiter.

        1 Reply Last reply Reply Quote 0
        • K
          kaioh
          last edited by

          I'm configuring two limiters for each vlan. It's a long task since we have 103 vlans :(

          .: Kaioh :.

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

            If all the VLANs have the same subnet mask you should get a separate pipe for each, say, /24 mask in the limiter config.

            If putting them on LAN mask on source addresses on the in limiter (user uploads) and dest addresses on the out limiter (user downloads).

            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.