Date: Thu, 16 Sep 2004 04:05:29 -0000 From: "Baroo" <baroo@poczta.onet.pl> To: <pf4freebsd@freelists.org> Subject: [pf4freebsd] Some changes in ALTQ implementation Message-ID: <000501c4531c$b2238b00$1501000a@dom>
next in thread | raw e-mail | index | archive | help
Hi I have some idea for implementation of pf in freebsd. I know that in the native implementation of pf queues filters are making with pass rules. (eg. pass out on fxp0 from any to any port 22 queue ssh ). I think that more resonable is to make an independent filters but in pf.conf file. This can be useful in many configurations, because sometimes administrators want to make an QoS configuration independent from packet filtering. Let say we have an internet gateway with two interfaces. For filtering we could use only one rule pass out on $EXT_IF from $NAT_ALLOW to any keep state an for qos something like this: traffic out on $EXT_IF proto tcp from $NAT_ALLOW to any port 22 queue prio traffic out on $EXT_IF proto udp from $NAT_ALLOW to any port 53 queue prio traffic out on $EXT_IF proto icmp from $NAT_ALLOW to any queue prio traffic out on $EXT_IF from 10.0.1.10 to any queue (user1, prio) traffic out on $EXT_IF from 10.0.1.11 to any queue (user2, prio) traffic out on $EXT_IF from 10.0.1.12 to any queue (user3, prio) traffic out on $EXT_IF from 10.0.1.13 to any queue (user4, prio) ... What are you think about it? And the second thing. Are there any plans to make an ingress shaping (to make a viritual pipe for queueing). It could be use to queueing a router traffic (eg. if we have a ftp server on the same machine as router) or shaping bandwidth between multiplie interfaces. Thanks for your job around this project.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000501c4531c$b2238b00$1501000a>