Free cnc routers software for linux

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

Cutter is an TCP/IP Connection cutting on Linux Firewalls and Routers.

Cutter is an open source program that uses the FIN-ACK-RST packet technique described above to abort TCP/IP connections routed over the firewall or router on which it is run. It can be called using one of the following four syntaxes.

cutter ip-address

Example: "cutter 10.10.0.45"

Cuts all connections passing through the firewall between any ports on the specified ip-address (either a "private" or "public" address) and any other hosts. This can be used to close down all incoming connections to a particular server, all outgoing connections from a particular client or all outgoing connections to a server.

cutter ip-address port

Example: "cutter 200.1.2.3 80"

Cuts all connections to or from the specified ip-address/port pair. This allows the user to be a little more specific than the previous example and allows targetting of specific services on specific hosts.

cutter ip-address-1 port-1 ip-address-2

Example "cutter 200.1.2.3 22 10.10.0.45"

Cuts all connections between ip-address-2 and ip-address-1/port-1. This allows the user to cut connections between a specified "client" and a particular service on a specified host. Our example closes host 10.10.0.45s SSH connection to server 200.1.2.3.

cutter ip-address-1 port-1 ip-address-2 port-2

Example: "cutter 200.1.2.3 22 10.10.0.45 32451"

Cuts the specific connection between the two ip/port number pairs given.

IMPORTANT WARNING

Cutter has been designed for use as a administrators tool for Linux firewalls. Its use (as is, or modified) for any other purpose is not sanctioned by the author. So - do not use this tool as a parachute, or to dry your cat, chill meat, answer your phone, drive you car, teach your kids to read or attack other peoples computer systems or networks.

This software has been designed for "legal" and "appropriate" use by network security administrators and the like. It has been written as part of a larger Linux firewall project, targetting at controlling traffic from peer-to-peer software such as Kazaa, iMesh and others into and out of a private network. It is not designed as a tool for malicious use and the author in no way sanctions such use.

Users of the software should be aware that its actions are easily detectable using a number of readily available network monitoring tools, and it makes no attempt to disguise its actions. Malicious use of "cutter" could result in a jail sentance in a number of countries around the world.

IP accounter application measures and graphs traffic for IPv4 and IPv6 netfilter-based routers. Input data is accounted using several abstraction layers (routers, hosts, flows), and IPv6 traffic accounting may be mixed with IPv4.
Enhancements:
- The WEB frontend is still unavailable. There were some minor dificulties running ipaccounter. Still the main issue is when mysql server crashes. The traffic info is then lost until someone fixes it. Therefore it is advised to use some net watching software like Nagios. For further feature enchancements see the ChangeLog. 2006-09-02 by Ondra Ipaccounter-1.0 was released. Only WEB frontend is unavailable at the moment. The accounter is run on one machine. Namely maximus.spi-net.org. There were no fault ancountered so far, but its running only for one week.

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.

Dropbear is a relatively small SSH 2 server and client. Dropbear SSH runs on a variety of POSIX-based platforms.
Dropbear is open source software, distributed under a MIT-style license. Dropbear is particularly useful for "embedded"-type Linux (or other Unix) systems, such as wireless routers.
Main features:
- A small memory footprint suitable for memory-constrained environments - Dropbear can compile to a 110kB statically linked binary with uClibc on x86 (only minimal options selected)
- Dropbear server implements X11 forwarding, and authentication-agent forwarding for OpenSSH clients
- Can run from inetd or standalone
- Compatible with OpenSSH ~/.ssh/authorized_keys public key authentication
- The daemon, keygen, key converter, and client can be compiled into a single binary (ala busybox)
- Features can easily be disabled when compiling to save space
- TCP forwarding support

ProQuake project is a Quake engine for advanced deathmatch play, including cheat-free mode.
ProQuake is a modification to the Quake source which is specifically intended for intense deathmatch play.
It is a rock solid set of enhancements to unmodified NetQuake, such as precise aim, and other small, simple changes that improve the quality of netplay enormously.
ProQuake is fully compatible with standard NetQuake and Clanring CRMod++ features including team scores, match timer, and client pings.
Main features:
- Eliminated cheat-free lag for modem players on 3.50 servers
- "cheatfree" command tells you if youre connected to a cheat-free server
- Connect to 3.40 servers through routers/NAT/IP Masquerading
- Four button mouse support
- Mouse wheel support
- Fullbright shaft in glpro
- r_polyblend in wqpro
- QuakePro+ bestweapon command
- Recognizes ip_address:port notation
- Remove r from console output
- Added %d for binds to say where you died
- Various minor bug-fixes and improvements
- Eliminated cheat-free lag for 3.50 modem players
- Append "(cheat-free)" to the host name for cheat-free servers
- 3.40 clients can connect through routers/NAT/IP Masquerading
- iplog supports multiple concurrent servers
- Clients without map can connect to cheatfree server
- Cheat protection
- Fixed incoming message buffer overflow (q1crash)
- Added pq_logbinds to store player binds in log file
Enhancements:
- ProQuake 3.50 eliminates the lag that modem users were experiencing on cheat-free servers.

CTShaper is a shell-script that helps setting up a traffic shaper, using Linuxs built-in network QoS (Quality of Service) infrastructure.

Have you ever noticed how your SSH/gaming sessions become sluggish when you start downloading something, or how your downloads slow down when you start uploading?

Have you ever been annoyed by other peoples downloads forcing you to wait ages while an email is being sent? Or making your web navigation painfully slow?

Well, if your outgoing link is managed by a Linux router/gateway, then you could benefit from using CTShaper.

CTShaper reduces link latency by preventing packet queues from getting too long on your side (your ADSL or Cable modem) and on your ISPs side (their routers). Long packet queues is what makes your uploads interfere with your downloads, and your downloads interfere with your SSH or gaming sessions.

Additionally, CTShaper sets up four traffic queues with different priorities and configurable flow rates (to have minimum bandwidth guarantees for each class). By default, only traffic with ToS (Type of Service) information gets prioritized (which could be enough, if lots of software had support for it, which they dont), but you can use your firewall (iptables, or an iptables frontend like FireHOL) to "mark" traffic.

The traffic shaper will then prioritize (outgoing) traffic based on those "marks". You can, for instance, give priority to SMTP and HTTP traffic. This will only affect outgoing HTTP and SMTP traffic, but thats enough to make your emails go out faster, and your web navigation more responsive.