AW: Issue using altq_priq unter FreeBSD 11.1 - help needed

[Ian FREISLICH]

On 10/16/17 12:32, Rolf Dahmen wrote:
> Thx, Doug
>
> Understood. We need to define some "pass" commands to map the traffic to dedicated queues. We´ve studied the "pf manual" and are not quite sure how the pass actions should look like.
>
> We have already configured the below listed tables in "ipfw.rules".
>
> pass in quick on igb0 from t_allowed to queue allowed

pass in quick on igb0 from t_allowed to any queue allowed

> pass in quick on igb0 from t_specialip to queue specialip
> pass in quick on igb0 from t_terminals to queue terminals
> pass in quick on igb0 from t_freeunlimited to queue freeunlimited
> pass in quick on igb0 from t_free to queue free
>
> Any idea what we have missed?
>
> -----Ursprüngliche Nachricht-----
> Von: Doug Hardie [mailto:bc979 at lafn.org]
> Gesendet: Montag, 16. Oktober 2017 17:22
> An: Rolf Dahmen <R.Dahmen at m3connect.de>
> Cc: freebsd-pf at freebsd.org
> Betreff: Re: Issue using altq_priq unter FreeBSD 11.1 - help needed
>
> You are missing the filtering commands to tell pf which traffic goes in which queue.  Here is an example using bandwidth queues that I used to use.  They are all commented out now since I don't need them anymore, but kept them around just in case.  This configuration restricted the bandwidth for web and mail.  If I remember correctly, I built this from "The Book of PF" which I believe is available on the web now.
>
>
> ############ Queueing:  rule-based bandwidth control.
> #altq on $ext_if cbq bandwidth 100% queue {normal, web, mail}
> #       queue normal bandwidth 99% qlimit 100 cbq(default)
> #       queue web bandwidth 100Kb qlimit 100 cbq
> #       queue mail bandwidth 250Kb qlimit 100 cbq
>
> ############ Filtering:  Last Rule Matches #pass log proto tcp from any to any port 80 queue web #pass log proto tcp from any to any port 25 queue mail
>
> -- Doug
>
>> On 16 October 2017, at 05:55, Rolf Dahmen <R.Dahmen at m3connect.de> wrote:
>>
>> Hi all,
>>
>> I´m Rolf Dahmen working as CTO for a german Wifi Service Provider. We do have a certain issue that we are not able to configure QoS to prioritize queues on FreeBSD using pf with altq. My SysOps engineers are stuck in getting it done, so I`m looking forward to get a resolution or any consults onboarded.
>>
>> We have successfully recompiled the kernel to use pf with altq.
>>
>> We have configured 5 new queues "allowed, specialip, terminals, freeunlimited, free" to pass the incoming traffic to prioritize the flow. The issue is that always the defined default queue is used but never the user queues.
>>
>> I do think that our pf.conf is not complete:
>>
>>        (pf.conf)
>> altq on igb0 priq queue {allowed, specialip, terminals, freeunlimited,
>> free} queue free priority 5 priq(red) queue freeunlimited priority 4
>> priq(red) queue terminals priority 3 priq(red) queue specialip
>> priority 2 priq(red) queue allowed priority 1 priq(default red)
>>
>>
>> Gruß,
>>
>> Rolf Dahmen
>> Chief Technology Officer (CTO)
>>
>> [cid:image001.jpg at 01D168B7.D9C957D0]
>>
>> T:             +49 (0)241 980 986 68
>> M:            +49 (0)151 617 196 23
>> Fax:         +49 (0)241 980 986 90
>>
>> Web:        www.m3connect.de<http://www.m3connect.de/>
>> E-Mail:     r.dahmen at m3connect.de<mailto:r.dahmen at m3connect.de>
>>
>> m3connect GmbH | Friedlandstr.18 | 52064 Aachen | DE/Germany |
>> Amtsgericht Aachen | HRB 8773 | USt.- ID: DE219 664 658 |
>> Geschäftsführer/CEO: Emilio Dragas, Markus Schindler
>>
>>
>>
>> _______________________________________________
>> freebsd-pf at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-pf
>> To unsubscribe, send any mail to "freebsd-pf-unsubscribe at freebsd.org"
> _______________________________________________
> freebsd-pf at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-pf
> To unsubscribe, send any mail to "freebsd-pf-unsubscribe at freebsd.org"


-- 
 

Cape Augusta Digital Properties, LLC a Cape Augusta Company

*Breach of confidentiality & accidental breach of confidentiality *

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.