Multiple IP's in shaper rule

[bgkskyguy]

So, I have an interface configured at 192.168.16.1/24... What I want to do is have a rule for a group of static addresses to go to one pipe in traffic shaper.  IE - addresses 192.168.16.50 - 192.168.16.100 go to my desired pipe.   Is it possible to enter a range of addresses in one rule as opposed to creating a rule for each address in that range?  If so how? 
Thanks in advance

[Ciprian]

Hello!

This is ”by the book”, if you follow the documentation you will get the exact answer for your situation. Please, be aware that I am NOT trying to be ”superior” with my lines, I only try to avoid repeating the documentation here, and again.

If there is something else you're looking for, and you can't achieve, then come back with required details.

Thank you!

[franco]

Hmm, not pointing to the documentation seems strange, there is duplication in pointing to the line where this is written down.

We support only (multiple) subnets or IPs at this point, the range is missing, I am unsure if ipfw supports it (but it should).

For now, all the IPs would have to be listed in the rule.

Best is to ask for the range feature via GitHub:

https://github.com/opnsense/core/issues


Thanks,
Franco

[bgkskyguy]

Thank you Franco..  I did search the docs for this and didn't find anything certain so I asked.  Thank you for your reply.  Is it possible to list multiple ip's in one rule then?  if so what is the proper syntax..  could I have one rule that just has a large list..  ie   192.168.16.50 ; 192.168.16.51 ; 192.168.16.52 ;  ect, ect.  Thank you in advance for your time and patience as I learn this thing.  I do try to read the documentation before I ask questions. 

[Ciprian]

Maybe sub-netting/ summarizing your range would be a temporary solution?!?! 

So, if you have a range of IPs, lets say 16.50 -> 16.60 then you might try a setup for 192.168.16.48/28. Of course, you should manage this very carefully, it might impact your other settings, like interface rules and etc., but at least, in what concerns your post, it might be a solution, if you plan and manage it right.

I hope it helps.

[franco]

The list is comma-separated, e.g. 23.43.43.34/24,10.0.0.1