Mandriva Linux ID

VideoCache Installation

2009-05-30T12:24:00.000+07:00

Download :

http://cachevideos.com/download

for mandriva linux, choose rpm packet
http://cachevideos.com/sites/default/files/pub/videocache/videocache-1.9.1-1.noarch.rpm

Installation :

Videocache requires following packages to work.

Squid >= 2.6
Python >= 2.4
Python-urlgrabber (urlgrabber module of python)
Python-iniparse (iniparse module of python)
Apache (httpd) Web Server

You should have these packages installed and properly configured on your system. In case you don't have these packages installed check the respective links above.

on mandriva linux :

urpmi videocache-1.9.1-1.noarch.rpm

If the installation was successful, add the following lines to your squid.conf .

# --BEGIN-- videocache config for squid
url_rewrite_program /usr/bin/python /usr/share/videocache/videocache.py
url_rewrite_children 7
acl videocache_allow_url url_regex -i \.youtube\.com\/get_video\?
acl videocache_allow_url url_regex -i \.googlevideo\.com\/videoplayback \.googlevideo\.com\/videoplay \.googlevideo\.com\/get_video\?
acl videocache_allow_url url_regex -i \.google\.com\/videoplayback \.google\.com\/videoplay \.google\.com\/get_video\?
acl videocache_allow_url url_regex -i \.google\.[a-z][a-z]\/videoplayback \.google\.[a-z][a-z]\/videoplay \.google\.[a-z][a-z]\/get_video\?
acl videocache_allow_url url_regex -i (25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\/videoplayback\?
acl videocache_allow_url url_regex -i (25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\/videoplay\?
acl videocache_allow_url url_regex -i (25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\/get_video\?
acl videocache_allow_url url_regex -i proxy[a-z0-9\-][a-z0-9][a-z0-9][a-z0-9]?\.dailymotion\.com\/
acl videocache_allow_url url_regex -i vid\.akm\.dailymotion\.com\/
acl videocache_allow_url url_regex -i [a-z0-9][0-9a-z][0-9a-z]?[0-9a-z]?[0-9a-z]?\.xtube\.com\/(.*)flv
acl videocache_allow_url url_regex -i bitcast\.vimeo\.com\/vimeo\/videos\/
acl videocache_allow_url url_regex -i va\.wrzuta\.pl\/wa[0-9][0-9][0-9][0-9]?
acl videocache_allow_url url_regex -i \.files\.youporn\.com\/(.*)\/flv\/
acl videocache_allow_url url_regex -i \.msn\.com\.edgesuite\.net\/(.*)\.flv
acl videocache_allow_url url_regex -i media[a-z0-9]?[a-z0-9]?[a-z0-9]?\.tube8\.com\/ mobile[a-z0-9]?[a-z0-9]?[a-z0-9]?\.tube8\.com\/
acl videocache_allow_url url_regex -i \.mais\.uol\.com\.br\/(.*)\.flv
acl videocache_allow_url url_regex -i \.video[a-z0-9]?[a-z0-9]?\.blip\.tv\/(.*)\.(flv|avi|mov|mp3|m4v|mp4|wmv|rm|ram)
acl videocache_allow_url url_regex -i video\.break\.com\/(.*)\.(flv|mp4)
acl videocache_allow_dom dstdomain .mccont.com dl.redtube.com .cdn.dailymotion.com
acl videocache_deny_url url_regex -i http:\/\/[a-z][a-z]\.youtube\.com http:\/\/www\.youtube\.com
url_rewrite_access deny videocache_deny_url
url_rewrite_access allow videocache_allow_url
url_rewrite_access allow videocache_allow_dom
redirector_bypass on
# --END-- videocache config for squid

Configuring Videocache is very easy. The configuration file for videocache is normally located at /etc/videocache.conf . Below is a brief explanation of different options used in videocache.conf .

Warning: If you change options in this file, please use the update script to update the videocache installation and reload apache web server and restart squid proxy server.

Click on the option name to get the details.

enable_video_cache

cache_host

proxy

proxy_username

proxy_password

hit_threshold

base_dir

disk_avail_threshold

temp_dir

max_parallel_downloads

enable_videocache_cleaner

video_lifetime

logdir

max_logfile_size

max_logfile_backups

rpc_host

rpc_port

enable_youtube_cache

youtube_cache_dir

max_youtube_video_size

min_youtube_video_size

All other options are similar to the above explained options.

CentOS : rpm based Linux Distro For Server

2009-05-25T13:40:00.000+07:00

CentOS 5 mini installation :

follow these step by step

Mandriva Spring 2009.1 : Simple Web Server

2009-05-13T12:35:00.000+07:00

bikin webserver dengan cara mudah di mandriva spring 2009.1 dan simple :)
bagi yang belum punya cd instalasi mandriva spring 2009.1 isa download di :

http://kambing.ui.edu/iso/mandriva/2009.1/mandriva-linux-free-2009.1-dual.iso

soale aq juga pake itu. kenapa kok pake iso file diatas ? simple aja. aq butuh
yang simple-simple, coz untuk aplikasi server langsung cocok, apalagi aplikasi
dekstop nya. cool abizz....
trus kenapa juga pake yang dual arch ? simple, mo pake cpu yang udah pensiun or
mo pake cpu yang support 64bit langsung isa. enak kan ?? :D

ok langsung aja yow... untuk tahapan instalasi aq lewatin aja, coz instalasi mandriva
linux simple banget.

o iya, file iso mandriva diatas akan menginstall desktop lxde yang ringan sebagai
default desktop nya. jangan kuatir dengan lxde, lxde akan lebih mudah dibanding kan
icewm :D

waduh... ni sebenere mo ng-review mandriva apa cara bikin webserver nya ya ? :p

pertama-tama, buka konsole, masuk menggunakan root dengan perintah 'su'.
setelah itu tambahkan repository untuk mandriva, disini aq pake yang server di indonesia
jalankan perintah ini :

urpmi.addmedia arsip_main_rilis http://telkom.arsip.or.id/mandrivalinux/official/2009.1/i586/media/main/release/

urpmi.addmedia arsip_main_backports http://telkom.arsip.or.id/mandrivalinux/official/2009.1/i586/media/main/backports/

urpmi.addmedia arsip_main_updates http://telkom.arsip.or.id/mandrivalinux/official/2009.1/i586/media/main/updates/

diatas untuk menambahkan repository main nya, sekarang untuk repo contrib nya

urpmi.addmedia arsip_contrib_rilis http://telkom.arsip.or.id/mandrivalinux/official/2009.1/i586/media/contrib/release/

urpmi.addmedia arsip_contrib_backports http://telkom.arsip.or.id/mandrivalinux/official/2009.1/i586/media/contrib/backports/

urpmi.addmedia arsip_contrib_updates http://telkom.arsip.or.id/mandrivalinux/official/2009.1/i586/media/contrib/updates/

ok, penambahan repositori instalasi untuk mandriva spring 2009.1 kita udah selesai. sekarang lanjut ke proses berikutnya. install webserver + database (apache+php+mysql+phpmyadmin).
jalankan perintah ini :

urpmi task-lamp

dengan perintah diatas, semua kebutuhan untuk lamp (linux,apache,mysql,php) langsung terpenuhi.
setelah proses diatas selesai, hal yang perlu di perhatikan adalah password untuk mysql / database
server nya. untuk menjalankan mysql server terlebih dulu silahkan ganti or buat password root untuk mysql server nya, dengan perintah seperti ini :

/usr/bin/mysqladmin -u root password 'root'

perintah diatas akan mengeset mysql server kita dengan username root dan password root.

ok sudah selesai semuanya. sekarang tinggal test drive :D

jalankan webserver, dengan perintah :

/etc/init.d/httpd start

atau

service httpd start

kemudian jalakan database server nya, disini mysqld dengan perintah

/etc/init.d/mysqld start

atau

service mysqld start

tes dengan buka browser (firefox) dan akses ke alamat http://localhost.

done...

nb : untuk semua dokumen / berkas web di simpan di /var/www/html

Tips Server : Portsentry

2009-04-12T14:44:00.000+07:00

Portsentry adalah aplikasi yang digunakan untuk mendeteksi dan merespon semua kegiatan yang berhubungan dengan 'port scanning' pada sebuah sistem.

install portsentry

centos
yum install portsentry
ato
rpm -ivh portsentry-1.1-11.fr.i386.rpm

mandriva
urpmi portsentry

dengan konfigurasi default portsentry langsung bisa digunakan. untuk file-file konfigurasi terletak di direktori :

/etc/portsentry/

dengan isi file sbb :

portsentry.blocked.atcp
portsentry.blocked.audp
portsentry.conf
portsentry.history
portsentry.ignore
portsentry.modes

untuk konfigurasi utama, silahkan di edit file /etc/portsentry/portsentry.conf , disini yang diperlu di perhatikan adalah di bagian 'kerjaan' portsentry setelah terjadi ato mendeteksi adanya 'port scanning'. di linux mandriva defaultnya adalah menge-blok usaha 'port scanning' tersebut menggunakan 'iptables', seperti terlihat di file portsentry.conf.

###################
# Dropping Routes:#
###################
# This command is used to drop the route or add the host into
# a local filter table.
#
# The gateway (333.444.555.666) should ideally be a dead host on
# the *local* subnet. On some hosts you can also point this at
# localhost (127.0.0.1) and get the same effect. NOTE THAT
# 333.444.555.66 WILL *NOT* WORK. YOU NEED TO CHANGE IT!!
#
# ALL KILL ROUTE OPTIONS ARE COMMENTED OUT INITIALLY. Make sure you
# uncomment the correct line for your OS. If you OS is not listed
# here and you have a route drop command that works then please
# mail it to me so I can include it. ONLY ONE KILL_ROUTE OPTION
# CAN BE USED AT A TIME SO DON'T UNCOMMENT MULTIPLE LINES.
#
# NOTE: The route commands are the least optimal way of blocking
# and do not provide complete protection against UDP attacks and
# will still generate alarms for both UDP and stealth scans. I
# always recommend you use a packet filter because they are made
# for this purpose.
#

...
# iptables support for Linux
KILL_ROUTE="/sbin/iptables -I INPUT -s $TARGET$ -j DROP"
...

dimana opsi diatas adalah default, dan bisa di ubah untuk menyesuaikan situasi dan kondisi serta kebutuhan.
semisal akan memerintahkan portsentry agar memasukkan usaha ip_orang 'port scanning' ke dalam file /etc/hosts.deny, cukup dengan mengkombinasikan dengan opsi yang ada di bagian tcp wrappers (service). liat contoh :

###############
# TCP Wrappers#
###############
# This text will be dropped into the hosts.deny file for wrappers
# to use. There are two formats for TCP wrappers:
#
# Format One: Old Style - The default when extended host processing
# options are not enabled.
#

KILL_HOSTS_DENY="ALL: $TARGET$"
#hilangkan tanda #

# Format Two: New Style - The format used when extended option
# processing is enabled. You can drop in extended processing
# options, but be sure you escape all '%' symbols with a backslash
# to prevent problems writing out (i.e. \%c \%h )
#
#KILL_HOSTS_DENY="ALL: $TARGET$ : DENY"

dan jika ingin memberikan alert tentang kejadian 'port scanning' tsb, misalnya menggunakan email, bisa langsung menggunakan konfigurasi 'External Command' :

###################
# External Command#
###################
# This is a command that is run when a host connects, it can be whatever
# you want it to be (pager, etc.). This command is executed before the
# route is dropped or after depending on the KILL_RUN_CMD_FIRST option below
#
#
# I NEVER RECOMMEND YOU PUT IN RETALIATORY ACTIONS AGAINST THE HOST SCANNING
# YOU!
...
KILL_RUN_CMD="/bin/mail -s 'Portscan from $TARGET$ on port $PORT$' admin@server.org < /dev/null"

...

mudah bukan mengkonfigurasi portsentry ? :D
dan yang perlu di perhatikan lagi adalah file /etc/portsentry/portsentry.ignore

# Put hosts in here you never want blocked. This includes the IP addresses
# of all local interfaces on the protected host (i.e virtual host, mult-home)
# Keep 127.0.0.1 and 0.0.0.0 to keep people from playing games.
#
# PortSentry can support full netmasks for networks as well. Format is:
#
# /
#
# Example:
#
# 192.168.2.0/24
# 192.168.0.0/16
# 192.168.2.1/32
# Etc.
#
# If you don't supply a netmask it is assumed to be 32 bits.
#
#

beberapa fitur dari portsentry (diambil dari tulisannya pak onno w purbo)

•Mendeteksi adanya Stealth port scan untuk semua platform Unix. Stealth port scan adalah teknik port scan yang tersamar / tersembunyi, biasanya sukar di deteksi oleh sistem operasi.
•PortSentry akan mendeteksi berbagai teknik scan seperti SYN/half-open, FIN, NULL dan X-MAS. Untuk mengetahui lebih jelas tentang berbagai teknik ini ada baiknya untuk membaca-baca manual dari software nmap yang merupakan salah satu software portscan terbaik yang ada.
•PortSentry akan bereaksi terhadap usaha port scan dari lawan dengan cara membolkir penyerang secara real-time dari usaha auto-scanner, probe penyelidik maupun serangan terhadap sistem.
•PortSentry akan melaporkan semua kejanggalan & pelanggaran kepada software daemon syslog lokal maupun remote yang berisi nama sistem, waktu serangan, IP penyerang maupun nomor port TCP atau UDP di mana serangan di lakukan. Jika PortSentry didampingkan dengan LogSentry, dia akan memberikan berita kepada administrator melalui e-mail.
•Fitur cantik dari PortSentry adalah pada saat terdeteksi sebuah scan, sistem anda tiba-tiba menghilang dari hadapan si penyerang. Fitur ini betul-betul membuat penyerang tidak berkutik.
•PortSentry selalu mengingat alamat IP penyerang, jika ada serangan Port Scan yang sifatnya random PortSentry akan bereaksi.

Mandriva 2009.0 : Add Repo dengan rpmdrake

2009-04-11T11:58:00.000+07:00

ok langsung aja. kita akan menambahkan repo untuk mandriva 2009.0 kita dengan repo yang tersedia di http://www.arsip.or.id. untuk link lengkapnya dari arsip.or.id adalah ini :

http://arsip.or.id/mandrakelinux/official/2009.0/i586/

disini repo tersebut terdiri dari main repo dan contrib repo. dan masing-masing repo terdapat repo bakcports, release, testing dan updates.

jadi untuk menambahkan semua repo itu (main dan contrib repo), dengan menambahkan link-link langsung ini melalui rpmdrake ataupun manual dengan perintah urpmi.addmedia. daftar linknya

main repo

backports : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/main/backports/
releease : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/main/release/
testing : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/main/testing/
updates : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/main/updates/

dan
contrib repo nya

backports : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/contrib/backports/
releease : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/contrib/release/
testing : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/contrib/testing/
updates : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/contrib/updates/

kemudian setelah kita tau link repo buat mandrivanya, sekarang kita masukkan ke database sistem mandriva kita. caranya :

1. klik menu, dan pilih Install & Remove Software

2. masukkan password root, setelah halaman rpmdrake muncul. langsung pilih menu Option dan pilih Media manager. seperti gambar di bawah ini:

3. muncul halaman configure media, seperti gambar di bawah ini :

kemudian tekan tombol Ctrl dengan diikuti huruf A ( Ctrl+A ), untuk menambahkan repo diatas. seperti gambar di bawah ini :

kemudian masukkan parameternya yang seperti diatas. contoh untuk medium name main repo, isikan ;

Medium Name : arsip_main_release
URL : http://arsip.or.id/mandrakelinux/official/2009.0/i586/media/main/release/

kemudian tekan OK jika sudah selesai, dan lanjutkan dengan repo lainnya (contrib repo).

Jika tidak ada error/kesalahan. sistem mandriva kita sudah bisa digunakan untuk menginstall dan meng-update software dari repo arsip.or.id

note :

http://bayuart.wordpress.com
http://bayu.blitar.org / http://blitar.org
http://blitar.linux.or.id / http://linux.or.id
http://mandriva.linux.or.id

Install Dansguardian + Transparent proxy

2008-08-17T13:31:00.000+07:00

[root@javanet loadbalancing]# urpmi dansguardian
In order to satisfy the 'sendmail-command' dependency, one of the following packages is needed:
1- postfix-2.5.1-2mdv2008.1.i586: Postfix Mail Transport Agent (to install)
2- sendmail-8.14.2-3mdv2008.1.i586: A widely used Mail Transport Agent (MTA) (to install)
3- masqmail-0.2.18-8mdv2008.1.i586: Offline Mail Transfert Agent (to install)
4- exim-4.63-14mdv2008.1.i586: The exim mail transfer agent (to install)
5- ssmtp-2.61-1mdv2008.1.i586: A minimal mail-transfer agent which forwards mail to an SMTP server (to install)
6- msmtp-1.4.13-1mdv2008.0.i586: An SMTP client (to install)
7- mini_sendmail-1.3.5-5mdv2008.1.i586: Accept email on behalf of real sendmail (to install)
8- nbsmtp-1.00-2mdv2008.1.i586: nbSMTP: no-brainer SMTP (to install)
What is your choice? (1-8)

To satisfy dependencies, the following packages are going to be installed:
Package Version Release Arch
(medium "Mandriva Linux - 2008.1 (Free) - i586 CD1")
ed 0.9 1mdv2008.1 i586
libclamav3 0.92.1 2mdv2008.1 i586
libpostfix1 2.5.1 2mdv2008.1 i586
(medium "Main")
dansguardian 2.9.9.2 4mdv2008.1 i586
libgmp3 4.2.2 1mdv2008.1 i586
postfix 2.5.1 2mdv2008.1 i586
8.2MB of additional disk space will be used.
2.9MB of packages will be retrieved.
Proceed with the installation of the 6 packages? (Y/n)
http://ftp.kddlabs.co.jp/Linux/distributions/Mandrake/official/2008.1/i586/media/main/release/dansguardian-2.9.9.2-4mdv2008.1.i586.rpm
3% of 515k completed, ETA = 0:01:51, speed = 9065
Proceed with the installation of the 6 packages? (Y/n)
http://ftp.kddlabs.co.jp/Linux/distributions/Mandrake/official/2008.1/i586/media/main/release/dansguardian-2.9.9.2-4mdv2008.1.i586.rpm
installing //var/ftp/pub/Mandrivalinux/media/main/libpostfix1-2.5.1-2mdv2008.1.i586.rpm
//var/ftp/pub/Mandrivalinux/media/main/libclamav3-0.92.1-2mdv2008.1.i586.rpm
//var/ftp/pub/Mandrivalinux/media/main/ed-0.9-1mdv2008.1.i586.rpm
//var/ftp/pub/Mandrivalinux/media/main/postfix-2.5.1-2mdv2008.1.i586.rpm
//var/ftp/pub/Mandrivalinux/media/main/libgmp3-4.2.2-1mdv2008.1.i586.rpm
/var/cache/urpmi/rpms/dansguardian-2.9.9.2-4mdv2008.1.i586.rpm
Preparing... ###########################################################################################
1/6: libgmp3 ###########################################################################################
2/6: libclamav3 ###########################################################################################
3/6: ed ###########################################################################################
4/6: libpostfix1 ###########################################################################################
5/6: postfix ###########################################################################################
Shutting down kernel logger: [ OK ]
Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
6/6: dansguardian ###########################################################################################
----------------------------------------------------------------------
More information on package dansguardian-2.9.9.2-4mdv2008.1.i586
Make sure to change your /etc/dansguardian/dansguardian.conf to reflect your own settings.
Special attention must be given to the port that the proxy server is listening to,
the port that dansguardian will listen to and to the web url to the dansguardian.pl cgi-script.

Author: Daniel Barron
daniel@jadeb.com
----------------------------------------------------------------------
[root@javanet loadbalancing]#

then run dansguardian

[root@javanet loadbalancing]# service dansguardian start
Starting dansguardian: [ OK ]
[root@javanet loadbalancing]#

On Mandriva

hping

2008-08-03T09:03:00.000+07:00

hping is a command-line oriented TCP/IP packet assembler/analyzer. The interface is inspired to the ping(8) unix command, but hping isn't only able to send ICMP echo requests. It supports TCP, UDP, ICMP and RAW-IP protocols, has a traceroute mode, the ability to send files between a covered channel, and many other features.

While hping was mainly used as a security tool in the past, it can be used in many ways by people that don't care about security to test networks and hosts. A subset of the stuff you can do using hping:

Firewall testing
Advanced port scanning
Network testing, using different protocols, TOS, fragmentation
Manual path MTU discovery
Advanced traceroute, under all the supported protocols
Remote OS fingerprinting
Remote uptime guessing
TCP/IP stacks auditing
hping can also be useful to students that are learning TCP/IP.

Hping works on the following unix-like systems: Linux, FreeBSD, NetBSD, OpenBSD, Solaris, MacOs X, Windows.

[root@kopegtel box]# hping --help
usage: hping host [options]
-h --help show this help
-v --version show version
-c --count packet count
-i --interval wait (uX for X microseconds, for example -i u1000)
--fast alias for -i u10000 (10 packets for second)
-n --numeric numeric output
-q --quiet quiet
-I --interface interface name (otherwise default routing interface)
-V --verbose verbose mode
-D --debug debugging info
-z --bind bind ctrl+z to ttl (default to dst port)
-Z --unbind unbind ctrl+z
Mode
default mode TCP
-0 --rawip RAW IP mode
-1 --icmp ICMP mode
-2 --udp UDP mode
-8 --scan SCAN mode.
Example: hping --scan 1-30,70-90 -S www.target.host
-9 --listen listen mode
IP
-a --spoof spoof source address
--rand-dest random destionation address mode. see the man.
--rand-source random source address mode. see the man.
-t --ttl ttl (default 64)
-N --id id (default random)
-W --winid use win* id byte ordering
-r --rel relativize id field (to estimate host traffic)
-f --frag split packets in more frag. (may pass weak acl)
-x --morefrag set more fragments flag
-y --dontfrag set dont fragment flag
-g --fragoff set the fragment offset
-m --mtu set virtual mtu, implies --frag if packet size > mtu
-o --tos type of service (default 0x00), try --tos help
-G --rroute includes RECORD_ROUTE option and display the route buffer
--lsrr loose source routing and record route
--ssrr strict source routing and record route
-H --ipproto set the IP protocol field, only in RAW IP mode
ICMP
-C --icmptype icmp type (default echo request)
-K --icmpcode icmp code (default 0)
--force-icmp send all icmp types (default send only supported types)
--icmp-gw set gateway address for ICMP redirect (default 0.0.0.0)
--icmp-ts Alias for --icmp --icmptype 13 (ICMP timestamp)
--icmp-addr Alias for --icmp --icmptype 17 (ICMP address subnet mask)
--icmp-help display help for others icmp options
UDP/TCP
-s --baseport base source port (default random)
-p --destport [+][+] destination port(default 0) ctrl+z inc/dec
-k --keep keep still source port
-w --win winsize (default 64)
-O --tcpoff set fake tcp data offset (instead of tcphdrlen / 4)
-Q --seqnum shows only tcp sequence number
-b --badcksum (try to) send packets with a bad IP checksum
many systems will fix the IP checksum sending the packet
so you'll get bad UDP/TCP checksum instead.
-M --setseq set TCP sequence number
-L --setack set TCP ack
-F --fin set FIN flag
-S --syn set SYN flag
-R --rst set RST flag
-P --push set PUSH flag
-A --ack set ACK flag
-U --urg set URG flag
-X --xmas set X unused flag (0x40)
-Y --ymas set Y unused flag (0x80)
--tcpexitcode use last tcp->th_flags as exit code
--tcp-timestamp enable the TCP timestamp option to guess the HZ/uptime
Common
-d --data data size (default is 0)
-E --file data from file
-e --sign add 'signature'
-j --dump dump packets in hex
-J --print dump printable characters
-B --safe enable 'safe' protocol
-u --end tell you when --file reached EOF and prevent rewind
-T --traceroute traceroute mode (implies --bind and --ttl 1)
--tr-stop Exit when receive the first not ICMP in traceroute mode
--tr-keep-ttl Keep the source TTL fixed, useful to monitor just one hop
--tr-no-rtt Don't calculate/show RTT information in traceroute mode
ARS packet description (new, unstable)
--apd-send Send the packet described with APD (see docs/APD.txt)
[root@kopegtel box]#

Mode Wireless

2008-07-17T16:02:00.000+07:00

	AP Mode : The AP is the central hub for all your wireless devices.
	Bridge Mode : To connect 2 LANs together wirelessly.
	Client Mode : Turn the AP into a wireless card so you can connect with remote AP.
	WDS Repeater : To increase the wireless coverage of a WDS enabled AP/Router
	Universal Repeater : AirLive's unique universal repeater function let the AP extend the coverage of your AP/Router, even if your AP/Router doesn't have WDS function!
	WISP Mode : The WISP mode is similar to Client Mode. IP sharing function is added so you can share the WISP connection with many PCs.
	WISP+Universal Repeater : The WISP+Universal Repeater mode let you share WISP connection on both wireless and wired side.

Application Diagram

TP-Link TL-WN322G On Mandriva Spring

2008-07-14T09:52:00.000+07:00

Install and Configure USB WiFi TP-Link TL-WN322G in
Mandriva 2008.1 Spring Free Edition

Prepared:
-Mandriva 2008.1 Spring Free Edition
-USB WiFi TP-LINK TL-WN322G

Step by Step :
-PLUG USB to USB port
-Check with dmesg command, like this

-Run MCC / Mandriva Control Center. Input Password root

-From MCC, choose Hardware > Browse and configure hardware
-Auto hardware is running, then driver installation begin automatically
-Result of hardware detection

-Configure USB Wifi, from MCC choose Network & Internet > Set up a new network interface ... > Choose connection >

Mandriva Minimalize

2008-07-01T10:50:00.000+07:00

Howto change Mandriva Spring to minimalize

for Window Manager (icewm or something else, not xfce). im using :
urpmi fluxbox
or
urpmi blackbox

for graphic viewer (not using gqview)
urpmi gthumb

for text editing (not using mousepad)
urpmi leafpad

for file manager and desktop icon (not using thunar)
urpmi pcmanfm

for spreadsheet and word editor
urpmi gnumeric
urpmi abiword

for graphic editing
urpmi gimp2

for tweak
urpmi powertweak
urpmi powertweak-gtk

for music player
urpmi audacious

for video player
urpmi mplayer mplayer-gui

for monitoring system
urpmi torsmo
urpmi htop

for browser (althought it bloated, but firefox is smooth)
urpmi mozilla-firefox

thats i call minimalize Mandriva Spring :)

Mandriva Spring with Moto Rokr E2

2008-06-27T08:45:00.000+07:00

Using Motorola Rokr E2 as Modem to connect Internet with Mandriva Spring 2008.1
Motorola Rokr E2
-Goto Main Menu
-Settings
-Connections
-USB Settings
-Choose Modem

On Mandriva Spring 2008.1 with wvdial
Install wvdial first

[root@box bayu]# urpmi wvdial
To satisfy dependencies, the following packages are going to be installed:
Package Version Release Arch
(medium "main_speedy")
libwvstreams4.4 4.4 3mdv2008.1 i586
libxplc0 0.3.13 3mdv2008.1 i586
wvdial 1.60 1mdv2008.1 i586
1.9MB of additional disk space will be used.
729KB of packages will be retrieved.
Proceed with the installation of the 3 packages? (Y/n)

http://opensource.telkomspeedy.com/repo/mandriva/official/2008.1/i586/media/main/release/libxplc0-0.3.13-3mdv2008.1.i586.rpm
http://opensource.telkomspeedy.com/repo/mandriva/official/2008.1/i586/media/main/release/wvdial-1.60-1mdv2008.1.i586.rpm
http://opensource.telkomspeedy.com/repo/mandriva/official/2008.1/i586/media/main/release/libwvstreams4.4-4.4-3mdv2008.1.i586.rpm
installing libxplc0-0.3.13-3mdv2008.1.i586.rpm wvdial-1.60-1mdv2008.1.i586.rpm libwvstreams4.4-4.4-3mdv2008.1.i586.rpm from /var/cache/urpmi/rpms
Preparing... ##########################################################################################
1/3: libxplc0 ##########################################################################################
2/3: libwvstreams4.4 ##########################################################################################
3/3: wvdial ##########################################################################################
[root@box bayu]#

then run

[root@box bayu]# wvdialconf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

Modem Port Scan<*1>: S0 S1 S2 S3
WvModem<*1>: Cannot get information for serial port.
ttyACM0<*1>: ATQ0 V1 E1 -- OK
ttyACM0<*1>: ATQ0 V1 E1 Z -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyACM0<*1>: Modem Identifier: ATI -- ERROR
ttyACM0<*1>: Speed 4800: AT -- OK
ttyACM0<*1>: Speed 9600: AT -- OK
ttyACM0<*1>: Speed 19200: AT -- OK
ttyACM0<*1>: Speed 38400: AT -- OK
ttyACM0<*1>: Speed 57600: AT -- OK
ttyACM0<*1>: Speed 115200: AT -- OK
ttyACM0<*1>: Speed 230400: AT -- OK
ttyACM0<*1>: Speed 460800: AT -- OK
ttyACM0<*1>: Max speed is 460800; that should be safe.
ttyACM0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK

Found an USB modem on /dev/ttyACM0.
/etc/wvdial.conf: Can't open '/etc/wvdial.conf' for reading: No such file or directory
/etc/wvdial.conf: ...starting with blank configuration.
Modem configuration written to /etc/wvdial.conf.
ttyACM0: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
[root@box bayu]#

Edit config file /etc/wvdial, this for my provider

#telkomsel
[Dialer telkomsel]
Modem = /dev/ttyACM0
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = at+cgdcont=1,”ip”,”telkomsel”
Modem Type = USB Modem
ISDN = 0
Phone = *99***1#
Username = “wap”
Password = “wap123″

#three
[Dialer three]
Modem = /dev/ttyACM0
Baud = 460800
Init1 =ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = at+cgdcont=1,”ip”,”3gprs”
Modem Type = USB Modem
ISDN = 0
Phone = *99***1#
Username = “3gprs”
Password = “3gprs”

#indosat
[Dialer indosat]
Modem = /dev/ttyACM0
Baud = 460800
Init1 =ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = at+cgdcont=1,”ip”,”www.indosat-m3.net”
Modem Type = USB Modem
ISDN = 0
Phone = *99***1#
Username = “gprs”
Password = “im3”

# xl
[Dialer xl]
Modem = /dev/ttyACM0
Baud = 460800
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = at+cgdcont=1,”ip”,”www.xlgprs.net”
Modem Type = USB Modem
ISDN = 0
Phone = *99***1#
Username = “xlgprs”
Password = “proxl”

Setting for GPRS Access Point.
telkomsel->telkomsel
three->3gprs
indosat->www.indosat-m3.net
xl->www.xlgprs.net

OK, let's do it

$ wvdial

Eg :
$ wvdial telkomsel
$ wvdial three
$ wvdial indosat
$ wvdial xl

end

Mandriva : Install LAMP / XAMP

2008-06-26T11:58:00.000+07:00

Simple way to install Webserver with PHP, MySQL, and PERL in Mandriva Spring

Connect to repo from http://easyurpmi.zarb.org, then
Install LAMP (Linux Apache MySQL PHP) with command

urpmi lamp
The following packages contain lamp:
task-lamp
task-lamp-perl
task-lamp-php
task-lamp-python

or

urpmi task-lamp (for complete LAMP in mandriva spring)

iptables : DNAT target

2008-06-19T14:54:00.000+07:00

The DNAT target is used to do Destination Network Address Translation, which means that it is used to rewrite the Destination IP address of a packet. If a packet is matched, and this is the target of the rule, the packet, and all subsequent packets in the same stream will be translated, and then routed on to the correct device, host or network. This target can be extremely useful, for example,when you have a host running your web server inside a LAN, but no real IP to give it that will work on the Internet. You could then tell the firewall to forward all packets going to its own HTTP port, on to the real web server within the LAN. We may also specify a whole range of destination IP addresses, and the DNAT mechanism will choose the destination IP address at random for each stream. Hence, we will be able to deal with a kind of load balancing by doing this.

Note that the DNAT target is only available within the PREROUTING and OUTPUT chains in the nat table, and any of the chains called upon from any of those listed chains. Note that chains containing DNAT targets may not be used from any other chains, such as the POSTROUTING chain.

Table 11-5. DNAT target options

Option	--to-destination
Example	iptables -t nat -A PREROUTING -p tcp -d 15.45.23.67 --dport 80 -j DNAT --to-destination 192.168.1.1-192.168.1.10
Explanation	The --to-destination option tells the DNAT mechanism which Destination IP to set in the IP header, and where to send packets that are matched. The above example would send on all packets destined for IP address 15.45.23.67 to a range of LAN IP's, namely 192.168.1.1 through 10. Note, as described previously, that a single stream will always use the same host, and that each stream will randomly be given an IP address that it will always be Destined for, within that stream. We could also have specified only one IP address, in which case we would always be connected to the same host. Also note that we may add a port or port range to which the traffic would be redirected to. This is done by adding, for example, an :80 statement to the IP addresses to which we want to DNAT the packets. A rule could then look like --to-destination 192.168.1.1:80 for example, or like --to-destination 192.168.1.1:80-100 if we wanted to specify a port range. As you can see, the syntax is pretty much the same for the DNAT target, as for the SNAT target even though they do two totally different things. Do note that port specifications are only valid for rules that specify the TCP or UDP protocols with the --protocol option.

Since DNAT requires quite a lot of work to work properly, I have decided to add a larger explanation on how to work with it. Let's take a brief example on how things would be done normally. We want to publish our website via our Internet connection. We only have one IP address, and the HTTP server is located on our internal network. Our firewall has the external IP address $INET_IP, and our HTTP server has the internal IP address $HTTP_IP and finally the firewall has the internal IP address $LAN_IP. The first thing to do is to add the following simple rule to the PREROUTING chain in the nat table:

iptables -t nat -A PREROUTING --dst $INET_IP -p tcp --dport 80 -j DNAT \
--to-destination $HTTP_IP

Now, all packets from the Internet going to port 80 on our firewall are redirected (or DNAT'ed) to our internal HTTP server. If you test this from the Internet, everything should work just perfect. So, what happens if you try connecting from a host on the same local network as the HTTP server? It will simply not work. This is a problem with routing really. We start out by dissecting what happens in a normal case. The external box has IP address $EXT_BOX, to maintain readability.

Packet leaves the connecting host going to $INET_IP and source $EXT_BOX.
Packet reaches the firewall.
Firewall DNAT's the packet and runs the packet through all different chains etcetera.
Packet leaves the firewall and travels to the $HTTP_IP.
Packet reaches the HTTP server, and the HTTP box replies back through the firewall, if that is the box that the routing database has entered as the gateway for $EXT_BOX. Normally, this would be the default gateway of the HTTP server.
Firewall Un-DNAT's the packet again, so the packet looks as if it was replied to from the firewall itself.
Reply packet travels as usual back to the client $EXT_BOX.

Now, we will consider what happens if the packet was instead generated by a client on the same network as the HTTP server itself. The client has the IP address $LAN_BOX, while the rest of the machines maintain the same settings.

Packet leaves $LAN_BOX to $INET_IP.
The packet reaches the firewall.
The packet gets DNAT'ed, and all other required actions are taken, however, the packet is not SNAT'ed, so the same source IP address is used on the packet.
The packet leaves the firewall and reaches the HTTP server.
The HTTP server tries to respond to the packet, and sees in the routing databases that the packet came from a local box on the same network, and hence tries to send the packet directly to the original source IP address (which now becomes the destination IP address).
The packet reaches the client, and the client gets confused since the return packet does not come from the host that it sent the original request to. Hence, the client drops the reply packet, and waits for the "real" reply.

The simple solution to this problem is to SNAT all packets entering the firewall and leaving for a host or IP that we know we do DNAT to. For example, consider the above rule. We SNAT the packets entering our firewall that are destined for $HTTP_IP port 80 so that they look as if they came from $LAN_IP. This will force the HTTP server to send the packets back to our firewall, which Un-DNAT's the packets and sends them on to the client. The rule would look something like this:

iptables -t nat -A POSTROUTING -p tcp --dst $HTTP_IP --dport 80 -j SNAT \
--to-source $LAN_IP

Remember that the POSTROUTING chain is processed last of the chains, and hence the packet will already be DNAT'ed once it reaches that specific chain. This is the reason that we match the packets based on the internal address.

This last rule will seriously harm your logging, so it is really advisable not to use this method, but the whole example is still a valid one. What will happen is this, packet comes from the Internet, gets SNAT'ed and DNAT'ed, and finally hits the HTTP server (for example). The HTTP server now only sees the request as if it was coming from the firewall, and hence logs all requests from the internet as if they came from the firewall.

This can also have even more severe implications. Take an SMTP server on the LAN, that allows requests from the internal network, and you have your firewall set up to forward SMTP traffic to it. You have now effectively created an open relay SMTP server, with horrenduously bad logging!

One solution to this problem is to simply make the SNAT rule even more specific in the match part, and to only work on packets that come in from our LAN interface. In other words, add a --src $LAN_IP_RANGE to the whole command as well. This will make the rule only work on streams that come in from the LAN, and hence will not affect the Source IP, so the logs will look correct, except for streams coming from our LAN.

You will, in other words, be better off solving these problems by either setting up a separate DNS server for your LAN, or to actually set up a separate DMZ, the latter being preferred if you have the money.

You think this should be enough by now, and it really is, unless considering one final aspect to this whole scenario. What if the firewall itself tries to access the HTTP server, where will it go? As it looks now, it will unfortunately try to get to its own HTTP server, and not the server residing on $HTTP_IP. To get around this, we need to add a DNAT rule in the OUTPUT chain as well. Following the above example, this should look something like the following:

iptables -t nat -A OUTPUT --dst $INET_IP -p tcp --dport 80 -j DNAT \
--to-destination $HTTP_IP

Adding this final rule should get everything up and running. All separate networks that do not sit on the same net as the HTTP server will run smoothly, all hosts on the same network as the HTTP server will be able to connect and finally, the firewall will be able to do proper connections as well. Now everything works and no problems should arise.

Everyone should realize that these rules only affect how the packet is DNAT'ed and SNAT'ed properly. In addition to these rules, you may also need extra rules in the filter table (FORWARD chain) to allow the packets to traverse through those chains as well. Don't forget that all packets have already gone through the PREROUTING chain, and should hence have their destination addresses rewritten already by DNAT.

Works under Linux kernel 2.3, 2.4, 2.5 and 2.6.

Speeding up Linux Using hdparm

2008-06-18T12:28:00.000+07:00

by Rob Flickenger
06/29/2000

Are you running an Intel Linux system with at least one (E)IDE hard drive?

Wouldn't it be neat if there were a magical command to instantly double the I/O performance of your disks? Or, in some cases, show 6 to 10 times your existing throughput?

Did you ever just wonder how to tell what kind of performance you're getting on your "tricked-out" Linux box?

Don't overlook hdparm(8). If you've never heard of it, don't worry. Most people I've talked to haven't either. But if you're running an IDE/Linux system (as many folks are,) you'll wonder how you ever got this far without it. I know I did.

What's the big deal?

So, you've got your brand-new UltraATA/66 EIDE drive with a screaming brand-new controller chipset that supports multiple PIO modes and DMA and the leather seat option and extra chrome... But is your system actually taking advantage of these snazzy features? The hdparm(8) command will not only tell you how your drives are performing, but will let you tweak them out to your heart's content.

Now before you get too excited, it is worth pointing out that under some circumstances, these commands CAN CAUSE UNEXPECTED DATA CORRUPTION! Use them at your own risk! At the very least, back up your box and bring it down to single-user mode before proceeding.

With the usual disclaimer out of the way, I'd like to point out that if you are using current hardware (i.e. your drive AND controller AND motherboard were manufactured in the last two or three years), you are at considerably lower risk. I've used these commands on several boxes with various hardware configurations, and the worst I've seen happen is the occasional hang, with no data problems on reboot. And no matter how much you might whine at me and the world in general for your personal misfortune, we all know who is ultimately responsible for the well-being of YOUR box: YOU ARE. Caveat Fair Reader.

Now, then. If I haven't scared you away yet, try this (as root, preferably in single-user mode):

hdparm -Tt /dev/hda

You'll see something like:

/dev/hda:
Timing buffer-cache reads:   128 MB in  1.34 seconds =95.52 MB/sec
Timing buffered disk reads:  64 MB in 17.86 seconds = 3.58 MB/sec

What does this tell us? The -T means to test the cache system (i.e., the memory, CPU, and buffer cache). The -t means to report stats on the disk in question, reading data not in the cache. The two together, run a couple of times in a row in single-user mode, will give you an idea of the performance of your disk I/O system. (These are actual numbers from a PII/350 / 128M Ram / newish EIDE HD; your numbers will vary.)

But even with varying numbers, 3.58 MB/sec is PATHETIC for the above hardware. I thought the ad for the HD said something about 66MB per second!!?!? What gives?

Well, let's find out more about how Linux is addressing your drive:

hdparm /dev/hda

/dev/hda:
multcount    =  0 (off)
I/O support  =  0 (default 16-bit)
unmaskirq    =  0 (off)
using_dma    =  0 (off)
keepsettings =  0 (off)
nowerr       =  0 (off)
readonly     =  0 (off)
readahead    =  8 (on)
geometry     = 1870/255/63, sectors = 30043440, start = 0

These are the defaults. Nice, safe, but not necessarily optimal. What's all this about 16-bit mode? I thought that went out with the 386! And why are most of the other options turned off?

Well, it's generally considered a good idea for any self-respecting distribution to install itself in the kewlest, slickest, but SAFEST way it possibly can. The above settings are virtually guaranteed to work on any hardware you might throw at it. But since we know we're throwing something more than a dusty, 8-year-old, 16-bit multi-IO card at it, let's talk about the interesting options:

multcount: Short for multiple sector count. This controls how many sectors are fetched from the disk in a single I/O interrupt. Almost all modern IDE drives support this. The man page claims:

When this feature is enabled, it typically reduces operating system overhead for disk I/O by 30-50%. On many systems, it also provides increased data throughput of anywhere from 5% to 50%.
I/O support: This is a big one. This flag controls how data is passed from the PCI bus to the controller. Almost all modern controller chipsets support mode 3, or 32-bit mode w/sync. Some even support 32-bit async. Turning this on will almost certainly double your throughput (see below.)

unmaskirq: Turning this on will allow Linux to unmask other interrupts while processing a disk interrupt. What does that mean? It lets Linux attend to other interrupt-related tasks (i.e., network traffic) while waiting for your disk to return with the data it asked for. It should improve overall system response time, but be warned: Not all hardware configurations will be able to handle it. See the manpage.

using_dma: DMA can be a tricky business. If you can get your controller and drive using a DMA mode, do it. But I have seen more than one machine hang while playing with this option. Again, see the manpage (and the example on the next page)!

Turbocharged

So, since we have our system in single-user mode like a good little admin, let's try out some turbo settings:

hdparm -c3 -m16 /dev/hda

/dev/hda:
setting 32-bit I/O support flag to 3
setting multcount to 16
multcount    =  16 (on)
I/O support  =  3 (32-bit w/sync)

Great! 32-bit sounds nice. And some multi-reads might work. Let's re-run the benchmark:

hdparm -tT /dev/hda


/dev/hda:
Timing buffer-cache reads:   128 MB in  1.41 seconds =90.78 MB/sec
Timing buffered disk reads:  64 MB in  9.84 seconds = 6.50 MB/sec

WOW! Almost double the disk throughput without really trying! Incredible.

But wait, there's more: We're still not unmasking interrupts, using DMA, or even a using decent PIO mode! Of course, enabling these gets riskier. (Why is it always a trade-off between freedom and security?) The man page mentions trying Multiword DMA mode2, so:

hdparm -X34 -d1 -u1 /dev/hda

...Unfortunately this seems to be unsupported on this particular box (it hung like an NT box running a Java app.) So, after rebooting it (again in single-user mode), I went with this:

hdparm -X66 -d1 -u1 -m16 -c3 /dev/hda

/dev/hda:
setting 32-bit I/O support flag to 3
setting multcount to 16
setting unmaskirq to 1 (on)
setting using_dma to 1 (on)
setting xfermode to 66 (UltraDMA mode2)
multcount    = 16 (on)
I/O support  =  3 (32-bit w/sync)
unmaskirq    =  1 (on)
using_dma    =  1 (on)

And then checked:

hdparm -tT /dev/hda

/dev/hda:
Timing buffer-cache reads:   128 MB in  1.43 seconds =89.51 MB/sec
Timing buffered disk reads:  64 MB in  3.18 seconds =20.13 MB/sec

20.13 MB/sec. A far cry from the miniscule 3.58 we started with...

By the way, notice how we specified the -m16 and -c3 switch again? That's because it doesn't remember your hdparm settings between reboots. Be sure to add the above line (not the test line with -tT flags!) to your /etc/rc.d/* scripts once you're sure the system is stable (and preferably after your fsck runs; having an extensive fs check run with your controller in a flaky mode may be a good way to generate vast quantities of entropy, but it's no way to administer a system. At least not with a straight face...)

Now, after running the benchmark a few more times, reboot in multi-user mode and fire up X. Load Netscape. And try not to fall out of your chair.

In conclusion

This is one of those interesting little tidbits that escapes many "seasoned" Linux veterans, especially since one never sees any indication that the system isn't using the most optimal settings. (Gee, all my kernel messages have looked fine....) And using hdparm isn't completely without risk, but is well worth investigating.

And it doesn't stop at performance: hdparm lets you adjust various power saving modes as well. See the hdparm(8) for the final word.

Many thanks to Mark Lord for putting together this nifty utility. If your particular distribution doesn't include hdparm (usually in /sbin or /usr/sbin), get it from the source at http://metalab.unc.edu/pub/Linux/system/hardware/

Happy hacking!

Rob Flickenger is a long time supporter of FreeNetworks and DIY networking. Rob is the author of three O'Reilly books: Building Wireless Community Networks, Linux Server Hacks, and Wireless Hacks.

Free thin Client

2008-06-18T08:13:00.000+07:00

How to get your free thin clients

1. Download 2X ThinClientServer PXES edition

2. Install 2X ThinClientServer PXES edition on a Windows or Linux machine

3. Select your PCs (these can be outdated PCs with as little as 32 MB of RAM and 200 Mhz processing power) to convert to thin clients. For detailed instructions review the manual (link to manual)

4. You will be able to use and manage an unlimited number of thin client devices perpetually - no license fees required.

How 2X ThinClientServer works

2X ThinClientServer deploys a small footprint Linux-based OS to old PCs, new low cost PCs and to popular thin client devices (HP, Neoware, Wyse, Maxspeed and more). Thin clients always boot the latest version of the OS from the ThinClientServer. The thin client OS is write protected for maximum security.

2X ThinClientServer features:

Converting existing PCs to thin clients
Manage users' connection settings centrally by user, group or department
Limit users to 2X published applications rather than giving access to a whole desktop
Thin client vendor independent: Manage any thin client / PC centrally
Supports virtually all thin clients and computer hardware

Download your free thin clients today!

Foundation of tweaking

2008-06-16T18:52:00.000+07:00

Much like building a house, the foundation is important. Tweaking and optimizing KDE will mean little in actual performance gains if the foundation is improperly laid.

Probably the first area users should focus is the distro they select. Some distro vendors try to be all things to all people and that effort results in a lot of unnecessary complication and overhead. This is especially true with distros where the vendor tries to merge several GUIs into a seamless operation. Doable, for sure, but clunky and slow. If users have decided to use KDE as their primary GUI, then select a distro that does not use the all-for-all approach.
Along with the distro choice, use the 2.6 kernel rather than the 2.4. This is rather standard these days, but there is a noticeable difference in speed between the two kernels.
Another area where users should focus is underneath the GUI: the X server environment. That is, users should ensure that X is configured correctly and there are no errors in the X server boot log (typically located at /var/log/Xorg.0.log).
Ensure the correct X driver is installed for the video card. The generic VESA driver will not run as quickly or efficiently as dedicated drivers.
Select a screen resolution that your system will handle easily. Although larger monitors handle screen resolutions of 1280x1024 and higher, some people might be content at 1024x768.
A similar X tweak is to run the video resolution at a lower screen depth. Many people with new hardware assume that everybody needs to run their boxes at 24-bit (16,777,216 colors) depth. Not so. To improve video response, consider running X at a 15-bit (32,768 colors) or 16-bit (65,536 colors) depth. Note: KDE provides no direct way to reduce color depth—manually edit the /etc/X11/xorg.conf file.
Related to configuring X is ensuring there are no problems with fonts. Inspect the X server boot log for clues. KDE uses font caches, therefore the number of fonts installed should not impact performance in any dramatic manner. However, ensure all font directories contain a font cache file.
If the budget allows, buy additional RAM. The Linux kernel tends to be RAM intensive rather than CPU intensive. Most older Pentium Socket-7 motherboard (Pentium I and MMX) will support up to 256 MB of RAM. Adding RAM will improve performance noticeably, even with older motherboards.
If the budget allows, obtain a newer hard drive. Bear in mind that the BIOS of older motherboards will limit the size and speed of the hard drive. However, used 20 and 40 GB drives manufactured only a few years ago are available for far less than one pays for new drives and need not impact the budget deeply. These drives minimally are ATA-33 and use DMA (direct memory access). Except for hobbyists and certain dedicated applications, many typical desktop users will never fill a 20 GB drive to capacity. Important, however is that the drive should support DMA.
Enable DMA. DMA will improve performance noticeably. For some distros, this option might require adding some lines to the startup rc.local script using the hdparm command.

Tweaking KDE

2008-06-16T18:47:00.000+07:00

After establishing these foundations, users can tweak KDE to perform well on older hardware. Several options are listed at the KDE wiki.

Update to a recent version of KDE. The updating game gets old real fast, but generally, with KDE a recent version means improved performance.
Disable wallpaper. Select a pleasing and comfortable desktop screen color. (Configure Desktop.)
Disable background gradients. (Configure Desktop.)
Disable shadowed fonts. (Configure Desktop, Advanced Options.)
Disable desktop icon tool tips. (Configure Desktop, Behavior.)
Minimize the number of device icons on the desktop. (Configure Desktop, Behavior.)
Virtual desktops. Limit this to two desktops, possibly only one. Consider that most people are not multi-taskers. Typically most people concurrently run only two to three desktop programs. Having a bunch of programs running in standby, which is how virtual desktops basically work, means a lot of extra overhead that most typical users do not need. Although useful, many people get by comfortably with only one desktop. (Configure Desktop, Multiple Desktops.)
Use a plain blank screen saver. (Configure Desktop, Screen Saver.)
Disable the mouse cursor launch feedback. (Appearance and Themes, Launch Behavior.)
Disable themes. Yes, themes add a degree of personalization, but with older hardware, at the sacrifice of speed and response.
Consider using the KDE Classic widget set and KDE 2 window decorations. Yes, this ends up looking like MS Windows 95, but this desktop is easy on system resources. (Appearance and Themes, Style; Appearance and Themes, Window Decorations.)
Disable displaying window content when moving or resizing windows. (Desktop, Windows Behavior.)
Disable shading animation and hovering. (Desktop, Window Behavior.)
Disable transparent and translucent menus and panels. These bells and whistles are CPU and memory intensive. (Desktop, Window Behavior.)
Disable GUI effects, such as cascading menus and drop shadows.
Mouse cursor. A simple non-themed mouse pointer is sufficient for most people.
System sounds. Reduce the number of system sounds being used and use sound files that are small in size and load quickly.
Enable Konqueror preloading. Konqueror will load faster and Konqueror is too useful as a file manager not to have this option enabled. (Control Center→KDE Components→KDE Performance)
Disable as many KDE specific services as practical. (Control Center→KDE Components→Service Manager)

Hopefully these suggestions will noticeably improve your KDE performance with your older box.

Mandriva Spring 2008.1 : How install LAMP

2008-06-16T09:46:00.000+07:00

LAMP = Linux Apache Mysql Phpmyadmin (link).
Connect to repository Mandriva from easyurpmi.

Installation:

-run command

urpmi apache mysql phpmyadmin

done...

Mandriva Spring 2008.1 : Mysql Installation

2008-06-16T09:20:00.000+07:00

urpmi mysql phpmyadmin

installing mysql-common-5.0.51a-7mdv2008.1.i586.rpm mysql-client-5.0.51a-7mdv2008.1.i586.rpm apache-mod_php-5.2.5-5mdv2008.1.i586.rpm phpmyadmin-2.11.5-1mdv2008.1.noarch.rpm mysql-5.0.51a-7mdv2008.1.i586.rpm from /var/cache/urpmi/rpms
Preparing... ##########################################################################################
33/37: mysql-client ##########################################################################################
34/37: mysql-common ##########################################################################################
35/37: apache-mod_php ##########################################################################################
36/37: phpmyadmin ##########################################################################################
37/37: mysql ##########################################################################################
----------------------------------------------------------------------

More information on package mysql-5.0.51a-7mdv2008.1.i586

The initscript used to start mysql has been reverted to use the one shipped
by MySQL AB. This means the following changes:

* The MYSQLD_OPTIONS="--skip-networking" option in the /etc/sysconfig/mysqld
file has been removed, this is now set in the /etc/my.cnf file.

* The MySQL Instance Manager is used by default, set use_mysqld_safe="1" in
the /etc/sysconfig/mysqld file to use the old mysqld_safe script.

* The generation of the initial system mysql database is now done when mysql
is started from the initscript and only if the /var/lib/mysql/mysql
directory is empty (mysql_install_db). Previousely this was quite hidden and
silently done at (rpm) install time.

The extra MySQL-NDB server package has been merged into the MySQL-Max package
and ndb related pieces has been split into different sub packages as done by
MySQL AB. The MySQL libraries and the MySQL-common sub package uses the
MySQL-Max build so that no functionality required by for example the NDB
parts are lost.

The MySQL-common package now ships with a default /etc/my.cnf file that is
based on the my-medium.cnf file that comes with the source code. The
/etc/my.cnf file is constructed at build time of this package.

To connect to the Instance Manager you need to pass the correct command line
options like in the following examples:

* mysql -u root --password=my_password --port=2273 --protocol=TCP
* mysql -u root --password=my_password --socket=/var/lib/mysql/mysqlmanager.sock

Please note you also need to add a user in the /etc/mysqlmanager.passwd file and
make sure the file is owned by the user under which the Instance Manager service
is running under.

[root@box bayu]# /etc/init.d/mysqld start
Initializing MySQL database:
Installing MySQL system tables...
OK
Filling help tables...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h box password 'new-password'

Alternatively you can run:
/usr/bin/mysql_secure_installation

which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with:
cd / ; /usr/bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl
cd mysql-test ; perl mysql-test-run.pl

Please report any problems with the /usr/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com
Starting MySQL: [ OK ]
[root@box bayu]#