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

    How do i give SIP Priority based on IPs on LAN

    Scheduled Pinned Locked Moved Traffic Shaping
    3 Posts 2 Posters 1.5k 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.
    • M
      mystycs
      last edited by

      Lets say i have a subnet on my LAN 192.168.75.0

      And i have 6 IPS on that subnet.

      192.168.75.1
      192.168.75.2
      192.168.75.3
      192.168.75.4
      192.168.75.5
      192.168.75.6

      I want to give them all seperate data bandwidth caps and VOIP priority of lets say 30% to sip.website.com

      How would i go about setting up something like this on pfsense? I am really confused by these traffic shaping rules.

      So for example the ips below would have different data caps (128up,128down, 256up ect… of my choosing). But all have for example 30% SIP priority or of my choosing how can i do that? And they should all have priority 1 top priority

      192.168.75.1 (128up,128down, 30% sip priority)
      192.168.75.2 (256up,256down, 15% sip priority)
      192.168.75.3 (256up,256down, 15% sip priority)
      192.168.75.4 (256up,256down, 15% sip priority)
      192.168.75.5 (128up,128down, 30% sip priority)
      192.168.75.6 (128up,128down, 30% sip priority)

      1 Reply Last reply Reply Quote 0
      • M
        mystycs
        last edited by

        Im afraid to use the traffic shaper because i dont want it to be global i want these to be on an IP level on my LAN.

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

          Without shaping the entire traffic from everyone, you cannot shape a subset of the LAN. Shaping works by dropping / queueing packets. This can't work unless all traffic is classified. Once you have basic rules in place, you can create further rules for specific IP addresses.

          Either way you need to completely understand HFSC and how the queues work or you'll fail to get it working.

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