Free juniper routers software for linux

Diet-Router provides a singe floppy DSL router.
Diet-Router is a Linux router that is small enough to fit on a single floppy disk. It focuses more on security than on functionality.
Diet-Router is a Linux router built with the dietlibc. It is small enough to fit on a single floppy disk. You may think that there are several other Linux routers, which come with more features and you are right. I build this router package more with the view on security than of functionality. So this project differs a lot from most other router or mini-Linux projects.
Main features:
- I use a 2.4.x kernel to have the great features of net-filter.
- I patch some net-filter extensions to have even more filter functions.
- I harden the kernel with the grsecurity kernel patch.
- Kernel modules are disabled.
- By default root login is disabled - even on the console.
How does it work:
First of all, all programs are linked statically. This is the main idea of this system. No libraries are needed. It uses busybox and tinylogin, two typical multi-call-binaries for small systems. The iptables, iptables-restore and iptables-save commands have been made a multi-call binary by me. The pppd and pppoe programs have only been patched to compile with the dietlibc. The minit and od_syslog are really small programs, from people with much more knowledge of programming than me. So, special thanks to Felix von Leitner, Olaf Drefs and all the dietlibc/libowfat programmers.
Enhancements:
- Updated dietlibc, libowfat, dropbear, ppp, kernel and grsecurity to recent
- versions.
- Added new packages dhcp server (udhcpd) and vi (e3).
- The build system has been completely rewritten and documented.
- It supports multiple downloads, a simple interface for package building/setup and target file descriptions including file owner and permissions.
- Some simple checks for build requirements are implementet.
- The setup is now able to configure mutiple network interfaces and also mproxy, udhcpd and dnscache can be configured for eachnetwork interface.
- All packages have at least two internet sources.
- Support for disc based target systems has been added.

Net::BGP::Router is a BGP Router based on Net::BGP.

SYNOPSIS

use Net::BGP::Router;
# Constructor
$router = new Net::BGP::Router(
Name => My very own router!,
Policy => new Net::BGP::Policy
);
# Accessor Methods
$router->add_peer($peer,both,$acl);
$router->remove_peer($peer,both);
$router->set_policy($policy);
$router->set_policy($peer,in,$acl);
__top

This module implement a BGP router. It uses Net::BGP objects for the BGP sessions and a Net::BGP::RIB object to store the routes. Policy are handled using a Net::BGP::Policy object.

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.

SMCRoute is a command line tool to manipulate the multicast routes of the Linux kernel. It can be used as an alternative to dynamic multicast routers like mrouted in situations where static multicast routes should be maintained and/or IGMP doesnt exist properly implemented
Enhancements:
- fixed the mroute: pending queue full, dropping entries error
- Smcroute 0.90 didnt care about the IGMP messages delivered to the UDP socket that establish the MC-Router API. After some time the queue for the sockets filled up and the pending queue full message was send from the kernel. To my knowledge this didnt affect smcroute or the operating system.
- version 0.92 reads the ICMP messages now from the UDP socket and logs them to syslog with daemon/debug
- smcroute does no further processing of this messages
- increased the number of supported interfaces The 16 interface limit of version 0.90 (interfaces as listed with ifconfig) was to small, especially when alias interfaces where defined.
- up to 40 interfaces are no recognized by smcroute - this does not change the number of virtual interfaces supported by the kernel (32)
- not all interfaces recognized by smcroute (40) results in a virtual interface of the kernel (32)

OpenWrt is a Linux distribution made for wireless routers. Instead of trying to cram every possible feature into one firmware, OpenWrt provides only a minimal firmware with support for add-on packages.
For users this means the ability to custom tune features, removing unwanted packages to make room for other packages and for developers this means being able to focus on packages without having to test and release an entire firmware.
Enhancements:
- Countless bugfixes, various security patches, improved Failsafe, faster installation (new firstboot script), a multilingual Web interface (Cesky, Deutsch, Dansk, Eesti, Espanol, Francais, Italiano, Norsk, and Polski), and ethernet switch configuration (/proc/switch).

CIPE is a Crypto IP Encapsulation.
This is an ongoing project to build encrypting IP routers. It works by tunneling IP packets in encrypted UDP packets. The protocol is designed to be lightweight and simple. Special care has been taken to make this work over dynamic addresses, NAT and SOCKS proxies.
Implementations are currently available for Linux and Windows.
Enhancements:
- This supports Linux 2.6 and the kernel crypto API.