Free routing software software for linux

BitWise Routing Server allows multiple PCs behind a router to make direct connections.

The BitWise Routing Server allows you to accept BitWise connections to multiple computers behind a router. Typically, using a router, you would set up port forwarding on BitWises client port (4137), and specify a single destination IP. This is fine until multiple users behind a router all need to accept incoming connections.

As shown by the picture at right, the Routing Server allows individual users to register themselves with the Routing Server, and then the Routing Server accepts all incoming connections and directs those connections to the appropriate user.

The Routing Server requires that your physical router support port forwarding with a way to specify different external and internal ports (this is sometimes labeled "UPnP" by many common home routers).

The Routing Server has several options allowing you to customize the Routing Server for your environment. Many of the options are self-explanatory. The two that are not are Listen on Port and IP filtering. IP filtering is explained in the next section.

The BitWise Routing Server listens on a different port than the BitWise IM client. This allows the Routing Server and the IM client to be run on the same computer without causing conflicts. You will want to set up your router (more detail in a later step) to shift the port of the incoming connections from 4137 to another port. It doesnt particularly matter which port you want to use, as long as it is not a port used by another program. The default port is 4200.

Depending on the complexity of the network, it may be desirable to filter the IP addresses that are allowed to register with the Routing Server. This can be done in the preferences. One very likely scenario would be limiting registrations to the 192.168.1.x IP addresses (192.168 is reserved for local networks). When specifying an IP as the comparison address, you can use any valid IP numbers for wildcards.

In the case shown here, the Routing Server will limit connections to computers having IP addresses of 192.168.1.x. Any number, 0 through 255, could be placed for x in the Routing Server preferences.

If you are not familiar with IP address classes and IP filtering, it will usually be safe to leave Any selected.

Setting up the physical router

The picture at right was taken from a Linksys router, other routers will have a similar capability, although it may be layed out differently. On some routers, the advanced port forwarding options are mistakingly labeled UPnP.

The router setup shows that we are accepting connections on port 4137 and then sending them inside the network on port 4200 (the default port). Enter the IP address of the machine on the network running the Routing Server, and make sure that the rule is enabled. You will want to enter a rule for both TCP and UDP (UDP is used only for voice).

Please consult your router manual for more detailed instructions about how to set up port forwarding on your specific model.

Configuring BitWise to use the Routing Server

In order for you to enjoy the connectivity benefits of the Routing Server, you will need to register with the Routing Server when you log in to BitWise. Prior to logging in to BitWise, click the Setup button next to the Connect button to open the BitWise Setup. There is an area to enter an address for the Routing Server, and to specify what port to use. The port must be the same as the port used above (4200 is the default).

Upon connecting to BitWise, you will be registered with the Routing Server. If you could not be registered, an error message will be displayed. Double-check that the correct address was entered in the Setup.

Registration with the Routing Server

Upon successfully registering with the Routing Server, the Routing Server will display the user name and the IP address of the registration. If you want to unregister a user, click on the username, and then click Unregister. Incoming connections will no longer be forwarded to the specified computer.

It is worth pointing out two things here. First, if you later log in from a different computer, and that computer is also set to use the Routing Server, you will be re-registered with your new IP address. Second, if you are unregistered, or move to another computer but are not set up to use the Routing Server, you will not be able to benefit from the services of the Routing Server.
By default, the Routing Server saves the registered user list when it is closed down.

Using the Routing Server

Assuming that everything is set up correctly, everyone that registers with the Routing Server when they log in to BitWise will be able to enjoy significantly increased connectivity with other BitWise users. As incoming connections are established, you will see the connections listed in the right pane of the Routing Server window. The IP address and the time of the connection is also displayed, and the connection is later marked when it is disconnected.

The disconnected/closed connections may be cleaned from the list at any time using the Clean List button. Only active connections will be left displayed.

Internet Registry Routing Daemon (IRRd) is a freely available, stand-alone Internet Routing Registry database server. IRRd supports the RPSL and RPSLng Routing Policy Specification Language standards.

The IRRd package includes all required IRR support services, including: automated near real-time mirroring of other IRR databases, update syntax checking, authentication/security, and notification.

Arping is an ARP level ping utility. Its good for finding out if an IP is taken before you have routing to that subnet. You can also ping MAC addresses directly.

Broadcasts a who-has ARP packet on the network and prints answers. VERY useful when you are trying to pick an unused IP for a net that you dont yet have routing to. Then again, if you have no idea what Im talking about then you prolly dont need it.

Arping is util to find out it a specific IP address on the LAN is taken and what MAC address owns it. Sure, you *could* just use ping to find out if its taken and even if the computer blocks ping (and everything else) you still get an entry in your ARP cache. But what if you arent on a routable net? Or the host blocks ping (all ICMP even)? Then youre screwed. Or you use arping.

Ad-hoc Wireless Distribution Service (AWDS) is a Layer 2 routing protocol for wireless mesh networks. The project provides transparent Ethernet-like access to all participating nodes, thus easily allowing the employment of different higher level protocols like IP (with DHCP), IPv6, AppleTalk, ...

A Linux implementation of AWDS can be downloaded from our download section. Ports to other platforms are highly appreciated!

Radio Shortest Path First (RSPF) is a routing protocol for wireless networks. This particular implementation is written for Linux and conforms to version 2.2 of the protocol specification. There are many reasons why our networks are complicated, but one significant thing is that you can no longer assume that just because you hear one station, then they can hear you. This means you can have a lot of unidirectional routes.
The current specification is RSPF version 2.2, written by Fred Goldstein K1IO. Until recently, if people were using RSPF at all, they would of been using RSPF version 2.1, which is available in the NOS program, written by Phil Karn and others. The RSPF code itself in NOS was written by Anders Klements.Thats why standard protocols dont work very well over amateur packet radio.
Now with the knowledge of how his protocol worked in real life, Fred then updated and improved RSPF to version 2.2. And, until late 1995, that was all that happened.
What did happen was that I was in my senior years in my undergraduate degree at University of Technology, Sydney and looking for an interesting Thesis. After seeing emails from Carl Makin VK1KCM asking if anyone was going to fix RSPF in NOS, this gave me my idea for my Thesis.
Enhancements:
- Control port speaks IPv6
- Made the ChangeLog prettier
- Fixed the checksum code so it works.
- Put everything through syslog()
- :s/t/ /

NSH is intended to handle configuration for interfaces, bridging, routing, packet filtering, NAT, and ISAKMP. It presents the user with a vaguely cisco-like interface.

It also gives the user access to system information and diagnostics. NSH replaces the userland commands which handle these functions, and talks directly to the OpenBSD kernel (with exceptions for pfctl, isakmpd, and dhcpd).

NSH is completely free, it only incorporates code with BSD-style licenses.

The current version fixes bugs from the last release and brings NSH up to speed for OpenBSD 3.7 and 3.7-current.

For the next major release, Im planning on some IPsec, OSPF, BGP, and DHCP functionality, and possibly ping and other functions. (Also, a rework of the CLI code might happen) The CLI is functional for information/diagnostics, and configuration of pf/nat/altq, interfaces, bridging, and routing.

Linux Advanced Routing & Traffic Control HOWTO is a document concerning iproute2, traffic control (shaping), and more!

The LARTC-HOWTO describes many advanced ways of routing and shaping traffic.

Using the HOWTO, you will be able to shape traffic in myriad ways, which will help you lower latency for interactive use when others are downloading or uploading.

It will also teach you how to limit certain hosts/protocols bandwidth usage. It also explains many aspects of routing using the ip tool from the iproute2 suite.