精彩内容 If you compare rwfilter's option-based filtering against tcpdurnp's BPF filtering,it's immediately obvious that rwfilter's approach is much more primitive.This was an intentional decision: rwfilter is focused on processing large volumes as quickly as possible,and the overhead involved in processing some kind of parseable language was deemed too expensive. The place where this usually trips people up is the lack ofobvious not and o r operators.For example,ifyou want to filter out all web sessions,you may try to filter traffic where one port is 80,and the other is ephemeral.The initial attempt might be: rwfilter--sport=80,1024-65535--dport=80,1024-65535--pass=stdout The problem is that this will also pass any flows where the source and destination port are both 80,and flows where the source and destination port are both ephemeral.To deal with problems like this,rwfilte r has a collection ofhelper functions,which combined with the--fail option and multiple fllters should be able to address any of these problems. In the case of ports,the--aport option refers to either the source or the destination port.Using--apo rt and two filters,you can identify the appropriate sessions as follows: rwfilter--aport=80--pass=stdout I rwfilter--input-pipe=stdin --aport=1024-65535--pass=stdout The first filter identiFies anything engaged in port 80 traffic,and the second takes thatset and identifies anything that also used an ephemeral port.
以下为对购买帮助不大的评价