Free broadband software for linux

web-nsupdate is a web-based dynamic DNS update utility.

The web-nsupdate package provides a simple, web-based facility for clients to send dynamic DNS updates. Clients are typically DHCP hosts, such as a Linux system acting as a gateway for residential broadband service.

The client sends a simple web request (such as with the wget(1) or lynx(1) commands) to the web-nsupdate service to register their host request.

This package has been tested on a server with the following Debian packages:

* bind9 (ver 9.2.4-1)
* apache2 (ver 2.0.54-5)
* php4 (ver 4.3.10-16)

BE ADVISED: Its a pain in the butt to configure BIND to do dynamic DNS. You are going to need to do that to make "web-nsupdate" work. These instructions describe that process, so follow carefully. I *strongly* urge you to review the dnssec-keygen(8) and nsupdate(8) man pages first, so you can get some idea of what we are trying to accomplish.

Installation Instructions:

1. Copy the "web-nsupdate" files to a location such as
"/usr/local/lib/web-nsupdate". It is OK to install somewhere else,
just adjust the following directions accordingly.

2. Generate a TSIG key that "web-nsupdate" will use to authenticate
itself to the DNS server.

SECURE THIS KEY! Do not leave readable copies around. This key can
be used to make changes to DNS records managed by "web-nsupdate".

Here are the steps to generate the key:

cd /usr/local/lib/web-nsupdate
/usr/sbin/dnssec-keygen -a HMAC-MD5 -b 512 -n HOST web-nsupdate
chmod 440 Kweb-nsupdate*
# Below, adjust "www-data" to the GID your web server runs under.
chgrp www-data Kweb-nsupdate*

3. Setup the "web-nsupdate" definitions file, starting with the provided
sample. This file needs to be secured, to protect the client passwords
from being revealed.

cd /usr/local/lib/web-nsupdate
cp nsupdate-defs.php.sample nsupdate-defs.php
chmod 640 nsupdate-defs.php
# Below, adjust "www-data" to the GID your web server runs under.
chgrp www-data nsupdate-defs.php
vi nsupdate-defs.php

4. Verify that "nsupdate.php" has the correct path to the "nsupdate-defs.php"
file.

vi nsupdate.php
# Check the require_once() statement near the top.

5. Symlink the update script into your web site.

# Below, adjust "/var/www/nsupdate.php" to a location in your web server.
ln -s /usr/local/lib/web-nsupdate/nsupdate.php /var/www/nsupdate.php

At this point, the "web-nsupdate" front-end is configured. Now to
configure the nameserver back-end.

6. Assuming you dont already have a place for nameserver keys, create
a new file called "named.keys" that contains the TSIG key that
"web-nsupdate" will use. The file will look something like:

key web-nsupdate {
algorithm HMAC-MD5;
secret "jzzoMR4ocgZGq5pQho2Pr5r9DDHT4lWK8QO09cpvVtpvHqaUdzktBs1DHCslpPR8PwXU3ni8zjST/5FxEwg44Q==";
};

Replace the "secret" value show above with the key in the
"Kweb-nsupdate.+157+nnnnn.private" file you generated in step 2.

7. Install the "named.keys" file to the directory where your "named.conf"
resides. This file needs to be secured, to protect your namesever
from unauthorized updates.

If your "named.conf" directory is "/etc/bind", do:

# Below, adjust /etc/bind to directory where named.conf lives.
mv named.keys /etc/bind/named.keys
chmod 400 /etc/bind/named.keys
# Below, adjust "bind:bind" to the UID:GID your nameserver runs under.
chown bind:bind /etc/bind/named.keys

8. Add a line to your "named.conf" that says:

include "named.keys";

9. Modify your "named.conf" to list each host that web-nsupdate will
be updating. If, for example, you want to allow dynamic updates
from hosts "host1.example.com" and "host2.example.com", then modify
the "example.com" stanza in "named.conf" and add two lines:

zone "example.com" {
type master;
.
.
.
# add the lines below, one per host in thie zone
update-policy {
grant web-nsupdate. name host1.example.com. A;
grant web-nsupdate. name host2.example.com. A;
};
};

10. Test the update capability. Point your web browser to the installed
"nsupdate.php" script. This should bring up a form for manual
entry. Submit your entry, and verify the update was successful.

OpenInteract2::Manual::AdminApache is a Perl module for compiling and configuration Apache/mod_perl 1.x.

SYNOPSIS

This section of the OpenInteract2 manual will show you how to compile Apache and mod_perl for a two-server proxy setup, along with other information for configuring Apache.

Apache and mod_perl really arent difficult to setup. As long as you have a standard C compiler (GCC!) and a little patience its really a piece of cake.

APACHE 1.x OVERVIEW

OpenInteract2 depends on a persistent Perl environment within a web server. Currently, the best alternative is mod_perl 1.x.

mod_perl is extremely powerful, but this power can come at a price. Embedding Perl into Apache uses more resources (particularly memory) than just using Apache alone. A number of developers have experimented with various ways of minimizing the memory footprint of mod_perl, and one of the easiest and best performing methods is to use a proxy server.

This is described in great detail in the mod_perl guide under the Choosing the Right Strategy heading. But well summarize here:

Setup a plain Apache server with mod_proxy and mod_rewrite to listen to port 80 for your website. (We describe the build process below.)
Tell this server to deal with static file requests (images, movies, PDFs, etc.)
Proxy all other requests back to a heavier mod_perl server.
Receive the information back from the mod_perl server and send to the client.

The benefits of this are:

Resource-hogging mod_perl processes do not serve static files -- if they did, youd need more of the processes.
Since OI2 can run under a URL context you can segment your site to different application servers. For instance, you can say that everything under /oi goes back to your OI2 application server running under mod_perl and everything under /jsp goes to a Tomcat web container with your Java Server Pages. But to the user its all under one site -- nifty.
The front-end proxy is able to feed data back to the client at whatever rate it needs without taking up many resources the entire time. For instance, users reaching your website with modems can tie up a web server process for much longer than users who are on some sort of broadband network. If the process is small its not such a big deal.
Since they are separate, you can make changes to the (heavy) back-end and mask them by the (light) front-end. This is a great help when things are going wrong with the back-end and you dont want users to see nasty error pages.
Also since they are separate, you can very easily move the back-end process to an entirely separate machine (or machines, using some sort of DNS or load-balancing manipulation) if the need arises.

Running OpenInteract2 in this environment is strongly recommended, and it comes with configuration files that make it easier to do the Right Thing.

Bandwidth Meter and Diagnostics is a Firefox extension that will automatically check whether Internet connection is working or not when a website can not be loaded, and a list of tools for network troubleshooting. Try to type a random domain name(e.g., qwqwqwq121212.com) to see what this means ...
This extension adds "Bandwidth Meter" to the Tools Menu. It performs the following tasks:
- Display your public IP address
- Display your public domain name
- Test download speed/bandwidth
- Test upload speed/bandwidth
This extension runs under any OS. If you use Windows, you could try our other Windows specific extension "Broadband Speed test and Diagnostics" that has extra features and can only run under Windows. We are creating this because we get many requests from non-windows users.

DOOM 3 is a sci-fi horror masterpiece, DOOM 3 is like nothing you have experienced.
id Software has released a new patch for its FPS DOOM 3. This update brings your retail game to v1.3.1 and adds various fixes and improvements, Vista compatibility, and bringing back cross-platform multiplayer compatibility with the Mac.
Minimum System Requierments:
3D Hardware Accelerator Card Required - 100% DirectX 9.0b compatible 64MB Hardware Accelerated video card and the lateset drivers*.
English verision of Microsoft Windows 2000/XP
Pentium IV 1.5 GHz or Athlon XP 1500+ processoror higher
384MB RAM
8x Speed CD-ROM drive (1200KB/sec sustained transfer rate) and latest drivers
2.2GB of uncompressed free hard disk space (plus 400MB for Windows swap file)
100% DirectX 9.0b compatible 16-bit sound card and the latest drivers
100% Windows compatible mouse, keyboard, and latest drivers
DirectX 9.0b (included)
Multiplayer Requierments:
Internet (TCP/IP) and LAN (TCP/IP) play supported.
Internet play requires broadband connection and latest drivers
LAN play requires network interface card and latest drivers
Enhancements:
- Tested and improved Vista compatibility
- Fix a potential crash in physics
- Fix an issue with pak downloaded being immediately appended without filesystem restart
- Fixes to DNS lookup, reduced the stalls
- Updated the code to gcc 4.0 compliance, for Mac OSX universal binaries and GNU/Linux x86 binaries
- Threading implementation for Mac and Linux is more compliant with the Win32 behaviours
- Fix Alsa sound backend (Linux)
- Fixes to tty code (Linux)

Automatic Firewall is a script that will automatically configure a firewall. If you are a broadband or dial-up user who doesnt have a firewall script, you need to get one to protect yourself. AutoFW is made to help you do that with no efforts.
Many people when connecting to the internet need a firewall script made for them so they can surf the net without being susceptible to various attacks. Most, if not all (until now :-), of the existing scripts are written for a large range of requirements and require some tweaking to make them work for a specific user. However many users do not know which parameters to fill in the script config file.
AutoFW intends to provide a simple firewall script that you just need to fire and forget. You make sure to run it on computer start-up or just before connecting to the net, and it will detect network condition and setup appropriate firewall rules for you.
In order to be "smart" AutoFW has to be limited, the current scope of AutoFW are standard broadband connections, it will also cover dial-up users and stand-alone servers.
AutoFW works only for Linux IPTables firewall and needs the iptables utility to update the firewall, it also needs the ifconfig utility, both of these are available on any standard install of a GNU/Linux machine.
AutoFW also needs the ip program which is part of the iproute2 package, sometimes also called iproute. It is available as a package for any standard GNU/Linux install, not it might not be installed in your particular.
There are two parts that do automatic detection, one is for interfaces and IPs and the other is for open listening ports.
The interface part looks at all the active interfaces in the machine and classifies them between internal and external. It does that by looking at the IPv4 address of the device. If it is one of:
127.0.0.0/8
10.0.0.0/8
172.16.0.0/12
192.168.0.0/16
it is considered to be an internal IP and thus an internal interface, otherwise it is an external IP and thus an external interface. There is no handling of an interface with both an internal and an external IP on it.
The listening ports are scanned for a known port and the accompanying known program name that binds to that port, known ports are opened later in the configuration stage.
The configuration itself is very simple for now, without many of the bell and whistles that exist in other scripts, but it works for the basic needs and provides adequate protection.
Enhancements:
- Internal systems are now protected, as well as servers and NAT gateways.