proxy server

Install Squid
Install squid and squid-common

sudo aptitude install squid squid-common


Edit the squid config file.

sudo vi /etc/squid/squid.conf


Set the allowed hosts.

acl internal_network src 192.168.0.0/24 (Where 192.168.0.0/24 is your IP range.)
http_access allow internal_network

Set the correct permissions.

sudo chown -R proxy:proxy /var/log/squid/
sudo chown proxy:proxy /etc/squid/squid.conf


You will need to restart squid for the changes to take affect.

sudo /etc/init.d/squid restart

Now open up your browser and set your proxy to point to your new squid server on port 3128

Authentication
If you wish to use authentication with your proxy you will need to install apache2 utilities

sudo aptitude install squid squid-common apache2-utils

To add your first user you will need to specify -c

sudo htpasswd -c /etc/squid.passwd first_user

Thereafter you add new users with

sudo htpasswd /etc/squid.passwd another_user

Edit the squid config file

sudo vi /etc/squid/squid.conf


Set the the authentication parameters and the acl

auth_param basic program /usr/lib/squid/ncsa_auth /etc/squid.passwd
auth_param basic children 5
auth_param basic realm NFYE Squid proxy-caching web server
auth_param basic credentialsttl 3 hours
auth_param basic casesensitive off

acl users proxy_auth REQUIRED
acl sectionx proxy_auth REQUIRED
http_access allow users

So this is what your squid.conf should look like.

acl all src 0.0.0.0/0.0.0.0

acl internal_network src 192.168.0.0/24
acl users proxy_auth REQUIRED
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 563 # https, snews
acl SSL_ports port 873 # rsync
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 563 # https, snews
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl Safe_ports port 631 # cups
acl Safe_ports port 873 # rsync
acl Safe_ports port 901 # SWAT
acl sectionx proxy_auth REQUIRED
acl purge method PURGE
acl CONNECT method CONNECT
http_access allow manager localhost
http_access allow users
http_access allow internal_network
http_access deny manager
http_access allow purge localhost
http_access deny purge
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost
http_access deny all
http_reply_access allow all
icp_access allow all

Redirect the all HTTP traffic.
If you would like to redirect the all HTTP traffic through the proxy without needing to set up a proxy manually in all your applications you will need to add some rules

iptables -t nat -A PREROUTING -i eth1 -p tcp -m tcp --dport 80 -j DNAT --to-destination 192.168.0.1:3128
iptables -t nat -A PREROUTING -i eth0 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 3128


Where eth1,eth0 are the LAN, WAN devices and 192.168.0.1 is the IP address of your LAN device.
If you wish to monitor the performance of your proxy you can look as some log parser’s (sarg, calamaris, ect.)

After all, probably you feel the need to monitor the performance of your proxy. Unfortunately, most of the squid log parsers in the Ubuntu repository are configured for Squid 2.x. Nevertheless, squid 3 uses the same log format, so you can change the log file path in your parser config file (sarg, calamaris, etd.) or simply link the log directory of squid 3 to the correct path

ln -s /var/log/squid3 /var/log/squid

Source : kuscsik

Post installation

After a successful installation and boot to the newly installed Ubuntu Lucid with out problem, now it’s time for the post-installation. You might consider to create a user if you want, login as root with your previous password:

Step 1. You will need to edit your hosts file

So I want to install Ubuntu Linux for my other system without using a cdrom, but I dont want to do it on that system, instead of that I want to install it via my current working ubuntu desktop that Im using right now.

Actually I want to build a firewall system complate with hotspot gateway and freeradius. But for now lets start with the basic installation first.

You could follow the instruction from ubuntu help community by Curtis Lee Bolin : Installation From Linux or you can continue to read it from here because I made a little modification for the installation method and I add the instruction for the post-installation and how to setup a firewall base system.

How to install without CD

You can install Ubuntu directly from Ubuntu using debootstrap. Debootstrap installs some essential packages in a directory for use with chroot. Note that the essential packages does not in itself make the system bootable. It just installs what you need to chroot to that directory and use apt-get to install other packages witch makes ubuntu usable.

Step 1. First turn off you computer and plugin your hard drive to it, after turn it on back then check that you have debootstrap installed if not, then you should run the following command below:

# sudo apt-get install debootstrap

(NOTE: if you want to install a newer release than your current system, you normally need to install the backported debootstrap version, see: UbuntuBackports)

Step 2. Partition device and make a file-system, to make it more easy, I use cfdisk to create partition for the other drive.

We will assume /dev/sdb is the storage device for your fresh install. I use my thumbdrive to show you an example how to partition the other drive for another system to setup an installation of ubuntu linux from your current ubuntu desktop.

Remove former partitions and create the new on.

# sudo cfdisk /dev/sdb

cfdisk (util-linux-ng 2.17.2)

Disk Drive: /dev/sdb
Size: 2056257536 bytes, 2056 MB
Heads: 64   Sectors per Track: 62   Cylinders: 1012

Name        Flags      Part Type  FS Type          [Label]        Size (MB)
——————————————————————————
sdb1        Boot        Primary   W95 FAT32 (LBA)                   2056.00

[ Bootable ]  [  Delete  ]  [   Help   ]  [ Maximize ]  [  Print   ]
[   Quit   ]  [   Type   ]  [  Units   ]  [  Write   ]

Use your arrow key to the [ Delete ] option to remove your partition on the other drive:

Name        Flags      Part Type  FS Type          [Label]        Size (MB)
——————————————————————————
Pri/Log   Free Space                        2056.00

[   Help   ]  [   New    ]  [  Print   ]  [   Quit   ]  [  Units   ]
[  Write   ]

Create new partition from free space, then you will see your drive is empty, now select [ New ] to create your new partition and select [ Primary ] :

Name        Flags      Part Type  FS Type          [Label]        Size (MB)
——————————————————————————
Pri/Log   Free Space                        2056.00

Size (in MB): 1500

You need to enter new size limit for primary partition, press backspace then enter the size yo want, for example I use 1500MB and 500MB++ for the extended and swap partition.

Now create the rest of your free space as an extended and swap, to change type of your newly created partition navigate to [ Type ] press Enter and select 83 for linux and 82 for swap.

Name        Flags      Part Type  FS Type          [Label]        Size (MB)
——————————————————————————
sdb1        Boot        Primary   Linux                             1499.34
sdb5                    Logical   Linux swap / Solaris               556.67

and select your primary partition as bootable by press the option [ Bootable ]. The write down your partition and quite cfdisk.

Are you sure you want to write the partition table to disk? (yes or no): yes

then [ Quit ] and start to make the file-system

# sudo mkfs.ext4 /dev/sdb1

Step 3. Mount that new partition.

# sudo mkdir /mnt
# sudo mount /dev/sdb1 /mnt

Step 4. Create the new install.

# sudo debootstrap lucid /mnt

Step 5. Copy files to the new install to keep your repositories

# sudo cp /etc/apt/sources.list /mnt/etc/apt/

Step 6. Chroot to your new install.

# sudo mount –bind /dev /mnt/dev
# sudo mount -t proc /proc /mnt/proc
# sudo chroot /mnt /bin/bash

Step 7. Upgrade the new install.

# apt-get update
# apt-get install language-pack-en-base

Note: I install the language-pack-en-base before upgrade to avoid perl warnings as shown below.

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = “en_US.utf8″
are supported and installed on your system.
perl: warning: Falling back to the standard locale (“C”).
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

then continue with :

# apt-get upgrade

Step 8. Install Grub and Linux Kernel.

# apt-get install grub-pc linux-image

Step 9. set root password.

To set a root password.

(NOTE: You must at least set a root password if you aren’t adding a user)

# passwd

It should now be safe to reboot, you may want the next few things.

Step 10. If you want to access it with ssh after reboot.

Use vi or install nano to edit /etc/hostname.

Remove anytext in this file and add the hostname you would like.

# vi /etc/hostname

yourhostnameyouwant

and then edit /etc/network/interfaces

# vi /etc/network/interfaces

Add this lines to /etc/network/interfaces. This will start eth0 at boot and request an ip with dhclient.

auto eth0
iface eth0 inet dhcp

Next you need to install ssh

# apt-get install ssh

Turn off your computer, remove the new installation drive and plugin to the other system, and bootup the system. If you want the Ubuntu Gnome desktop, continue with Step 11, but if you want to setup a firewall base system, so just skip the Step 11 and Step 12, so it safe for you turn off your system and boot the drive from other system.

Step 11. Install ubuntu-desktop.

# apt-get install ubuntu-desktop ubuntu-standard

Step 12. Reboot and keep those fingers crossed.

# sudo halt or sudo reboot

To be continue on Part 2

My actual problem is :

1. the UTP cable on POE Adapter is not working to transmit data via it own UTP cable, to buy a new one it cost about $25-$60 buck(RM80 – RM200), but why spending when you can still use the POE Adapter as power supply, except for the broken UTP cable on the POE Adapter.
2. the current UTP installed with Linksys WAP54GPE with RJ45 PCB Socket attached on it is not working too.

the power is there but not the network connection

My Solution :
Splitting 1 UTP cable into POE connector and networking cable. At the first end of the UTP cable clamped as normal straight cable, and the second end we split it one as data cable and the other as power supply cable. So pins 1,2,3 and 6 will be connected to the switch.

like this one

We see that the TX (transmitter) pins are connected to the corresponding RX (receiver) pins, plus to plus and minus to minus. You can also see that both the blue and brown wire pairs on pins 4, 5, 7, and 8 are not used in either standard, but actually it was used as power transmiter between the POE Adapter and WAP54GPE Access Point.


What you may not realize is that, these same pins 4, 5, 7, and 8 can be used as data or network cable as well if we going to split one UTP cable to be connected to two NIC on the same computer system such as linux pc based router/firewall, so for pins 4,5,7 and 8 are used as power supply pins.

This is because I was so eager and can wait to buy Ironman 2 and Clash Of The Titan DVD.

After searching and googleling for solution then I’ve find out how to upgrade to Limewire 5.5.8.

Just follow these simple instruction here :

1. sudo add-apt-repository “deb http://archive.canonical.com/ lucid partner”
2. sudo apt-get update
3. download Limewire Basic 5.5.8 for Ubuntu Linux from here http://www.limewire.com/LimeWireSoftLinuxDeb
4. search for the downloaded file, double click and follow the installation prosess

If you prompted with authentication key for Limewire Pro, just ignore it, click cancel and proceed to use it as usual.

There is another software you might consider to try, I just installed it but dont have any intentions to explorer gtk-gnutella, but you can give a try.

One of the most important thing that cyber cafe or internet cafe owners should not forget is a firewall. I am not going to brief about firewall history here, but from my experiences dealing with business that has an internet access, a firewall is a must.

They are many kind of firewall system and application you can try for free, and one of them are Smoothwall Express 3.0 polar. Further more SmoothWall Express is not just a firewall but it can also to be setup as a proxy server. Yeah, normally a cyber cafe really needs a proxy server to release the burden of their connection.

Installing and configuring a Linux firewall can be one of the most difficult tasks Linux administrators face. In addition to actually configuring the gateway, few admin pros have expertise with securing the network through ipchains.

Not to worry. The SmoothWall Linux distribution simplifies the otherwise daunting task of sharing Internet connections and providing network security. This relatively new Linux distribution is used for one purpose: to provide an easy-to-configure firewall with minimal hardware requirements. Typically, you can convert an older desktop system that has outlived its word-processing and Web-surfing usefulness into a formidable firewall box. SmoothWall is able to run on processors as old as a 386 with 8 MB of RAM. In this Daily Drill Down, I’ll discuss how to install and configure SmoothWall.

What you need

• Intel-based PC (386 or greater) with 8 MB of RAM
• CD-ROM drive
• 100 MB of disk space
• Access to a CD-ROM writer

SmoothWall Express Polar Screenshot

Nice simple and slick web administration interface

Source : http://articles.techrepublic.com.com/5100-10878_11-1053408.html

Links:
[1] http://www.linuxjournal.com/content/dns-server
[2] http://www.linuxjournal.com/content/photo-gallery-software

If network manager does not solve the problem, the first step should be to see which driver your wireless card needs. Do a search for your card on Google and in the Ubuntu Forums to find out which driver you need. Many of the drivers are already included in Ubuntu, but some newer drivers may not be present.

Next, you need to find out if the driver is loaded. As an example, if you have an Intel Centrino and it uses the ipw2200 driver, run this command:

sudo lsmod | grep ipw2200

Replace ipw2200 with the relevant driver for your card. If you get some lines returned, the driver is loaded and working. If nothing is returned, your card is either not supported or the driver is not included in Ubuntu. You should refer to the Ubuntu Forums for further support.

With the card identified, you now need to get connected. The easiest way to do this is to select System -> Administration -> Networking. Inside this tool you should see an icon for your wireless card. Select it and click the Properties button. Add the name of the wireless network and a password if applicable. If you are using a normal password such as s3cr3tpass, select Plain (ASCII) from the Key type box. If you are entering the long numeric password, use the Hexedecimal option. If you don’t have a password on your wireless network, leave the Key type and WEP key boxes empty.

If you are automatically assigned an IP address, use the Configuration box to select DHCP. Otherwise, select Static IP Address, and enter the details of your network in the boxes.
For more information, see the Ubuntu wiki.

Using WPA
To use WPA, you need a supported card. Such cards are listed on the WPA Supplicant Web site. Common drivers that support WPA include ipw2200, ipw2100, and madwifi.

To use WPA (Wi-Fi Protected Access) with wireless cards in Ubuntu, the wpasupplicant package must be installed. After installing it, edit /etc/wpa_supplicant.conf. Networks are configured by adding network blocks to the configuration file. Each network block can also be assigned a priority so if both networks are seen, the higher priority network is chosen. Examples for common network configurations can be found in /usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf.gz.

Some configurations require certificates that should be available from the network administrator. WPA Supplicant can also configure your wireless card to use unencrypted networks, as noted in the example file. After writing the file, edit /etc/default/wpasupplicant and change the ENABLED, DRIVER, and INTERFACE options. The DRIVER option should match the type of wireless device being used. Available drivers can be viewed by typing:

wpa_supplicant -help

To start the Supplicant run:

/etc/init.d/wpasupplicant start

Lastly, wpasupplicant should be added to STOP_SERVICES in /etc/default/ acpi-support to ensure it functions properly after a system suspend or hibernation.

To check if the connection is working, run:

sudo wpa_cli

This command gives information on the current connection along with scrolling logs to indicate the current status. By default wpa_cli must be run as root. Status will show what network the wireless card is currently connected to and parameters about the link. Scan causes the supplicant to look for a new access point while scan_results will display what access points are locally accessible to the machine. As soon as the supplicant authenticates, ifplugd should start the interface with ifup, and networking will be available shortly. If it seems that the supplicant is not working it may be that a different driver must be selected in the /etc/defaults/wpasupplicant configuration file. Also, some cards cannot operate in a mixed TKIP/CCMP (types of encryption) mode. If it appears the PTK listed in the log from wpa_cli is CCMP but that the GTK is TKIP, setting the pairwise and group entries of a network configuration block to TKIP may fix the issue.

By Benjamin Mako Hill, Jono Bacon, Ivan Krstic. David J. Murphy, Jonathan Jesse, Peter Savage, Corey Burger
This article is excerpted from the newly published book The Official Ubuntu Book . © Copyright Pearson Education. All rights reserved.