Wireshark-dev: Re: [Wireshark-dev] [ACL][firewall] how to

From: Mihai Bucicoiu <mihai.bucicoiu@xxxxxxx>
Date: Tue, 14 Apr 2009 17:20:51 +0300
I was looking for something like iptables, I'll my own kernel module if it's necessary, but I know that netfilter has some user-space interface for this.

Thanx,

   Mihai

On Tue, Apr 14, 2009 at 4:17 PM, Jaap Keuter <jaap.keuter@xxxxxxxxx> wrote:
Hi,

How do you imagine 'apply' from a user application like Wireshark? What kind of interface should it communicate through to the firewall? Firewall is a generic term, there are hundreds of types, which one do you target?

Thanx,
Jaap

Sent from my iPhone

On 14 apr 2009, at 11:46, Mihai Bucicoiu <mihai.bucicoiu@xxxxxxx> wrote:

Hello everyone,

   My name is Mihai and I'm new at wireshark developer list. Am in the last year in a romanian University and I have a bachelor paper to do.

   My paper is about Wireshark, I have 2 months for it. What I would like to do is a wireshark firewall. What I mean by that is , that I would like to create from a wireshark filter, one entry in an ACL. Give the user the posibility to create more that one ACL, and apply from Wireshark the rules that you have created.

   Because I only have 2 months for it, I would only go to the port, ip and mac addresses, not to the application and conversation watching.

   This all being told, I would really appreciate your help for this task.

   My first question is : are those things already in Wireshark? I saw that there is already an ACL filter tab that creates an rule, which can be applied by the user later, but is there any way that Wireshark applies this ?

Best regards,

   Mihai 
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe