Definition of Firewall Tools
Tools used either to prevent unauthorized users from gaining access to a computer network or tools used to gain access to a computer network.
|
|
Firewall Tools
Easy Firewall Generator for IPTables
This program generates an iptables firewall script for use with the 2.4 or later linux kernel. It is intended for use on a single system connected to the Internet or a gateway system for a private, internal network. It provides a range of options, but is not intended to cover every possible situation.
Read the Article
|
Vuurmuur Firewall
The program is basicly split into three pieces. One piece (the middle-end) converts humanly-readable rules, hosts, groups, networks, zones, interfaces and services into a iptables ruleset (or optional into a bash-script). The second part is a little daemon that converts the netfiler logs to easy readable logs, that reflect all the predefined objects described above. The third part is a Ncurses-based Gui (the front-end) in which one can manage the firewall. Most important here is the real-time feedback. Logs can be viewed in real-time, using colours for easy interpretation. Also, the current connections can be viewed in real-time. Filtering possibilities make it easy to monitor specific hosts or services.
Read the Article
|
Filterrules
Filterrules is a program which allows you to determine the rules of a firewall in a very reliable way. It is made up of two parts: a "master", in charge of forging several IP packets, and a "slave", which listens on the other side of the firewall, and which tells to the master which packets passed through. At the end of the test, the firewall rules are displayed in the ipfw format.
Read the Article
|
IPCop
IPCop firewall is a nice tool to protect your home computer and large corporate networks from intrusions and attacks.
IPCop implements existing technology, secure programming practices and outstanding new concepts to make it "the" Linux Distribution for protecting single home computers, to large corporate networks.
Read the Article
|
Firewalk
Firewalk is an active reconnaissance network security tool that attempts to determine what layer 4 protocols a given IP forwarding device will pass. Firewalk works by sending out TCP or UDP packets with a TTL one greater than the targeted gateway. If the gateway allows the traffic, it will forward the packets to the next hop where they will expire and elicit an ICMP_TIME_EXCEEDED message. If the gateway hostdoes not allow the traffic, it will likely drop the packets on the floor and we will see no response.
Read the Article
|
Firewall Builder
Firewall Builder is multi-platform firewall configuration and management tool. It consists of a GUI and set of policy compilers for various firewall platforms.
Read the Article
|
Nemesis
Nemesis is a command-line network packet injection utility for UNIX-like and Windows systems. You might think of it as an EZ-bake packet oven or a manually controlled IP stack. With Nemesis, it is possible to generate and transmit packets from the command line or from within a shell script. Nemesis is developed and maintained by Jeff Nathan <jeff at snort dot org>.
Read the Article
|
arp-sk
Designed to manipulate ARP tables of all kinds of equipment. This can be easily performed through the sending of the appropriate packet(s). Could be used for ARPspoofing, ARPoisoning ... sniffing.
Read the Article
|
Packit
Packit (Packet toolkit) is a network auditing tool. Its value is derived from its ability to customize, inject, monitor, and manipulate IP traffic. By allowing you to define (spoof) nearly all TCP, UDP, ICMP, IP, ARP, RARP, and Ethernet header options, Packit can be useful in testing firewalls, intrusion detection/prevention systems, port scanning, simulating network traffic, and general TCP/IP auditing. Packit is also an excellent tool for learning TCP/IP.
Read the Article
|
Firewall Tester
The Firewall Tester is a tool designed for testing firewalls filtering policies and Intrusion Detection System (IDS) capabilities. The tool consists of two perl scripts, a packet injector (ftest) and the listening sniffer (ftestd). The first script injects custom packets, defined in ftest.conf, with a signature in the data part while the sniffer listens for such marked packets. The scripts both write a log file which is in the same form for both scripts.
Read the Article
|
|
|
Page: 1 2
Members currently browsing this category:
|
|
