Free mikrotik routers software for linux

Web Site Robot is an easy to use Web site builder with a blog tool, shopping cart, and online photo album. It is free and does not require additional software, HTML, programming, or a hosting company.
It enables secure online payments with credit cards. There is virtually unlimited storage space for HTML, documents, blogs, photos, music, videos, or any multimedia content.
Enhancements:
- The Robot is now able to discover and inform UPnP routers about its presence and the need to have a NAT port available for its Web server.
- In most SOHO environments with UPnP enabled routers, manual configuration is not needed.
- The operator just installs, registers the Robot and the Web site is online effortlessly.

Snmpstat shows router interface information and statistics through web interface using SNMP protocol.

Tested on Linux/Apache for CISCO routers, Route Lynx RL-2000 routers.

Rodent is an ident daemon that is capable of routing AUTH requests to other machines on your network.

Rodent is intended for routers or to be run on a machine behind a home router.

Rodent allows others to enjoy full ident without the limitations of port forwarding to a single machine.

Cisco IP Accounting Fetcher is a set of Perl scripts that allows you to fetch IP accounting data from Cisco routers. There is the only one config file - "getdata.conf for configuration.
Main features:
- fetch accounting data from the router
- generate the HTML statistics

Linux LiveCD Router project allows you to share and firewall your broadband connection and use WIFI.
You can use DSL, ADSL, Cable Modem, T1, Fixed IPs, Dial-Up, WIFI, build you own Access Point and more.
Main features:
- Share and Firewall your broadband or dedicated Internet connection
- Includes Firewall Shorewall and Masquerading (NAT)
- Does not require any installation. It is a LiveCD, your computer simply boots straight from the CD. Does not require a hard disk
- Supports DSL, Cablemodem, Fixed IP and Dial-Up
- Traffic Control, QoS
- DHCP Client and Server
- Remote SSH administration
- Includes DNS Cache to accelerate surfing
- Includes SNMP Monitoring, MRTG graphical statistics
- Use standard and low cost computer, networking and wifi hardware (also USB)
- Can use multiple ethernet and wifi 802.11a/b/g cards. Supports PCI, USB and PCMCIA cards (can replace external Access Points!)
- Linux Software compatible with Windows and Mac Networks

Snmp Monitor provides a SNMP router and monitoring alarms.

Snmp Monitor is a Scotty extension to monitor SNMP variables on the net. If there are changes to the routers, etc., it can send you a message on your cellular, by email, or via the screen.

di624stats.pl is a Perl script that screen-scrapes the Web interface of a D-Link DI-624 wireless NAT router to gather traffic statistics. You can use RRDtool to store these statistics and generate graphs. Instructions for using di624stats.pl in conjunction with RRDtool are included.

1. Make sure you have RRDtool installed. Get it at
http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/ or from an APT
repository or from *BSD ports.

2. Create an RRD file to store your routers throughput statistics. For
example, go like this (read the rrdtool(1) man page if this is
confusing):

rrdtool create di624.rrd
--step=300
DS:in:COUNTER:600:0:12500000
DS:out:COUNTER:600:0:12500000
RRA:AVERAGE:0.5:1:288
RRA:AVERAGE:0.5:4:504
RRA:AVERAGE:0.5:144:730
RRA:MIN:0.5:1:288
RRA:MIN:0.5:4:504
RRA:MIN:0.5:144:730
RRA:MAX:0.5:1:288
RRA:MAX:0.5:4:504
RRA:MAX:0.5:144:730

For more information about install read the README file.

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.