Hello, Developers! Sorry, my english is bad. :( Patch to IPFW2 for adding restrictions of the traffic with use IPFW bytes counters. It include two parts: * First part is ipfw_bound.patch, this part add ipfw rule options "bound VALUE" and "check-bound NUM". Example: # ipfw add 100 allow ip from any to any bound 10K # ipfw add 200 deny ip from any to any While bytes counter of rule 100 below 10 KBytes, it work. Example: # ipfw add 100 allow ip from A.B.C.D to any out xmit internet check-bound 200 # ipfw add 200 allow ip from any to A.B.C.D in recv internet bound 100M # ipfw add 300 deny ip from any to any via internet While bytes counter of rule 200 below 100 MBytes, rules 100 and 200 work. NOTE: Check-bound option search rule NUM like "ipfw skipto", but if rule NUM not contain bound option, then match fail. Second part is bound_change.patch, this part add control call to ipfw for boundary value change without bytes counter reset. Syntax: # ipfw bound NUM [set N] change VALUE. Files: For CURRENT: http://butcher.heavennet.ru/ipfw_bound/CURRENT/ipfw_bound.patch http://butcher.heavennet.ru/ipfw_bound/CURRENT/bound_change.patch For RELENG_5: http://butcher.heavennet.ru/ipfw_bound/RELENG_5/ipfw_bound.patch http://butcher.heavennet.ru/ipfw_bound/RELENG_5/bound_change.patch For RELENG_5_4: http://butcher.heavennet.ru/ipfw_bound/RELENG_5_4/ipfw_bound.patch http://butcher.heavennet.ru/ipfw_bound/RELENG_5_4/bound_change.patch -- WBR, Andrey V. ElsukovReceived on Mon May 23 2005 - 08:29:24 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:35 UTC