Здравствуйте, Lowell.

Вы писали 16 апреля 2009 г., 15:22:31:

LG> KES <kes-...@yandex.ru> writes:

>>      The tablearg feature provides the ability to use a value, looked up in
>>      the table, as the argument for a rule action, action parameter or rule
>>      option.  This can significantly reduce number of rules in some 
>> configura-
>>      tions.  If two tables are used in a rule, the result of the second (des-
>>      tination) is used.  The tablearg argument can be used with the following
>>      actions: nat, pipe, queue, divert, tee, netgraph, ngtee, fwd, skipto
>>      action parameters: tag, untag, rule options: limit, tagged.
>> Why tablearg cannot be used with setfib?

LG> Because tables are a feature of IPFW, and the FIB isn't.

setfib is also feature of ipfw. see man:

     setfib fibnum
             The packet is tagged so as to use the FIB (routing table) fibnum
             in any subsequent forwarding decisions. Initially this is limited
             to the values  0 through 15. See setfib(8).  Processing continues
             at the next rule.

There is no any difficulties to use 'tablearg' as 'fibnum'

ipfw add 3 setfib 2 all from to any in recv <IFACE>
ipfw add 3 setfib tablearg all from table(<X>) to any in recv <IFACE>

but now this is not mistake to write 'setfib tablearg'. IPFW just replace 
tablearg in rule with 0
It seems like a bug. because of it MUST work in proper way or DO NOT
work at all. IMHO

С уважением,
 KES                          mailto:kes-...@yandex.ru

freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to