Re: RFC: new ipfw options

2010-01-11 Thread Luigi Rizzo
On Sun, Jan 10, 2010 at 11:55:54PM -0800, Julian Elischer wrote: Maxim Ignatenko wrote: 2009/12/9 Luigi Rizzo ri...@iet.unipi.it: 3. a hash version of 'table's Right now ipfw tables are implented as routing tables, which is great if you have to lookup a longest matching prefix, but a

Re: RFC: new ipfw options

2010-01-11 Thread Julian Elischer
Maxim Ignatenko wrote: 2009/12/9 Luigi Rizzo ri...@iet.unipi.it: 3. a hash version of 'table's Right now ipfw tables are implented as routing tables, which is great if you have to lookup a longest matching prefix, but a bit overkill if you care only for ports or jail ids, and totally

Re: RFC: new ipfw options

2010-01-10 Thread Maxim Ignatenko
2009/12/9 Luigi Rizzo ri...@iet.unipi.it: 3. a hash version of 'table's   Right now ipfw tables are implented as routing tables, which is   great if you have to lookup a longest matching prefix, but a   bit overkill if you care only for ports or jail ids, and   totally uninteresting if you

RFC: new ipfw options

2009-12-09 Thread Luigi Rizzo
Hi, I would like to discuss some new features that I am going to add to ipfw. 1. A new option lookup search-key T[,V] where search-key ::= {src-ip|dst-ip|src-port|dst-port|proto|jail|...} This extends the existing '{dst-ip|src-ip} table(T[,V])' options, and allows a lookup of other