tag:blogger.com,1999:blog-12783726.post2350578884764221638..comments2024-02-19T16:39:32.319+08:00Comments on When {Puffy} Meets ^RedDevil^: BPF - Birectional FilterC.S.Leehttp://www.blogger.com/profile/10778262436985693992noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-12783726.post-34887436438452904562007-09-16T22:22:00.000+08:002007-09-16T22:22:00.000+08:00anonymous,np ;]anonymous,<BR/><BR/>np ;]C.S.Leehttps://www.blogger.com/profile/10778262436985693992noreply@blogger.comtag:blogger.com,1999:blog-12783726.post-19487105155490224312007-09-16T20:33:00.000+08:002007-09-16T20:33:00.000+08:00Okay, I understand now. Thanks for setting me str...Okay, I understand now. Thanks for setting me straight. :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-12783726.post-40438430490341695632007-09-16T11:27:00.000+08:002007-09-16T11:27:00.000+08:00anonymous,Yes, you can just do that but you will c...anonymous,<BR/><BR/>Yes, you can just do that but you will catch all the traffics where 192.168.0.55 connects to destination port 80 too instead of you just want the conversation where the traffics flowing to and from 192.168.0.55 port 80(web server condition). <BR/><BR/>Simply say that if you use that filter, you will filter the traffics when 192.168.0.55 acts as either web client or web server which is not what I want here.<BR/><BR/>Cheers ;]C.S.Leehttps://www.blogger.com/profile/10778262436985693992noreply@blogger.comtag:blogger.com,1999:blog-12783726.post-81131527141587990862007-09-15T23:50:00.000+08:002007-09-15T23:50:00.000+08:00Could you just do:host 192.168.0.55 and port 80I t...Could you just do:<BR/><BR/><B>host 192.168.0.55 and port 80</B><BR/><BR/>I think that would include both source and destination port 80 traffic involving 192.168.0.55, which would do the same thing, but then again I could be wrong...Anonymousnoreply@blogger.com