Free who designed the brooklyn bridge software for linux

Hogwash Light BR is an Intrusion Prevention System that can filter packets directly in the layer 2 of the OSI model (so the machine doesnt need even an IP address).
Detection of malicious/anomalous traffic is done by rules based in signatures, and the user can add more rules. It is an efficient and versatile IPS, and it can even be used as bridge to honeypots and honeynets.
Since it doesnt make use of the operating systems TCP/IP stack, it can be "invisible" to network access and attackers.
Enhancements:
- New rules were added.

IP and Ethernet testing Tool is also known as "IET" and its an ethernet bridge addon for testing of network appliances and applications.
Initialy IskraTel extended and customized the NistNet tool.
However NistNet functions on IP layer and requires that tested equipment be configured to use different subnets and gateways.
Nistnet main purpose was internet emulation while IET main purpose is testing of communication equipment.
Main features:
- no need to reconfigure equipment, just insert a PC with two NICs "on the cable"
- works on the ethernet level with a bridge
- network error conditions:
- packet loss
- delay
- in transmission errors (IP, UDP layer)
- bandwidth restraints
- kernel driver for low-CPU overhead packet processing
- control application for configuring driver engine
- GUI
- CLI
- saving configuration to a text file
Enhancements:
- Fixed support for matching ethernet packets based on the protocol
- Added additional matches for ICMP, TCP and UDP protocols (ICMP Type, TCP/UDP src port and dst port)
- Added target for corruption of IP and UDP packets with optional checksum update.
- Numerous small bug-fixes and enhancements
- IET has entered feature-freez and until version 1.0.0 is released there will be only bugfixes

UDP-Bridge is a transparent proxy for UDP traffic, designed for use with Linux 2.2.x kernels. It provides two-way proxying of UDP packets, to avoid the port number mangling that occurs with Linux IP masquerading. This mangle rule causes problems for some online games.

This program was actually developed to solve a problem with handling Playstation 2 network traffic through a Linux firewall. According to testimonials, most games worked fine with this kind of configuration, but the one that I had tried (ATV Offroad Fury 2) would not work. The problem was apparently the UDP port mangling done by Linux IP masquerading, hence the need for this proxy.

To build the proxy, simply run make from within the source directory:

make

To install the proxy, run the following command as root:

make install

This will install the proxy executable (udpbridge) into /usr/local/sbin, and the man page into /usr/local/man/man8.

The last step is to create and install a configuration file. The included example.conf file is a good template for this. The default location for the configuration file is /etc/udpbridge.conf.

Linux Bridge Utilities is a bridge is a way to connect two Ethernet segments together in a protocol independent way. Packets are forwarded based on Ethernet address, rather than IP address (like a router). Since forwarding is done at Layer 2, all protocols can go transparently through a bridge.

The Linux bridge code implements a subset of the ANSI/IEEE 802.1d standard. [1]. The original Linux bridging was first done in Linux 2.2, then rewritten by Lennert Buytenhek. The code for bridging has been integrated into 2.4 and 2.6 kernel series.

Manual Configuration

Network cards

Before you start make sure both network cards are set up and working properly. Dont set the IP address, and dont let the startup scripts run DHCP on the ethernet interfaces either. The IP address needs to be set after the bridge has been configured.

The command ifconfig should show both network cards, and they should have be DOWN.

Module loading

In most cases, the bridge code is built as a module. If the module is configured and installed correctly, it will get automatically loaded on the first brctl command.
If your bridge-utilities have been correctly built and your kernel and bridge-module are OK, then issuing a brctl should show a small command synopsis.

BridgeQuery is a Perl extension for retrieving bridge tables.

SYNOPSIS

use SNMP::BridgeQuery;
use SNMP::BridgeQuery qw(querymacs queryports queryat);

$fdb = queryfdb(host => $address,
comm => $community);
unless (exists $fdb->{error}) {
($fdb->{$mac} = "n/a") unless (exists $fdb->{$mac});
print "This MAC address was found on port: ".$fdb->{$mac}."n";
}

BridgeQuery polls a device which responds to SNMP Bridge Table queries and generates a hash reference with each polled MAC address as the key and the associated port as the value. The specific MIBs that are polled are described in RFC1493.

SNMP::BridgeQuery requires Net::SNMP in order to function. (Checked for during perl Makefile.PL)

Devices can be switches, bridges, or most anything that responds as a OSI Layer 2 component. Layer 3 devices do not generally respond and will cause an error. If an error is generated, it will return a hash reference with a single element (error) which can be tested for.

Two other functions (querymacs & queryports) can be explicitly exported. They work the same way as queryfdb, but they return MAC addresses or ports (respectively) with the SNMP MIB as the hash key.

A newly added function (queryat) can be used on layer 3 switches to poll the Address Translation Tables. This is similar to the data returned by the queryfdb function, but it returns the IP address of the device and the associated interface (separated by a pipe |) with the MAC address as the key. On a layer 3 switch, this interface probably does not correspond to a physical port, but more likely refers to a vlan ID. Using this function on a layer 2 device will generate a trapped error.

Clearlooks-BlackMod are three themes designed to perfectly fits Clearlooks themes with Black borders.

See for example the Light and Medium versions how look good with Aerials! Absolutely wonderful.