Free bridge 1.0 software for linux

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.

aBridge project is a multiplayer online cross-platform bridge game.
It allows you to play bridge online with other real people.
It is currently available for UNIX (including linux), Microsoft Windows and MacOS X.
On all platforms, aBridge supports speech synthesis, allowing you to choose to listen to the bids and chat conversation rather than simply gazing at the screen waiting for someone to play.
aBridge also has some rudimentary bots, for when other players arent online, but their AI is pretty pathetic, and they are in need of a complete rewrite.
Enhancements:
- Complete rewrite of card-displaying code. Cards are now scalable.
- Remember size of game window.
- Use flite instead of festival on sid, since speech-tools is broken on sid at the moment.

PyBridge is a free online bridge game.
PyBridge is software which lets you play the card game of (contract) bridge, with human players, over the Internet or a local network.
Main features:
- Complete bridge game logic: support for bidding, trick playing and duplicate scoring.
- A PyGTK graphical front-end - see the screenshots!
- A standalone server, capable of managing an arbitary number of tables and games.

SIB (Simple IPX Bridge) is able to tunnel IPX and IP frames received by your Ethernet device via UDP over the Internet. It is able to put the interface it listens on to promiscous mode, so all frames (not only broadcasts, and frames for the tunneling server) can be received.
Actually every 802.3 frame can be tunneled, but SIB only tunnels IPX frames per default (this can be changed via command line). SIB also filters SMB over IPX, to reduce network traffic (this can be disabled too).
Additionally SIB takes care which frames belong to local MAC addresses and sends only broadcasts and frame to non-local MACs to the remote host.
A non-plus-ultra is, that SIB can compress every frame it tunnels via LZO, but you must have LZO library installed.
You may ask yourself: "Why should I need this?" Well, there are lot of answers, but the main reason is: FOR GAMES. Even with KALI for Windows ($14.99) and KALI cracked 1.2 ($0 - but bugs bugs bugs) there is no real WHOLE NETWORK to WHOLE NETWORK connection program which can tunnel IPX, filter SMB, compress it, and works with 2.4.0. And EVERY new game (for Windows) uses IPX for "network" (or should I say Internet ;-) games. (RA2, Q3, HL...)
Enhancements:
- fix for "divide by zero" bug on alpha
- fixed hostname resolver
- added option to set local UDP port
- added option to bind to an specific local IP
- MAC lists flushed on SIGHUP

VETH is a daemon that creates a virtual ethernet card in Linux. This is done via the Universal TUN/ TAP Driver. It is useful to request more than one IP address via DHCP with a virtual ethernet card attached to an existing NIC.

Linux has an implementation that does the work, but partially. Sometimes, this emulation doesnt work as expected. Because of this, I wrote VETH, to be helpful in this situations.

For example, if you want to have more than one IP address obtained via DHCP probably you know thats impossible. With VETH you can attach a virtual ethernet into an existent NIC card, and the run dhclient in it to obtain a new IP.

Perhaps you are saying "hey, man, dont mess with me, I can do that with aliasing. With an ifconfig eth0:1 I have a new ethernet". OK, perhaps, perhaps...

It isnt 100% true. Look at this scenario:

You have a DSL modem working as a bridge. You have a firewall with exactly 2 NICs, no more. One of these NICs is crossover-connected to your modem, and another is in your internal subnet.

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.

tinc is a Virtual Private Network (VPN) daemon that uses tunnelling and encryption to create a secure private network between hosts on the Internet.
tinc is Free Software and licensed under the GNU General Public License.
Because the VPN appears to the IP level network code as a normal network device, there is no need to adapt any existing software. This allows VPN sites to share information with each other over the Internet without showing any information to others.
Main features:
- Encryption, authentication and compression
- All traffic is optionally compressed using zlib or LZO, and OpenSSL is used to encrypt the traffic and protect it from alteration with message authentication codes and sequence numbers.
- Automatic full mesh routing
- Regardless of how you set up the tinc daemons to connect to each other, VPN traffic is always (if possible) sent directly to the destination, without going through intermediate hops.
- Easily expand your VPN
- When you want to add nodes to your VPN, all you have to do is add an extra configuration file, there is no need to start new daemons or create and configure new devices or network interfaces.
- Ability to bridge ethernet segments
- You can link multiple ethernet segments together to work like a single segment, allowing you to run applications and games that normally only work on a LAN over the Internet.
- Runs on many operating systems and supports IPv6
- Currently Linux, FreeBSD, OpenBSD, NetBSD, MacOS/X, Solaris, Windows 2000 and XP platforms are supported. See our section about supported platforms for more information about the state of the ports. tinc has also full support for IPv6, providing both the possibility of tunneling IPv6 traffic over its tunnels and of creating tunnels over existing IPv6 networks.
Enhancements:
- This release fixes some memory and resource leaks, and makes network sockets non-blocking under Windows.

Need a Type 3 JDBC Driver for MS Access or SQL Server? Think RmiJdbc!
RmiJdbc project is a client/server JDBC Driver that relies on Java RMI.
All JDBC classes (like Connection, ResultSet, etc...) are distributed as RMI objects, so that you can distribute as you like the access to any database supporting the JDBC API.
In fact, RmiJdbc is just a bridge to allow remote access to JDBC drivers.
Why RmiJdbc?
- You develop a client/server application with databases on Windows (NT)? Use RmiJdbc along with the JDBC/ODBC Bridge, your Windows (NT) databases become remotely accessible in Java.
- You implement a JDBC Driver? Just implement the JDBC classes locally, dont bother with remote access!
- You need serializable JDBC classes? Here they are.
Enhancements:
- Add features/limitations/changes here