Beyond Technology

Linux Software RAID

2020-01-13T01:46:00.002-08:00

Introduction

The main goals of using redundant arrays of inexpensive disks (RAID) are to improve disk data performance and provide data redundancy.
RAID can be handled either by the operating system software or it may be implemented via a purpose built RAID disk controller card without having to configure the operating system at all. This chapter will explain how to configure the software RAID schemes supported by RedHat/Fedora Linux.
For the sake of simplicity, the chapter focuses on using RAID for partitions that include neither the /boot or the root (/) filesystems.

RAID Types

Whether hardware- or software-based, RAID can be configured using a variety of standards. Take a look at the most popular.

Linear Mode RAID

In the Linear RAID, the RAID controller views the RAID set as a chain of disks. Data is written to the next device in the chain only after the previous one is filled.
The aim of Linear RAID is to accommodate large filesystems spread over multiple devices with no data redundancy. A drive failure will corrupt your data.
Linear mode RAID is not supported by Fedora Linux.

RAID 0

With RAID 0, the RAID controller tries to evenly distribute data across all disks in the RAID set.
Envision a disk as if it were a plate, and think of the data as a cake. You have four cakes- chocolate, vanilla, cherry and strawberry-and four plates. The initialization process of RAID 0, divides the cakes and distributes the slices across all the plates. The RAID 0 drivers make the operating system feel that the cakes are intact and placed on one large plate. For example, four 9GB hard disks configured in a RAID 0 set are seen by the operating system to be one 36GB disk.
Like Linear RAID, RAID 0 aims to accommodate large filesystems spread over multiple devices with no data redundancy. The advantage of RAID 0 is data access speed. A file that is spread over four disks can be read four times as fast. You should also be aware that RAID 0 is often called striping.
RAID 0 can accommodate disks of unequal sizes. When RAID runs out of striping space on the smallest device, it then continues the striping using the available space on the remaining drives. When this occurs, the data access speed is lower for this portion of data, because the total number of RAID drives available is reduced. For this reason, RAID 0 is best used with drives of equal size.
RAID 0 is supported by Fedora Linux. Figure 26.1 illustrates the data allocation process in RAID 0.

RAID 1

With RAID 1, data is cloned on a duplicate disk. This RAID method is therefore frequently called disk mirroring. Think of telling two people the same story so that if one forgets some of the details you can ask the other one to remind you.
When one of the disks in the RAID set fails, the other one continues to function. When the failed disk is replaced, the data is automatically cloned to the new disk from the surviving disk. RAID 1 also offers the possibility of using a hot standby spare disk that will be automatically cloned in the event of a disk failure on any of the primary RAID devices.
RAID 1 offers data redundancy, without the speed advantages of RAID 0. A disadvantage of software-based RAID 1 is that the server has to send data twice to be written to each of the mirror disks. This can saturate data busses and CPU use. With a hardware-based solution, the server CPU sends the data to the RAID disk controller once, and the disk controller then duplicates the data to the mirror disks. This makes RAID-capable disk controllers the preferred solution when implementing RAID 1.
A limitation of RAID 1 is that the total RAID size in gigabytes is equal to that of the smallest disk in the RAID set. Unlike RAID 0, the extra space on the larger device isn't used.
RAID 1 is supported by Fedora Linux. Figure 26.1 illustrates the data allocation process in RAID 1.

Figure 26-1 RAID 0 And RAID 1 Operation

RAID 4

RAID 4 operates likes RAID 0 but inserts a special error-correcting or parity chunk on an additional disk dedicated to this purpose.
RAID 4 requires at least three disks in the RAID set and can survive the loss of a single drive only. When this occurs, the data in it can be recreated on the fly with the aid of the information on the RAID set's parity disk. When the failed disk is replaced, it is repopulated with the lost data with the help of the parity disk's information.
RAID 4 combines the high speed provided of RAID 0 with the redundancy of RAID 1. Its major disadvantage is that the data is striped, but the parity information is not. In other words, any data written to any section of the data portion of the RAID set must be followed by an update of the parity disk. The parity disk can therefore act as a bottleneck. For this reason, RAID 4 isn't used very frequently.
RAID 4 is not supported by Fedora Linux.

RAID 5

RAID 5 improves on RAID 4 by striping the parity data between all the disks in the RAID set. This avoids the parity disk bottleneck, while maintaining many of the speed features of RAID 0 and the redundancy of RAID 1. Like RAID 4, RAID 5 can survive the loss of a single disk only.
RAID 5 is supported by Fedora Linux. Figure 26.2 illustrates the data allocation process in RAID 5.
Linux RAID 5 requires a minimum of three disks or partitions.

Figure 26-2 RAID 5 Operation

Before You Start

Specially built hardware-based RAID disk controllers are available for both IDE and SCSI drives. They usually have their own BIOS, so you can configure them right after your system's the power on self test (POST). Hardware-based RAID is transparent to your operating system; the hardware does all the work.
If hardware RAID isn't available, then you should be aware of these basic guidelines to follow when setting up software RAID.

IDE Drives

To save costs, many small business systems will probably use IDE disks, but they do have some limitations.

The total length of an IDE cable can be only a few feet long, which generally limits IDE drives to small home systems.
IDE drives do not hot swap. You cannot replace them while your system is running.
Only two devices can be attached per controller.
The performance of the IDE bus can be degraded by the presence of a second device on the cable.
The failure of one drive on an IDE bus often causes the malfunctioning of the second device. This can be fatal if you have two IDE drives of the same RAID set attached to the same cable.

For these reasons, I recommend you use only one IDE drive per controller when using RAID, especially in a corporate environment. In a home or SOHO setting, IDE-based software RAID may be adequate.

Serial ATA Drives

Serial ATA type drives are rapidly replacing IDE, or Ultra ATA, drives as the preferred entry level disk storage option because of a number of advantages:

The drive data cable can be as long as 1 meter in length versus IDE's 18 inches.
Serial ATA has better error checking than IDE.
There is only one drive per cable which makes hot swapping, or the capability to replace components while the system is still running, possible without the fear of affecting other devices on the data cable.
There are no jumpers to set on Serial ATA drives to make it a master or slave which makes them simpler to configure.
IDE drives have a 133Mbytes/s data rate whereas the Serial ATA specification starts at 150 Mbytes/sec with a goal of reaching 600 Mbytes/s over the expected ten year life of the specification.

If you can't afford more expensive and faster SCSI drives, Serial ATA would be the preferred device for software and hardware RAID

SCSI Drives

SCSI hard disks have a number of features that make them more attractive for RAID use than either IDE or Serial ATA drives.

SCSI controllers are more tolerant of disk failures. The failure of a single drive is less likely to disrupt the remaining drives on the bus.
SCSI cables can be up to 25 meters long, making them suitable for data center applications.
Much more than two devices may be connected to a SCSI cable bus. It can accommodate 7 (single-ended SCSI) or 15 (all other SCSI types) devices.
Some models of SCSI devices support "hot swapping" which allows you to replace them while the system is running.
SCSI currently supports data rates of up to 640 Mbytes/s making them highly desirable for installations where rapid data access is imperative.

SCSI drives tend to be more expensive than IDE drives, however, which may make them less attractive for home use.

Should I Use Software RAID Partitions Or Entire Disks?

It is generally a not a good idea to share RAID-configured partitions with non-RAID partitions. The reason for this is obvious: A disk failure could still incapacitate a system.
If you decide to use RAID, all the partitions on each RAID disk should be part of a RAID set. Many people simplify this problem by filling each disk of a RAID set with only one partition.

Backup Your System First

Software RAID creates the equivalent of a single RAID virtual disk drive made up of all the underlying regular partitions used to create it. You have to format this new RAID device before your Linux system can store files on it. Formatting, however, causes all the old data on the underlying RAID partitions to be lost. It is best to backup the data on these and any other partitions on the disk drive on which you want implement RAID. A mistake could unintentionally corrupt valid data.

Configure RAID In Single User Mode

As you will be modifying the disk structure of your system, you should also consider configuring RAID while your system is running in single-user mode from the VGA console. This makes sure that most applications and networking are shutdown and that no other users can access the system, reducing the risk of data corruption during the exercise.

[root@bigboy tmp]# init 1

Once finished, issue the exit command, and your system will boot in the default runlevel provided in the /etc/inittab file.

Configuring Software RAID

Configuring RAID using Fedora Linux requires a number of steps that need to be followed carefully. In the tutorial example, you'll be configuring RAID 5 using a system with three pre-partitioned hard disks. The partitions to be used are:

/dev/hde1

/dev/hdf2

/dev/hdg1

Be sure to adapt the various stages outlined below to your particular environment.

RAID Partitioning

You first need to identify two or more partitions, each on a separate disk. If you are doing RAID 0 or RAID 5, the partitions should be of approximately the same size, as in this scenario. RAID limits the extent of data access on each partition to an area no larger than that of the smallest partition in the RAID set.

Determining Available Partitions

First use the fdisk -l command to view all the mounted and unmounted filesystems available on your system. You may then also want to use the df -k command, which shows only mounted filesystems but has the big advantage of giving you the mount points too.
These two commands should help you to easily identify the partitions you want to use. Here is some sample output of these commands.

[root@bigboy tmp]# fdisk -l

Disk /dev/hda: 12.0 GB, 12072517632 bytes

255 heads, 63 sectors/track, 1467 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System

/dev/hda1   *         1        13    104391   83  Linux

/dev/hda2            14       144   1052257+  83  Linux

/dev/hda3           145       209    522112+  82  Linux swap

/dev/hda4           210      1467  10104885    5  Extended

/dev/hda5           210       655   3582463+  83  Linux

...

...

/dev/hda15         1455      1467    104391   83  Linux

[root@bigboy tmp]#

[root@bigboy tmp]# df -k

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/hda2              1035692    163916    819164  17% /

/dev/hda1               101086      8357     87510   9% /boot

/dev/hda15              101086      4127     91740   5% /data1

...

...

...

/dev/hda7              5336664    464228   4601344  10% /var

[root@bigboy tmp]#

Unmount the Partitions

You don't want anyone else accessing these partitions while you are creating the RAID set, so you need to make sure they are unmounted.

[root@bigboy tmp]# umount /dev/hde1

[root@bigboy tmp]# umount /dev/hdf2

[root@bigboy tmp]# umount /dev/hdg1

Prepare The Partitions With FDISK

You have to change each partition in the RAID set to be of type FD (Linux raid autodetect), and you can do this with fdisk. Here is an example using /dev/hde1.

[root@bigboy tmp]# fdisk /dev/hde

The number of cylinders for this disk is set to 8355.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

  (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help):

Use FDISK Help

Now use the fdisk m command to get some help:

Command (m for help): m

...

...

  p   print the partition table

  q   quit without saving changes

  s   create a new empty Sun disklabel

  t   change a partition's system id

...

...

Command (m for help):

Set The ID Type To FD

Partition /dev/hde1 is the first partition on disk /dev/hde. Modify its type using the t command, and specify the partition number and type code. You also should use the L command to get a full listing of ID types in case you forget.

Command (m for help): t

Partition number (1-5): 1

Hex code (type L to list codes): L

...

...

...

16  Hidden FAT16    61   SpeedStor       f2  DOS secondary

17  Hidden HPFS/NTF 63  GNU HURD or Sys fd  Linux raid auto

18  AST SmartSleep  64  Novell Netware  fe  LANstep

1b  Hidden Win95 FA 65  Novell Netware  ff  BBT

Hex code (type L to list codes): fd

Changed system type of partition 1 to fd (Linux raid autodetect)

Command (m for help):

Make Sure The Change Occurred

Use the p command to get the new proposed partition table:

Command (m for help): p

Disk /dev/hde: 4311 MB, 4311982080 bytes

16 heads, 63 sectors/track, 8355 cylinders

Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot    Start       End    Blocks   Id  System

/dev/hde1             1      4088   2060320+  fd  Linux raid autodetect

/dev/hde2          4089      5713    819000   83  Linux

/dev/hde4          6608      8355    880992    5  Extended

/dev/hde5          6608      7500    450040+  83  Linux

/dev/hde6          7501      8355    430888+  83  Linux

Command (m for help):

Save The Changes

Use the w command to permanently save the changes to disk /dev/hde:

Command (m for help): w

The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.

The kernel still uses the old table.

The new table will be used at the next reboot.

Syncing disks.

[root@bigboy tmp]#

The error above will occur if any of the other partitions on the disk is mounted.

Repeat For The Other Partitions

For the sake of brevity, I won't show the process for the other partitions. It's enough to know that the steps for changing the IDs for /dev/hdf2 and /dev/hdg1 are very similar.

Preparing the RAID Set

Now that the partitions have been prepared, we have to merge them into a new RAID partition that we'll then have to format and mount. Here's how it's done.

Create the RAID Set

You use the mdadm command with the --create option to create the RAID set. In this example we use the --level option to specify RAID 5, and the --raid-devices option to define the number of partitions to use.

[root@bigboy tmp]# mdadm --create --verbose /dev/md0 --level=5 \

   --raid-devices=3 /dev/hde1 /dev/hdf2 /dev/hdg1

mdadm: layout defaults to left-symmetric

mdadm: chunk size defaults to 64K

mdadm: /dev/hde1 appears to contain an ext2fs file system

    size=48160K  mtime=Sat Jan 27 23:11:39 2007

mdadm: /dev/hdf2 appears to contain an ext2fs file system

    size=48160K  mtime=Sat Jan 27 23:11:39 2007

mdadm: /dev/hdg1 appears to contain an ext2fs file system

    size=48160K  mtime=Sat Jan 27 23:11:39 2007

mdadm: size set to 48064K

Continue creating array? y

mdadm: array /dev/md0 started.

[root@bigboy tmp]#

Confirm RAID Is Correctly Inititalized

The /proc/mdstat file provides the current status of all RAID devices. Confirm that the initialization is finished by inspecting the file and making sure that there are no initialization related messages. If there are, then wait until there are none.

[root@bigboy tmp]# cat /proc/mdstat

Personalities : [raid5]

read_ahead 1024 sectors

md0 : active raid5 hdg1[2] hde1[1] hdf2[0]

      4120448 blocks level 5, 32k chunk, algorithm 3 [3/3] [UUU]

unused devices: <none>

[root@bigboy tmp]#

Notice that the new RAID device is called /dev/md0. This information will be required for the next step.

Format The New RAID Set

Your new RAID partition now has to be formatted. The mkfs.ext3 command is used to do this.

[root@bigboy tmp]# mkfs.ext3 /dev/md0

mke2fs 1.39 (29-May-2006)

Filesystem label=

OS type: Linux

Block size=1024 (log=0)

Fragment size=1024 (log=0)

36144 inodes, 144192 blocks

7209 blocks (5.00%) reserved for the super user

First data block=1

Maximum filesystem blocks=67371008

18 block groups

8192 blocks per group, 8192 fragments per group

2008 inodes per group

Superblock backups stored on blocks:

        8193, 24577, 40961, 57345, 73729

Writing inode tables: done

Creating journal (4096 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 33 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

[root@bigboy tmp]#

Create the mdadm.conf Configuration File

Your system doesn't automatically remember all the component partitions of your RAID set. This information has to be kept in the mdadm.conf file. The formatting can be tricky, but fortunately the output of the mdadm --detail --scan --verbose command provides you with it. Here we see the output sent to the screen.

[root@bigboy tmp]# mdadm --detail --scan --verbose

ARRAY /dev/md0 level=raid5 num-devices=4

UUID=77b695c4:32e5dd46:63dd7d16:17696e09

   devices=/dev/hde1,/dev/hdf2,/dev/hdg1

[root@bigboy tmp]#

Here we export the screen output to create the configuration file.

[root@bigboy tmp]# mdadm --detail --scan --verbose > /etc/mdadm.conf

Create A Mount Point For The RAID Set

The next step is to create a mount point for /dev/md0. In this case we'll create one called /mnt/raid

[root@bigboy mnt]# mkdir /mnt/raid

Edit The /etc/fstab File

The /etc/fstab file lists all the partitions that need to mount when the system boots. Add an Entry for the RAID set, the /dev/md0 device.

/dev/md0      /mnt/raid     ext3    defaults    1 2

Do not use labels in the /etc/fstab file for RAID devices; just use the real device name, such as /dev/md0. In older Linux versions, the /etc/rc.d/rc.sysinit script would check the /etc/fstab file for device entries that matched RAID set names listed in the now unused /etc/raidtab configuration file. The script would not automatically start the RAID set driver for the RAID set if it didn't find a match. Device mounting would then occur later on in the boot process. Mounting a RAID device that doesn't have a loaded driver can corrupt your data and produce this error.

Starting up RAID devices: md0(skipped)

Checking filesystems

/raiddata: Superblock has a bad ext3 journal(inode8)

CLEARED.

***journal has been deleted - file system is now ext 2 only***

/raiddata: The filesystem size (according to the superblock) is 2688072 blocks.

The physical size of the device is 8960245 blocks.

Either the superblock or the partition table is likely to be corrupt!

/boot: clean, 41/26104 files, 12755/104391 blocks

/raiddata: UNEXPECTED INCONSISTENCY; Run fsck manually (ie without -a or -p options).

If you are not familiar with the /etc/fstab file use the man fstab command to get a comprehensive explanation of each data column it contains.
The /dev/hde1, /dev/hdf2, and /dev/hdg1 partitions were replaced by the combined /dev/md0 partition. You therefore don't want the old partitions to be mounted again. Make sure that all references to them in this file are commented with a # at the beginning of the line or deleted entirely.

#/dev/hde1       /data1        ext3    defaults        1 2

#/dev/hdf2       /data2        ext3    defaults        1 2

#/dev/hdg1       /data3        ext3    defaults        1 2

Mount The New RAID Set

Use the mount command to mount the RAID set. You have your choice of methods:

The mount command's -a flag causes Linux to mount all the devices in the /etc/fstab file that have automounting enabled (default) and that are also not already mounted.

[root@bigboy tmp]# mount -a

You can also mount the device manually.

[root@bigboy tmp]# mount /dev/md0 /mnt/raid

Check The Status Of The New RAID

The /proc/mdstat file provides the current status of all the devices.

[root@bigboy tmp]# raidstart /dev/md0

[root@bigboy tmp]# cat /proc/mdstat

Personalities : [raid5]

read_ahead 1024 sectors

md0 : active raid5 hdg1[2] hde1[1] hdf2[0]

      4120448 blocks level 5, 32k chunk, algorithm 3 [3/3] [UUU]

unused devices: <none>

[root@bigboy tmp]#

Conclusion

Linux software RAID provides redundancy across partitions and hard disks, but it tends to be slower and less reliable than RAID provided by a hardware-based RAID disk controller.
Hardware RAID configuration is usually done via the system BIOS when the server boots up, and once configured, it is absolutely transparent to Linux. Unlike software RAID, hardware RAID requires entire disks to be dedicated to the purpose and when combined with the fact that it usually requires faster SCSI hard disks and an additional controller card, it tends to be expensive.
Remember to take these factors into consideration when determining the right solution for your needs and research the topic thoroughly before proceeding. Weighing cost versus reliability is always a difficult choice in systems administration.

Understanding DNS setting

2019-12-29T22:50:00.000-08:00

What is an MX Record

MX stands for Mail Exchange Records. MX records are used in DNS records(or Zone files) to specify how email should be routed.
Lets take an example of say liz@mydomain.com.
This is how a typical DNS record(for mydomain.com) looks like.

; Zone file for mydomain.com

@ 14400 IN SOA ns.mynameserver.com. root.ns.mynameserver.com. (

109157199

                       600 )

mydomain.com. 14400 IN NS ns.mynameserver.com.

mydomain.com. 14400 IN NS ns2.mynameserver.com.

mydomain.com. 14400 IN NS ns3.mynameserver.com.

; A Record

mydomain.com. 14400 IN A 216.34.94.184

localhost.mydomain.com. 14400 IN A 127.0.0.1

; MX record

mydomain.com. 14400 IN MX 0 mydomain.com.

mail 14400 IN CNAME mydomain.com.

www 14400 IN CNAME mydomain.com.

ftp 14400 IN CNAME mydomain.com.

Notice the line with the ``MX'' in it. This is called the MX record.

mydomain.com. 14400 IN MX 0 mydomain.com.

The MX record shows that all emails @ mydomain.com should be routed to the mail server at mydomain.com. The DNS record shows that mydomain.com is located at 216.34.94.184. This means that email meant for liz@mydomain.com will be routed to the email server at 216.34.94.184. This finishes the task of the MX record. The email server on that server(say sendmail) then takes over, collects the email and then proceeds to distribute it to the user ``liz''.
It is important that there be a dot(``.'') after the domain name in the MX record. If the dot is absent, it routes to ``mydomain.com.mydomain.com''. The number 0, indicates Preferance number. Mail is always routed to the server which has the lowest Preferance number. If there is only one mail server, it is safe to mark it 0.

Multiple mail servers

Multiple email servers are useful for the sake of redundancy. If the Highest Priority email server (one with the lowest Preference number) is down, then the email is routed to the Server with the second highest Preference number.
For example

mydomain.com. 14400 IN A 216.34.94.184

server2.mydomain.com. 14400 IN A 216.34.94.185

mydomain.com. 14400 IN MX 0 mydomain.com.

mydomain.com. 14400 IN MX 30 server2.mydomain.com.

You can have unlimited MX entries for Fallback.
If all the MX records are equal Preference numbers, the client simply attempts all equal Preference servers in random order, and then goes to MX record with the next highest Preference number.

Pointing MX records to an IP

Its not possible to have an MX record pointing directly to an IP. For example 'mydomain.com. 14400 IN MX 0 216.34.94.184`` is wrong. Define an ``A Record'' first and then have the MX record pointing to it.

server2.mydomain.com. 14400 IN A 216.34.94.185

mydomain.com. 14400 IN MX 30 server2.mydomain.com.

MX records for Subdomains

A Subdomain is something like this ``Subdomain.mydomain.com''. Assume you want to send an email to liz@subdomain.mydomain.com and to capture that on another server.

mydomain.com. 14400 IN A 216.34.94.184

server2.mydomain.com. 14400 IN A 216.34.94.185

mydomain.com. 14400 IN MX 30 mydomain.com.

subdomain.mydomain.com. 14400 IN MX 30 server2.mydomain.com.

In this configuration, liz@subdomain.mydomain.com would go to 216.34.94.185 and liz@mydomain.com would go to 216.34.94.184.

Testing the MX record

Once you setup your MX record, always test it to see if it is setup correctly. You can do with tools like nslookup.

[root@localhost sangeetha]# nslookup

> set q=mx

> yahoo.com

Server: 192.168.1.1 Address: 192.168.1.1#53

Non-authoritative answer:

yahoo.com mail exchanger = 1 mx1.mail.yahoo.com.

yahoo.com mail exchanger = 1 mx2.mail.yahoo.com.

yahoo.com mail exchanger = 1 mx3.mail.yahoo.com.

yahoo.com mail exchanger = 5 mx4.mail.yahoo.com.

Authoritative answers can be found from:

yahoo.com nameserver = ns2.yahoo.com.

yahoo.com nameserver = ns3.yahoo.com.

yahoo.com nameserver = ns4.yahoo.com.

yahoo.com nameserver = ns5.yahoo.com.

yahoo.com nameserver = ns1.yahoo.com.

mx1.mail.yahoo.com internet address = 4.79.181.14

mx1.mail.yahoo.com internet address = 4.79.181.15

mx1.mail.yahoo.com internet address = 67.28.113.10

mx1.mail.yahoo.com internet address = 67.28.113.11

ns1.yahoo.com internet address = 66.218.71.63

ns2.yahoo.com internet address = 66.163.169.170

ns3.yahoo.com internet address = 217.12.4.104

ns4.yahoo.com internet address = 63.250.206.138

ns5.yahoo.com internet address = 216.109.116.17

IT Policy Document

2019-12-22T20:34:00.002-08:00

Information Technology Policies

And Procedures

Company Name

Introduction

Company Name’s information technology resources constitute a valuable Company name’s asset that must be managed accordingly to ensure their integrity, security, and availability for work, research and business activities. Carrying out this mission requires the company to establish basic Information Security policies and standards and to provide both access and reasonable Security at an acceptable cost. The Company Information Technology Policies and Procedures are intended to facilitate and support authorized access to Company information.

The purpose of the Company Information Policies and Procedures is:

• To establish company-wide Protocol for Information Security.

• To help identify and prevent the compromise of Information Security and the misuse of Company information technology resources.

• To protect the reputation of the Company and to allow the Company to satisfy its legal and ethical responsibilities with regard to its information technology resources.

• To enable the Company to respond to complaints and queries about real or perceived non-compliance with the Company Information Technology Policies and Procedures.

Responsibility

Authorized Users of Company information technology resources are personally responsible for complying with all Company policies, procedures and standards relating to Information Security, regardless of data center or location and will be held personally accountable for any misuse of these resources.

Approvals

This Document in its initial form has received the following review and approvals from Company name Management:

________________ ______________ _____________

Title Date

________________ ______________ _____________

Title Date

Table of Contents

Unauthorized Use Policy.............................................................................3

Guest User Policy........................................................................................4

Company Confidentiality Policy.................................................................5

Acceptable Use Policy.................................................................................6

Electronic Communications Policy............................................................10

Password Policy.........................................................................................11

Acceptable Encryption Policy....................................................................14

Remote Access Policy................................................................................15

Physical Security Policy.............................................................................17

Workstation Configuration Security Policy...............................................19

Server Configuration Security Policy........................................................21

“De-Militarized Zone” Network Equipment Policy..................................23

Router Security Policy...............................................................................26

Wireless Communication Policy................................................................27

Change Management Policy......................................................................28

Information Security Audit Policy.............................................................29

Unauthorized Use Policy

1. Purpose.

This policy sets forth the Company name’s policy regarding Unauthorized Use of the Company Information Technology Network.

2. Scope.

This policy covers all Unauthorized Use of the Company Information Technology Network, whether such Unauthorized Use is done by a person who is not an Authorized User, or by an Authorized User who exceeds the limits of that person’s authorization whose use exceeds Authorized Use permitted by the Company, all of whom are referred to in this policy as “Unauthorized Users.”

3. Policy.

· All Unauthorized Users are prohibited from using Company Information Technology Network for any purpose whatsoever. Authorized Users are prohibited from using the Company Information Technology Network in any way that exceeds the limits of their individual authorization.

· The Computing and networking facilities of the Company are intended for use for administration in support of the Company mission.

· Access granted as a privilege to staff and the Company reserves the right to limit, restricts, or extends access to the facilities.

· The Company IT facilities are not to be use for commercial/Personal purposes or non-Company-related activities.

4. Enforcement.

Unauthorized Users may be subject to criminal prosecution and/or civil suits in which the Company seeks damages and/or other legal and/or equitable remedies. Unauthorized Users who are employees of the Company may also be subject to disciplinary action, up to and including termination of employment.

Guest User Policy

1. Purpose.

The Company sharing and meeting with the buyers’ agent.

Companies held regular pp meeting with buyer and some supplier. In doing so, Company often grants to Company guests and visitors the right to use Internet with connected to Company Public WIFI, and cannot be allow connect to Company’s Corporate WIFI.

2. Scope.

This policy applies only to any Guest Users and does not include staff, or guest from The Companies group.

3. Policy.

A Guest User is an Authorized User when utilizing the Company’s information technology resources in compliance with the Company Information Technology Policies and Procedures and as long as the use remains within the limits of the Guest User’s individual authorization. The Guest User may not be authorized to use computers in the Company. The Guests only permitted using the WIFI’s guest in the specified area.

4. Enforcement.

Any Authorized User found to be in violation of this policy will be considered an Unauthorized User, and as such are subject to disciplinary action pursuant with the Enforcement section of the Unauthorized Use Policy.

Company Confidentiality Policy

Purpose.

Confidential information may be developed or obtained by Company employees/interns as a result of that person’s relationship with the Company.

Scope.

All Authorized Users who have contact with and access to confidential information must keep such information confidential. Confidential information includes, but is not limited to, the following types of information:

• Staff and employee information, such as address, telephone number, KTP number, birth date and other private information.

• Operations manuals, Company practices, marketing plans, techniques and materials, development plans, and financial information.

• Staff or applicant lists, personnel and payroll records, records regarding vendors and suppliers, records and files of the Company, and other information concerning the business affairs or operating practices of the Company.

Policy.

Confidential information must never be released, removed from the Company premises, copied, transmitted, or in any other way used by the Authorized User for any purpose outside the scope of their Company employment, nor revealed to non-Company employees, without the express written consent of Company management personnel.

Information stored on the Company Information Technology Network is confidential and may not be distributed outside the Company except in the course of the Company’s business or as otherwise authorized by management personnel. Authorized Users may not remove or borrow from the Company premises any computer equipment, disks, or related technology, product or information unless authorized to do so.

Enforcement.

Acceptable Use Policy

Overview.

This policy is intended to protect the Company, employees, and staff as well as the Company from the consequences of illegal or damaging actions by individuals using the Company Information Technology Network.

The Company Information Technology Network includes: Internet/Intranet/Extranet-related systems, including but not limited to computer/Networking equipment, Software, Operating Systems, storage media, Network accounts providing electronic mail, VOIP (Voice Over Internet Protocol), HRD’s information system, WWW browsing, and FTP, which are the property of the Company. They are to be used for Company business purposes and to serve the interests of the Company and are intended for use for administration in support of the Company mission, and as well as all Authorized Users. Effective computer Security is a team effort requiring the participation and support of every employee, Staff and Authorized User who deals with information and/or information systems. It is the responsibility of every computer user to know the Company Information Technology Policies and Procedures, and to comply with the Company Information Technology Policies and Procedures.

Purpose.

This policy describes the Authorized Use of the Company Information Technology Network and protects the Company and Authorized Users. Unauthorized uses expose the Company to many risks including legal liability, Virus attacks, and the compromise of Network systems, Services, and information.

Scope.

This policy applies to all persons with a Company-owned, third party-owned, or personally-owned computing device that is connected to the Company Information Technology Network.

Policy.

a. General Use and Ownership:

1. Data created by Authorized Users that is on the Company Information Technology Network is the property of the Company. There is no guarantee that information stored on the Company Information Technology Network device will be confidential

2. Authorized Use includes reasonable personal use of the Company Information Technology Network by Authorized Users. Company departments are responsible for creating guidelines concerning personal use of the Company Information Technology Network. In the absence of such guidelines, employees or staff should consult their supervisor, manager, or the Information Security Guidelines.

3. Any information that an Authorized User considers to be sensitive or vulnerable should be encrypted. For guidelines on information classification, see Information Security's Information Sensitivity Policy. For guidelines on encrypting Email and documents, consult Information Security's Awareness Initiative.

4. Authorized Company employees may monitor the Company Information Technology Network traffic at any time, in accordance with the Information Security Audit Policy.

b. Security and Proprietary Information.

1. Authorized Users are required to classify the user interface for information contained on the Company Information Technology Network as “confidential” or “not confidential,” as defined by Company Confidentiality Guidelines. Confidential information includes, but is not limited to: Company private data, specifications, student information, and research data. Employees are required to take all necessary steps to prevent unauthorized access to this Sensitive Information.

2. Authorized Users are responsible for the Security of their passwords and accounts and must keep passwords confidential and are not permitted to share accounts.

3. Authorized Users are responsible for logging out of all systems and accounts when they are not being used; they must not be left unattended.

4. All Laptops and workstation that are part of or connected to the Company Information Technology Network are required to be secured with a password-protected screensaver with the automatic activation feature set at 10 minutes or less, or by logging-off when the device will be unattended.

5. Encryption of information must be used in compliance with Information Security's Acceptable Encryption Use Policy.

6. Authorized Users are required to exercise special care to protect laptop computers that are part of or connected to the Company Information Technology Network in accordance with the “Laptop Security Guidelines.”

7. Postings by Authorized Users from a Company Email address must contain a disclaimer stating that the opinions expressed are strictly those of the author and not necessarily those of the Company, unless posting has been done in the course of Company business.

8. All Computers used by Authorized Users that are connected to the Company Information Technology Network, whether owned by the individual or the Company, must be continually executing approved Virus-scanning Software with a current Virus Database.

9. Authorized Users must use extreme caution when opening e-mail attachments received from unknown senders, which may contain Viruses, e-mail bombs, or Trojan Horse codes.

c. Unacceptable Use of the Company Information Technology Network.

The following activities are prohibited, although Company employees who are Authorized Users may be exempted from these restrictions during the performance of their legitimate job responsibilities. Under no circumstances is an Authorized User permitted to engage in any activity that is illegal under local, state, federal or international law while utilizing the Company Information Technology Network.

Unacceptable use includes, but is not limited to the following activities:

System and Network Activities

The following activities are strictly prohibited, with no exceptions:

1. Violations of the rights of any person or company protected by copyright, trade secret, patent or other Intellectual Property, or similar laws or regulations, including, but not limited to, the installation or distribution of copyrighted or other Software products that are not licensed for use by the Company.

2. Unauthorized copying of copyrighted material including, but not limited to, digitization and distribution of photographs from magazines, books or other copyrighted sources, copyrighted music, and the installation of any copyrighted Software for which the Company or the Authorized User does not have an active license is strictly prohibited.

3. Exporting Software, technical information, Encryption Software or technology, in violation of international or regional export control laws, is illegal. Company management must be consulted prior to export of any material that is in question.

4. Introduction of Malicious Software into the Company Information Technology Network (e.g., Viruses, Worms, Trojan Horses, e-mail bombs, etc.).

5. An Authorized User’s revelation of that person’s account password to others or allowing use of an Authorized User’s account by others, including family and other household members when an Authorized User’s computer is connected to the Company Information Technology Network from home or other non-Company locations.

6. The use of a component of the Company Information Technology Network or other computing asset to actively engage in procuring or transmitting material that violates sexual harassment or hostile workplace laws or that violates any Company policy. Pornographic material is a violation of sexual harassment policies.

7. Making fraudulent offers of products, items, or services originating from any Company account or otherwise made from a computer connected to the Company Information Technology Network.

8. Causing Security breaches or disruptions of communication over the Company Information Technology Network. Security breaches include, but are not limited to, accessing data or other communications of which the Authorized User is not an intended recipient or logging into an account that the Authorized User is not expressly authorized to access. For purposes of this section, "disruption" includes, but is not limited to, Network Sniffing, traffic floods, Packet Spoofing, Denial of Service, etc.

9. Port Scanning or Security Scanning is expressly prohibited unless prior notification to Information Security is made.

10. Executing any form of Network monitoring which will intercept data not intended for the Authorized User is expressly prohibited, unless this activity is a part of the Authorized User’s normal job/duty.

11. Circumventing User Authentication or Security of any device, Network, or account.

12. Interfering with or denying Service to any user other than the individual's Host (for example, a Denial of Service attack).

13. Using any Program/script/command, or sending messages of any kind, with the intent to interfere with or disable a user's terminal session, via any means locally or remotely.

14. Providing information about, or lists of, Company employees or Staff to non-Company parties.

Email and Communications Activities.

1. Requesting new account Mail must send to IT Administrator by Supervisor for activating.

2. Authorized User must not use non-Company Email accounts (e.g. Hotmail, Yahoo, Gmail and AOL) or other external resources.

3. Sending unsolicited Email messages, including the sending of "junk mail" or other advertising material to individuals who did not specifically request such material (Email SPAM).

4. Any form of harassment via Email, instant messenger, telephone, whether through language, frequency, or size of messages.

5. Unauthorized use, or forging, of Email header information.

6. Solicitation of Email for any other Email address, other than that of the Authorized User’s own account, with the intent to harass or to collect replies.

7. Creating or forwarding Chain email, Phishing, or other scams of any type.

8. Use of the Company’s name in any unsolicited Email on behalf of, or to advertise, any service or product without the explicit written permission of the Company.

9. Posting the same or similar non-business-related messages to large numbers of Usenet newsgroups (newsgroup SPAM).

Enforcement.

Electronic Communications Policy

Purpose.

Electronic communications systems that utilize the Company Information Technology Network are not an open forum, but rather are owned and operated by the Company to communicate inter-company, and to conduct official Company business. Authorized Users may use these systems only within the scope of Company Information Technology Policies and Procedures. Electronic communication systems include, but are not limited to: all electronic mail and Skype Messaging systems, web content, and Internet access.

Scope.

This policy covers appropriate use of any electronic message sent from a Company account, and applies to all Authorized Users of the Company Information Technology Network.

Policy.

Prohibited Use

The Company Email system must not to be used for the creation or distribution of any disruptive or offensive messages may not be used for personal business or personal gain, except as permitted by management

Personal Use

Authorized Users may use a reasonable amount of Company resources for personal Emails. However, non-work related Email shall be saved in a separate folder from work related Email.

Signatures

Signatures in Emails and other electronic messages may contain some or all of the following only: name, title, department name, name of Company, and workplace contact information (phone number, fax number, mailing address, Email address). Quotations, such as proverbs, witticisms, etc., are not allowed in signatures.

Monitoring

Authorized Users of Company accounts shall have no expectation of privacy in anything they store, send or receive in a Company’s Information Technology Network. The IT Administrator may monitor communication on the Company Information Technology Network without prior notice, but is not obliged to do so.

Enforcement.

Any Authorized User found to be in violation of this policy will be considered an Unauthorized User, IT Administrator may suspend any person from using the computing and network facilities and as such are subject to disciplinary action pursuant with the Enforcement section of the Unauthorized Use Policy.

Password Policy

Overview.

Passwords are essential to computer Security. They are the front line of protection for Authorized User accounts. A poorly chosen password can result in the compromise of the entire Company Information Technology Network. All Authorized Users are responsible for taking the actions outlined below, to select and secure their passwords.

Purpose.

The purpose of this policy is to establish a standard for creation and protection of strong passwords for Authorized Users of information technology resources on the Company Information Technology Network. This policy will also establish the frequency of change for those passwords.

Scope.

The scope of this policy includes all Authorized Users who are responsible for an account (or any form of access that supports or requires a password) on any system that resides at any Company facility, accesses the Company Information Technology Network.

Policy.

General

• All system-level passwords (e.g. the "root" account on UNIX-based Operating Systems, the "enable" functionality of Routers, the Windows "administrator" account, application administration accounts, VOIP, etc.) must be changed on at least a quarterly basis.

• All system-level passwords on all equipment must be part of the Company Password Management System.

• All user-level passwords (e.g. Email, web, desktop computer, etc.) must be changed at least every Three month and are to be changes quarterly, by IT Administrator.

• Authorized User accounts that have system-level privileges granted through group memberships or Programs such as “sudo” or “SU” must have a unique password that is different from all other accounts held by that Authorized User.

• Passwords must not be included in Email messages, phone conversations, or other forms of electronic communication.

• All user-level and system-level passwords must conform to the guidelines described below.

Standards

a. General Password Construction Guidelines

Passwords are used for various purposes at the Company. Some of the more common uses include: user-level accounts, Email accounts, screen saver protection, VOIPl passwords, and local Router logins.

Poor, weak passwords have the following characteristics:

• The password contains less than eight characters

• The password is a word found in a dictionary (English or foreign)

• The password is a common usage word, such as:

• Names of family members, pets, friends, co-workers, fictional characters, etc.

• Computer terms and names, commands, sites, companies, Hardware and Software terms

• Birthdays and other personal information, such as addresses and phone numbers

• Word or number patterns like aaabbb, qwerty, xyzzy, 123321, etc.

• Any of the above spelled backwards

• Any of the above preceded or followed by a digit (e.g. secret1, 1secret)

Strong passwords have the following characteristics:

• The password contains both upper and lower case characters (e.g. a-z, A-Z)

• The password has digits and punctuation characters as well as letters, if possible

(e.g. 0-9, !@#$%^&*()_+|~-=\`{}[]:";'<>?,./)

• The password is at least eight alpha-numeric characters long

• The password is not a word in any language, slang, dialect, jargon, etc.

• The password is not based on personal information, names of family, etc.

Passwords must never be written down or stored on-line. Passwords should be created so that they can be easily remembered while still having strong password characteristics. One way to do this is to create a password derived from a song title, affirmation, or other phrase. For example, the phrase might be "This May Be One Way To Remember" and the corresponding password might be "TmB1w2R!", or "Tmb1W>r~", or some other variation.

NOTE: These particular examples are now public, and must not be used as real passwords!

b. Password Protection Standards

Authorized Users must not use the same password for Company accounts as for other non-Company access (e.g. personal ISP account, etc.). Wherever possible, the same password must not be used for various Company access needs. For example, the password for the CARS systems must be separate from the password for other Information Technology systems. Also, a separate password must be selected for a Windows account and a UNIX account.

Company passwords must not be shared with anyone, including administrative assistants or secretaries. All passwords are to be treated as confidential Company information. Groups accounts (an account shared among two or more users) are prohibited.

Users must not do the following:

• Passwords must not be revealed or hinted at over the phone to anyone without proper verification, in an Email message which includes the user name, to any supervisors or co-workers, on questionnaires or Security forms, or to family members.

• The "Remember Password" feature of applications (e.g. Eudora, Outlook, Thunderbird or Netscape Messenger) must not be used.

If someone demands a password, they should be referred to this document or they should call IT personnel.

Again, passwords must not be written down and stored anywhere by the Authorized User. Passwords must not be stored in a file on ANY computer system without Encryption.

If an account or password is suspected to be compromised, the incident must be reported to IT personnel and the password must be changed immediately.

Password Cracking or guessing may be performed on a periodic or random basis by IT personnel. If a password is guessed or cracked during one of these scans, the user will be required to change it.

c. Application Development Standards

Application developers must ensure their Programs contain the following Security precautions:

• Applications must support User Authentication of individual Authorized Users, not groups.

• Applications must not store passwords in clear text or in any easily reversible form.

• Applications must provide for some sort of role management, so that one Authorized User can take over the functions of another without having to know the other's password.

d. Use of Passwords and Pass-phrases for Remote Access Users

Remote Access to the Company Information Technology Network must be controlled using either one-time password authentication or a public / private key system with a strong Pass-phrase.

e. Pass-phrases

Pass-phrases are generally used for public / private key authentication. A public / private key system defines a mathematical relationship between the public key that is known by all, and the private key, that is known only to the Authorized User. Without the Pass-phrase to "unlock" the private key, the Authorized User cannot gain access.

Pass-phrases are not the same as passwords. A Pass-phrase is a longer version of a password and is, therefore, considered more secure. A Pass-phrase is typically composed of multiple words. Because of this, a Pass-phrase is more secure against "dictionary attacks."

A good Pass-phrase is relatively long and contains a combination of upper- and lower-case letters, numerals, and punctuation characters. The following is an example of a good Pass-phrase:

"R34d car3fu!!y. B3 h0n3$t."

All of the rules above that apply to passwords, also apply to Pass-phrases

Enforcement.

Acceptable Encryption Policy

Purpose.

The purpose of this policy is to limit the use of Encryption by Authorized Users to methods that receive substantial work effectively. Additionally, this policy provides direction to ensure compliance with buyer’s regulations, and to ensure legal authority is granted for the dissemination and use of Encryption technologies outside of the Country.

Scope.

This policy applies to all Authorized Users including employees and affiliates.

Policy.

Proven, standard Encryption methods (e.g. DES, Blowfish, RSA, RC5, IDEA, etc.) must be used as the basis for Encryption technologies. These methods represent the actual Cipher used for an approved application. For example, Network Associate's Pretty Good Privacy (PGP) technology uses the IDEA method in combination with RSA or Diffie-Hellman methods, while Secure Socket Layer (SSL) technology uses RSA Encryption. Symmetric Cryptosystem key lengths must be at least 128 bits. Asymmetric Cryptosystem keys must be of a length that yields equivalent strength. Company’s key length requirements are reviewed annually and upgraded as technology allows.

Authorized Users may not use Proprietary Encryption Algorithms for any purpose, unless reviewed by qualified experts outside of the vendor in question and approved by Information Security personnel. Be aware that the export of Encryption technologies is restricted by the U.S. Government. Residents of countries other than the United States need to be aware of the Encryption technology laws of the country in which they reside.

Enforcement.

Remote Access Policy

Purpose.

This policy defines standards for connecting to the Company Information Technology Network from any Host. These standards are designed to minimize potential exposure of the Company to damages that result from Unauthorized Use of the Company Information Technology Network. Damages include, but are not limited to: the loss of sensitive or confidential data, loss of Intellectual Property, damage to the Company’s VOIP Communication, damage to the Company’s internal systems, and financial damages of all kinds.

Scope.

This policy applies to all Authorized Users including Company staff, employees and affiliates, who utilize Company-owned or personally-owned information technology resources to connect such devices to the Company Information Technology Network. This policy applies to Remote Access connections used to do work on behalf of the Company, including but not limited to Email correspondence and accessing Intranet web resources.

Remote Access implementations that are covered by this policy include, but are not limited to: dial-up Modems, Frame Relays, Integrated Services Digital Network (ISDN) connections, Digital Subscriber Line (DSL) connections, Cable Modems, etc.

Policy.

General

1. Authorized Users with Remote Access privileges to the Company Information Technology Network must ensure that their Remote Access connection complies with the Company Information Technology Policies and Procedures, and treat it with the same consideration as their on-site connection to the Company.

2. General access to the Internet through the Company Information Technology Network is not permitted.

3. Authorized Users must review the following policies to determine how to protect information when accessing the Company Information Technology.

Network via Remote Access methods, and for acceptable use of the Company Information Technology Network:

a. The Company Acceptable Encryption Policy

b. The Company Team Viewer/VNC Policy

c. The Company Wireless Communications Policy

d. The Company Acceptable Use Policy

4. For additional information regarding the Company's Remote Access connections, Authorized Users should contact the Information Technology Department.

Requirements

1. Secure Remote Access must be strictly controlled. Control will be enforced via one-time password authentication or public / private keys with strong Pass-phrases. For information about how to create a strong Pass-phrase, Authorized Users should refer to the Password Policy.

2. Authorized Users must not provide their login identification to the Company Information Technology Network or its resources to anyone, not even family members.

3. Authorized Users who, as a Company employee or affiliates with Remote Access privileges, must ensure that Company-owned or personal information technology resources are not connected to any other Network at the same time they are connected to the Company Information Technology Network (with the exception of personal Networks that are under the complete control of the Authorized User).

4. Authorized Users who, as a Company employee or affiliates with remote Authorized User access privileges to the Company Information Technology Network must not use non-Company Email accounts (e.g. Hotmail, Yahoo, and AOL) or other external resources to conduct Company business, thereby ensuring that official business is never confused with personal business.

5. Routers for dedicated ISDN lines configured for access to the Company Information Technology Network must meet the minimum authentication requirements of the Challenge Handshake Authentication Protocol (CHAP).

6. Reconfiguration of an Authorized User’s home equipment for the purpose of Split-Tunneling or Dual Homing is not permitted.

7. Frame Relay must meet the minimum authentication requirements of Data-Link Connection Identifier (DLCI) standards.

8. Non-standard Hardware configurations must be approved by Information Technology personnel, and Information Technology personnel must approve Security configurations for access to Hardware.

9. All Hosts that are connected to the Company Information Technology Network via Remote Access technologies, including personal computers, must use the most recent corporate-standard Anti-Virus Software. Third-party connections to the Company Information Technology Network must comply with requirements as stated in the Third Party Agreement Documentation.

10. Personal equipment that is used to connect to the Company Information Technology Network must meet the same requirements applied to Company-owned equipment for Remote Access.

11. Organizations or Authorized Users who wish to implement non-standard Remote Access solutions to the Company Information Technology Network must obtain prior written approval from the Information Technology Department.

Enforcement.

Physical Security Policy

Overview.

Physical Security means providing environmental safeguards for, and controlling physical access to, equipment and data on the Company Information Technology Network in order to protect information technology resources from Unauthorized Use, in terms of both physical Hardware and data perspectives.

Purpose.

The purpose of this policy is to establish standards for granting, monitoring, and terminating physical access to the Company Information Technology Network and to protect equipment on the Company Information Technology Network from environmental factors.

Scope.

This policy applies to the entire Company Information Technology Network, including but not limited to Finger Print/Door lock Network, CCTV Network, and the Information Technology Services Network Operations Center.

Policy.

Environmental Safeguards

1. Adequate air conditioning must be operational in Company Information Technology Network facilities that house information technology resources, to prevent long-term heat damage and equipment failure.

2. All Company Information Technology Network facilities must have adequate fire extinguishing devices present in the office area. These devices must be inspected by Company General Affair/Compliance personnel.

3. All Company Information Technology Network information technology resources must be fitted with effective Surge Protectors to prevent power spikes and subsequent damage to data and Hardware.

4. Critical Company Information Technology Network information technology resources must each be connected to an Uninterrupted Power Supply (UPS) in order to prevent power spikes, brownouts, and subsequent damage to data and Hardware.

5. Electrical outlets must not be overloaded by connecting too many devices. Proper and practical usage of extension cords are to be reviewed annually.

Physical Access

1. All Company Information Technology Network physical Security systems must comply with all regulations, including, but not limited to, building codes and fire prevention codes.

2. Physical access privileges to all Company Information Technology Network facilities must be documented and managed by Information Technology Department.

3. All facilities that house Company Information Technology Network information technology resources must be physically protected in proportion to the importance of their function.

4. Access to Company Information Technology Network restricted facilities will be granted only to Company staff and affiliates whose job responsibilities require access to that facility.

5. The process for granting card or key access to Company Information Technology Network facilities must include approval from the Company Manager of Information Technology.

6. Secured access devices (e.g. access cards, keys, combinations, etc.) must not be shared with or loaned to others by Authorized Users.

7. Secured access devices that are no longer needed must be returned to the Information Technology department, and logged appropriately before they are re-allocated to another Authorized User.

8. Lost or stolen Company Information Technology Network secured access devices must be reported to Information Technology personnel immediately.

9. The Company Employees responsible for Company Information Technology Network facilities must remove the secured access device rights of individuals that no longer require access.

10. Company Visitors and other invitees must be escorted and monitored while in restricted Company Information Technology Network facilities.

11. Company Employees responsible for Company Information Technology Network facilities must review access records and visitor Logs for the facility on a periodic basis, and investigate any unusual access.

12. All spaces housing information technology resources must be kept locked when not occupied by a Company Employee, in order to reduce the occurrence of unauthorized entry and access.

5. Enforcement.

Workstation Configuration Security Policy

Purpose.

The purpose of this policy is to establish standards for the base configuration of workstations that are owned or operated by the Company. Effective implementation of this policy will minimize unauthorized access to the Company Information Technology Network and other Proprietary Information and technology.

Scope.

This policy applies to all Company Information Technology Network workstation equipment owned or operated by the Company, and to workstations registered under any Company-owned internal Network domain.

Policy.

Ownership and Responsibilities

All Company Information Technology Network workstations at the Company must be the responsibility of an operational group that is responsible for system administration. Approved workstation configuration standards must be established and maintained by IT Administrator. IT Administrator must monitor configuration compliance and request special approval for any noted exceptions.

1. Workstations must be registered within the Company IT Management System. At a minimum, the following information is required to positively identify the point of contact:

a. Workstation location

b. Hardware and Operating System (OS) version numbers

c. Main functions and applications, if applicable

2. Information in the Company Management System must be kept current.

General Configuration Standards

1. OS configuration must comply with approved Information Technology Standards.

2. Services and applications that are unused must be disabled where practical. Exceptions must be noted and approved by authorized Information Technology personnel.

3. Access to Services must be protected through authorized access-control methods (e.g. TCP wrappers), if possible.

4. The most recent Security Patches must be installed on the system as soon as practical, the only exception being when immediate application would interfere with business requirements.

5. Trust Relationships between systems constitute a Security risk, and their use should be avoided and should not be used when another method of communication will suffice.

6. The standard Security principle of Least Required Access must be utilized when performing a function.

7. If a methodology for Secure Channel connection is available (i.e. technically feasible), privileged access must be performed over Secure Channels (e.g. encrypted Network connections using IPSec or Secure Shell).

Monitoring

Security-related events must be reported to appropriate Information Technology personnel, who review Logs and report incidents to IT Administrator. Corrective measures are prescribed as needed. Security-related events include (but are not limited to):

1. Port scan attacks

2. Evidence of unauthorized access to privileged accounts or data

3. Anomalous occurrences that are not related to specific applications on the Host

Compliance

1. Audits are performed on a regular basis by authorized parties within the Company.

2. Audits are managed by the Company’s appropriate Information Technology personnel, in accordance with the Compliance Policy documentation. Findings not related to a specific operational group are filtered by Information Technology personnel, and then presented to the appropriate support staff for remediation or justification.

3. Reasonable efforts are made to prevent audits from causing operational failures or disruptions.

4. Enforcement.

Server Configuration Security Policy

Purpose.

The purpose of this policy is to establish standards for the base configuration of server equipment that is owned or operated by the Company. Effective implementation of this policy will minimize Unauthorized Use of the Company Information Technology Network or other access to the Company’s Proprietary Information and technology.

Scope.

This policy applies to server equipment owned or operated by the Company, and to servers registered under any Company-owned internal Network domain.

This policy applies specifically to equipment connected to the internal Company Information Technology Network. For secure configuration of equipment external to the Company on the “De-Militarized Zone” (DMZ), refer to the Company ”De-Militarized Zone” Equipment Policy documentation.

Policy.

Ownership and Responsibilities

All internal servers deployed at the Company must be the responsibility of an system administration. Approved server configuration standards must be established and maintained by IT Manager, based on business needs. IT Administrator must monitor configuration compliance and request special approval for any noted exceptions. IT Administrator must establish a process for changing the configuration standards, which includes review and approval by Information Security personnel.

1. Servers must be registered within the Company Security Management System. At a minimum, the following information is required to positively identify the point of contact:

a. Server location.

b. Hardware and Operating System (OS) version numbers

c. Main functions and applications, if applicable

2. Information in the Company Security Management System must be kept current.

3. Configuration changes made by Authorized Users for operational servers must comply with the Change Management Policy documentation.

General Configuration Standards

1. OS configuration must be in accordance with approved Information Security Standards.

2. Services and applications that are unused must be disabled where practical. Exceptions must be noted and approved by Information Technology Admin.

3. Access to Services must be logged or protected through appropriate Access Control methods (e.g. TCP wrappers), if possible.

4. The most recent Security Patches must be installed on the system as soon as practical, the only exception being when immediate application would interfere with business requirements.

5. Trust Relationships between systems are a Security risk, and their use should be avoided. Do not use a Trust Relationship when some other method of communication will do.

6. Authorized Users must always use the standard Security principle of Least Required Access to perform a function.

8. All servers must be physically located in an access-controlled environment.

9. Authorized Users are specifically prohibited from operating servers in uncontrolled office areas.

Monitoring

1. All Security-related events on critical or sensitive systems must be logged by Information Technology personnel saved as follows:

a. All Security-related Logs must be kept online as required in the specific server standards document.

b. Daily incremental tape Backups must be retained as required in the specific server standards document.

c. Weekly full tape Backups of Logs must be retained as required in the specific server standards document.

d. Monthly full Backups must be retained as required in the specific server standards document.

2. Security-related events must be reported by Authorized Users to Information Technology Administrator, who review Logs and report incidents to IT Manager department. Corrective measures are prescribed as needed.

Security-related events include, but are not limited to:

a. Port scan attacks

b. Evidence of unauthorized access to privileged accounts or data

c. Anomalous occurrences that are not related to specific applications on the Host

Compliance

1. Audits must be performed on a regular basis by authorized parties within the Company.

2. Audits must be managed by Compliance department or Information Technology personnel, in accordance with the Audit Policy documentation.

3. Every effort will be made to prevent audits from causing operational failures or disruptions.

Enforcement.

“De-Militarized Zone” Network Equipment Policy

Purpose.

Company information technology resources that connect directly to the Internet are considered part of a "De-Militarized zone" (DMZ) on the Company Information Technology Network. These resources are particularly vulnerable to attack since they are directly accessible from the Internet.

The purpose of this policy is to articulate standards that govern the use of all Company Information Technology Network information technology resources, which are located within a Company DMZ Network. These standards are designed to minimize the exposure of the Company from the loss of sensitive or confidential data, Intellectual Property, damage to the Company’s public image, etc., which may result from Unauthorized Use of Company Information Technology Network information technology resources.

The policy defines the following standards:

• Operational Group responsibility

• Secure configuration requirements

• Operational requirements

• Change control requirements

Scope.

All Company Information Technology Network information technology resources deployed in a DMZ owned or operated by the Company, including but not limited to servers, Routers, or switches, must be operated in accord with this policy. Additionally, all information technology resources registered in any Domain Name System (DNS) domain owned by the Company are subject to this policy. Any devices outsourced or hosted at third-party service providers, if said information technology resources reside in the "domain.co.id" domain or appear to be owned by the Company, are also subject to this policy.

All new Company Information Technology Network equipment that is subject to this policy must be configured according to the applicable configuration documents, unless a waiver is obtained from Company Information Technology personnel. All existing and future Company Information Technology Network equipment deployed on a Company DMZ Network must comply with this policy.

Policy.

Ownership and Responsibilities

Company Information Technology Network equipment and applications within the scope of this policy must be administered by the Information Technology department, and be approved by authorized Information Technology personnel for DMZ-level management of the relevant system, application, or Network access.

The Information Technology Services department is responsible for the following:

1. Documenting equipment in the Company Security Management System, recording at least the following information:

a. Host contacts and location

b. Hardware and Operating System version numbers

c. Main functions and applications

d. Password groups for privileged passwords

2. Assuring that Company Information Technology Network interfaces have appropriate DNS records (minimum of A and PTR records).

3. Assuring that password groups are maintained in accordance with the Company Password Management System and the Password Policy.

4. Assuring that immediate access to Company Information Technology Network equipment and system Logs is granted to Information Security personnel upon demand, in accordance with the Audit Policy.

5. Assuring that changes to Company Information Technology Network existing equipment and deployment of new equipment comply with the Company Change Management System and comply with the Change Management Policy.

To verify compliance with this policy, Company Information Security personnel periodically perform an audit on DMZ equipment as set forth in the Audit Policy.

General Configuration Policy

All Company Information Technology Network equipment must comply with the following configuration policy:

1. Hardware, Operating Systems, Services and applications must be approved by Company Information Technology personnel, as part of the pre-deployment review phase.

2. Operating System configuration must be done in accord with the secure server and Router installation and configuration standards, as defined in the Server Configuration and Workstation Configuration policy.

3. All Patches and updates recommended by the equipment vendor and Information Technology personnel must be installed. This applies to all Services installed, even though those Services may be temporarily or permanently disabled. Operational Groups must have processes in place to stay current on appropriate Patches and updates.

4. Services and applications not serving business requirements must be disabled.

5. Trust Relationships between systems may only be introduced according to business requirements, must be documented, and must be approved by Company Information Technology personnel.

6. Services and applications not for general access must be restricted by Access Control Lists.

7. Insecure Services or Protocols (as determined by Company Information Technology personnel) must be replaced with more secure equivalents whenever such exist.

8. Remote administration must be performed over Secure Channels (e.g. encrypted Network connections using Secure Shell) or Console Access independent from a DMZ Network.

9. All server content updates must occur over Secure Channels.

10. Security-related events must be logged and audit trails saved to Logs approved by Company Information Technolgy personnel. Security-related events include, but are not limited to, the following:

a. User login failures

b. Failure to obtain privileged access

c. Access policy violations

New Company Information Technology Network Installations and Change Management Procedures

All new installations and changes to the configuration of existing Company Information Technology Network equipment and applications must comply with the following standards:

1. New installations must be done in compliance with the DMZ Equipment Deployment Process.

2. Configuration changes must comply with the Company Change Management Policy.

3. Information Security personnel must be notified to perform system or application audits prior to the deployment of new Services.

4. Information Security personnel must be engaged, directly or in accordance with the Company Change Management System, to approve all new deployments and configuration changes.

Company Information Technology Network Equipment Outsourced to External Service Providers

The responsibility for the Security of Company Information Technology Network information technology resources deployed by external service providers must be articulated in the contract with the service provider and must include Security contacts. Escalation procedures must also be documented. Contracting Company departments are responsible for the third-party organization’s compliance with this policy.

Enforcement.

Router Security Policy

Purpose.

This document describes a required minimal Security configuration for all Routers and switches connected to the Company Information Technology Network or used in a production capacity on behalf of the Company.

Scope.

All Network infrastructure devices connected to the Company Information Technology Network are subject to this policy.

Policy.

Every Router must meet the following configuration standards:

1. The Router must have no local user accounts configured. Routers must use the Terminal Access Controller Access Control System (TACACS+) Protocol for User Authentication.

2. The “enable” and “secret” passwords on the Router must be kept in a secure encrypted form. The Router must have the “enable” and “secret” passwords set to the current production Router passwords provided by the Information Technology Services department.

3. The following are prohibited:

a. IP directed broadcasts

b. Incoming packets at the Router sourced with invalid addresses (e.g. RFC1918 addresses)

c. TCP small Services

d. UDP small Services

e. All source Routing

f. All web Services running on Router

4. Company standardized Simple Network Messaging Protocol (SNMP) community strings must be used.

5. Information Technology Services has the authority to, and will add, rules to the Access Control List as business needs arise.

6. The Router must be included in the Company Security Management System with a designated point of contact.

7. Each Router must have the following statement posted in clear view:

"UNAUTHORIZED ACCESS TO THIS NETWORK DEVICE IS PROHIBITED. Users must have explicit permission from Company’s Information Security to access or configure this device. All activities performed on this device may be logged, and violations of this policy may result in disciplinary action, and may be reported to law enforcement. Authorized Users who utilize this device have no right to privacy.

Enforcement.

Wireless Communication Policy

Purpose.

This policy defines the standards that govern the use of wireless communication equipment to access the Company Information Technology Network.

Scope.

This policy covers all wireless data communication devices, including, but not limited to, personal computers, cellular phones, and wireless access points (WAPs) connected to the Company Information Technology Network. This includes any form of wireless communication device capable of transmitting packet data. Wireless devices or Networks that do not connect to the Company Information Technology Network are not subject to this policy.

Policy.

Use of Wireless Equipment

Authorized Users may only access the Company Information Technology Network via wireless systems that meet the criteria set forth in this policy, unless they have been granted a written waiver by Information Technology personnel.

Corporate WIFI use for the Staff only, and for the guess or visitor is connected to Service Set Identifier (SSID) Company public WIFI.

Register Access Points and Cards

All WAPs and base stations connected to the Company Information Technology Network must be registered with and approved by Information Technology personnel. Use of these devices by Authorized Users subjects the devices to periodic penetration tests and audits by Information Security. All Wireless Network interface cards used in resources owned by the Company must be registered with the Information Technology Services department.

Approved Technology

All wireless Local Area Network (LAN) access must use vendor products and Security configurations approved by Information Technology personnel before being connected to the Company Information Technology Network.

Enforcement.

Change Management Policy

Purpose.

This policy describes a systematic process to document and manage changes to the Company Information Technology Network in order to permit effective planning by the Company Information Technology Services to serve the Company user-base.

Scope.

This policy applies to all Authorized Users that install, maintain, or operate Company information technology resources, including, but not limited to: computer Hardware, Software, and Networking devices.

Policy.

Any change to a Company Information Technology Network information technology resource is subject to this policy, and must be performed in compliance with the Company’s Change Management Procedure.

All changes affecting Company Information Technology Network computer-based environmental facilities, including but not limited to electricity, and alarms, must be reported to or coordinated with the Information Technology department.

A formal written change request must be submitted to the Information Technology department for all changes, both scheduled and unscheduled.

All scheduled change requests and supportive documentation must be submitted in compliance with the Change Management Procedure. The request will then be reviewed by the Management, and a decision will be made whether to allow or delay the request.

The Management may deny a scheduled or unscheduled change for reasons that include, but are not limited to, the following: inadequate planning, inadequate reversion plans, negative impact of change timing on a key business process, or inadequate resource availability.

Customer notification must be completed for each scheduled or unscheduled change, in compliance with the Change Management Procedure documentation.

A Change Review must be completed for each change to the Company Information Technology Network, whether scheduled or unscheduled, successful or not.

A Change Management Log must be maintained for all changes. The Log must contain (but is not limited to):

• Date of submission

• Requestor of change

• Date of change

• Implementer of change

• Nature of the change

• Results of the change

Enforcement.

Information Security Audit Policy

Purpose.

Information Technology personnel utilize various methods to perform electronic scans of the Company’s Networks and Firewalls, or on any system connected to the Company Information Technology Network.

Information Security personnel are authorized to conduct audits to:

• Ensure integrity, confidentiality and availability of information and resources

• Investigate possible Security incidents

• Ensure compliance to Company Information Technology Policies and Procedures documentation

• Monitor Authorized User or system activity where appropriate

Scope.

This policy covers all computer and communication devices owned or operated by the Company. This policy also covers any computer and communications device that are connected to the Company Information Technology Network, but which may not be owned or operated by the Company. Information Security personnel will not perform Denial of Service or other disruptive activities.

Policy.

Authorization to Audit

Only Information Technology personnel or other specifically authorized parties may audit devices that are owned by the Company or are connected to the Company Information Technology Network. Third-party organizations may only perform audits with the explicit written permission of the Information Technology department.

Access

Information Technology personnel shall be granted access to the following in order to effectively perform audits:

• User level or system level access to any computing or communications device

• Access to information (electronic, hardcopy, etc.) that may be produced, transmitted or stored on the Company Information Technology Network.

• Access to work areas

• Access to interactively monitor and Log traffic on the Company Information Technology Network

Enforcement.

HOW TO install java plugin on Linux o/s

2019-12-22T19:57:00.000-08:00

Install Java Plugin

1. Test Keberadaan Java dalam system dan menghapus karena menginstall lewat Yum (lakukan lewat RPM) : (perintah dibawah)

    [pietermarbun@pieter-desktop]#rpm -q jre

    jre-1.6.0-fcs

    [pietermarbun@pieter-desktop]#rpm -e jre

2. Download the Java package dari:
http://java.sun.com/javase/downloads/index.jsp

3. Select: Java Runtime Environment (JRE) 6 Update 3 (the JDK adalah untuk developers)

4. Pada Halaman berikut, accept the license agreement, dan pastikan memilih berikut:

    Linux self-extracting file        jre-6u3-linux-i586.bin      18.23 MB

5. To install:

    [pietermarbun@pieter-desktop]#sh jre-6u3-linux-i586.bin

    (hit 'space' till the end, then type 'yes')

    [pietermarbun@pieter-desktop]#mv -f jre1.6* /opt/jre1.6

[pietermarbun@pieter-desktop]#ln -s /opt/jre1.6/plugin/i386/ns7/libjavaplugin_oji.so /usr/lib/mozilla/plugins/libjavaplugin_oji.so

Note: The compat-libstdc++-33 compatibility libraries dibutuhkan browser plugin untuk aktif

To update: Jika untuk update JRE package, simple delete the /opt/jre1.6 directory dan copy download terbaru ke /opt/jre1.6 – tidak perlu menjalankan 'ln -s' command.

Controlling Java lewat 'alternatives'. Ketika running Java Command, Fedora akan otomatis mengunakan GNU Java, untuk menggunakan Sun's java Lakukan hal berikut:

[pietermarbun@pieter-desktop]#/usr/sbin/alternatives --install /usr/bin/java java /opt/jre1.6/bin/java 2

[pietermarbun@pieter-desktop]#echo 2 | sudo /usr/sbin/alternatives --config java

[pietermarbun@pieter-desktop]#java -version

java version "1.6.0_03"

Java(TM) SE Runtime Environment (build 1.6.0_03-b05)

Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing)

BRIA apps - VOIP for Unified Communications & Collaboration

2019-12-19T20:00:00.000-08:00

BRIA is SIP trunking makes it easy to connect your existing PBX system to the world in minutes.

STEP BY STEP BRIA PROFFESIONAL INSTALLATION:

Extract file :

counterpath.bria.professional.v2.4.3.50906.retail.incl.keymaker-zwt.rar (you can get this file from counterpath web)

go to the file and start for installation with enter the setup file

step 1

step 2

step 3

step 4

step 5

step 6

step 7

step 8

step 9

SETTING BRIA SIP Account :

setting 1

setting 2

setting 3

You can add 2 or more SIP account on the system and make sure to make enable the account with checklist mark then apply.

setting 4

That's it, now you can use your Bria as your PBX client.

Qemu Guide

2019-12-18T22:21:00.000-08:00

QEMU quick start guide

1. QEMU quick start guide

1. Windows guest on Linux host

2. Linux guest on Windows host

This page is intended as quick start guide for people who want to use QEMU to install

• Windows guest on Linux host

• Linux guest on Windows host

QEMU is a virtual machine program. So, that's a machine in the machine. There is a computer, called host, which runs an OS, called host OS, and QEMU (besides other programs). Inside QEMU, there runs an OS, called guest OS. QEMU is a simple program ("exe") from the host point of view.

While QEMU is able to handle different host and guest architectures like PPC, ARM or MIPS (not complete), this quick start guide only covers x86 where host and guest architectures are the same. To emulate a guest x86 machine on a host x86 we use QEMUs Full System Emulation mode.

Windows guest on Linux host

1. Download QEMU Binary distribution for linux-i386 and install it. Installation is simply done by extracting the contents of the tar archive in root directory ("/"). It will extract its contents to /usr/local/bin and /usr/local/share.

2. You need a blank disk image ("harddisk"). This is like adding a blank disk to the virtual computer that QEMU creates. Use qemu-img to create a 3Gb blank disk image:

qemu-img create -f qcow c.img 3G

The last argument is the size of the image (3G). This 3G will be the maximum end size of the image file. It will grow while adding contents (writing files to the harddisk). A fresh WinXP installation will use e.g. ~1.7Gb. For more information on creating a blank image see Disk Images.

3. When you install an OS on a real computer you normally boot an installation CD/DVD or an existing image. We'll do the same with the virtual computer. Here you have two options: Either you use a real installation CD/DVD or you have an install ISO image. Depending on this, the next steps are slightly different.

* If you have an installation CD, put the CD (e.g. Windows installation CD) into the real CD drive of your host computer. Then run

qemu -cdrom /dev/cdrom -hda c.img -m 256 -boot d

* Suppose you have an install ISO image , called my_os_install.iso. Then run

qemu -cdrom my_os_install.iso -hda c.img -m 256 -boot d

Both will run the virtual machine. It will have two drives, the primary master (/dev/hda) is the 3G image (-hda c.img). The secondary master is that cdrom or cdrom image. Note that (from the host point of view) those are still two plain files (in case of iso image). But from the guest OS (running in the VM), those are real drives. Boot is done from secondary master (-boot d) using 256MB of RAM (-m 256) using c.img as "hardisk" (image).

Note: If -m 256 or more fails (depends on your PC configuration) it will explain what to do.

So, the virtual machine is started. It shows a window in the monitor like on a real hardware. Now you can install the client OS just as you would in a real computer. First you probably need to create partitions, format them, run installer to copy files, and so on. If it needs to reboot the guest, feel free to do that, Qemu will not stop working.

If you don't like windowed mode, you can use special keys. Press ctrl-alt-f to go fullscreen. When you'd like to use your host OS, press ctrl-alt to release mouse grab or try seamless mouse. You can return to the VM any time.

When you stop guest OS, and the virtual machine halts, QEMU exits. But the image file (c.img) is modified (the guest OS remains on that), so, you don't have to reinstall it every time. So, if you have installed the client OS shutdown it as you will do with your real computer. You will then note that the image file (here c.img) will have increased dramatically. You can now start the system you just installed by booting from the "hardisk" (c.img):

qemu -hda c.img -m 256

If you want, you can compress c.img to backup, or do anything. Note that closing the VM window while guest OS is running is like unplugging the computer. It might complain next time

4. If you have basic system up and running, you may want to add sound and correct local time.

qemu -hda c.img -m 256 -soundhw sb16 -localtime

-soundhw sb16

just like putting a soundblaster card into the slot

-localtime

in case the host OS runs in local time (and not GMT)

-net nic -net user option is not necessary here because it is enabled by default if no -net option is specified. This is, by default, "user mode" (user-net) networking, which is the simplest way to reach internet from inside. It just works (getting IP address from DHCP automatically)

If you call QEMU without any parameters, it will show its possible parameter list.

At runtime QEMU itself can be controlled by QEMU Monitor.

5. To increase emulation speed, you would like to install QEMU Accelerator (KQEMU). Download latest QEMU Accelerator Module and follow KQEMU Compilation and kqemu installation.

If you start QEMU now, it will probably run significantly faster. Try -kernel-kqemu option as well.

To check if everything is okay, use QEMU Monitor command info kqemu:

(qemu) info kqemu

kqemu support: enabled for user and kernel mode

With this, your final command line to start QEMU with installed image (c.img) may now be

qemu -hda c.img -m 256 -kernel-kqemu

(plus additional options like above i.e. for sound or localtime)

6. This guide tries to give you some basic ideas how to start with QEMU and to explain some first steps to get you up with QEMU on Linux quickly. There are several areas for additional configuration (i.e. additional drives, further network, data exchange between host and guest, overlay images, VNC etc.) which are not covered here. For this, go on reading resources given in Documentation.

Acknowledgements

The text in this section was mainly taken from

• Daniel Carreras post to QEMU developer list.

• NyOS' post to QEMU developer list.

Links

• For a more detailed guide see QemuOnLinux

Formatting Dates in MySql

2019-12-16T02:34:00.004-08:00

When you want to format dates stored in a MySQL database to output onto your web pages, you have a choice; either do it with PHP or do it directly in the MySQL query itself.

I usually do it in the MySQL query itself; unless I have a very good reason not to - which is rare.

MySQL Date and Time types

Out of the many Date and Time types supported in MySQL, we will only discuss the one I use 95% of the time in my MySQL tables i.e. TIMESTAMP. Most people use this type and it's good enough for most of your needs and even transaction recording. I will elaborate on the different DATE and TIME types in a future article perhaps but for now we are using TIMESTAMP, okay?

Sample data and table

code:

TABLE: tbl_messages

==================================

msg_id |msg_time |poster_id

--------+---------------+---------

1 |20020922230743 | 1

2 |20020923010930 | 2

3 |20020924223015 | 1

4 |20020926151515 | 1

5 |20020930001504 | 1

Looking at the sample table above, we already note that the column type for msg_time is TIMESTAMP(14).

Introducing DATE_FORMAT()

To help illustrate the uses of MySQL's DATE_FORMAT(), I will list below the different syntax and results for one particular row off our sample table for each situation.

Output date as: "Sep 23rd, 2002 at 01:09:30 hrs"

php:

<?php

$sql = "SELECT DATE_FORMAT(msg_time,'%b %D, %Y at %T hrs')

FROM tbl_messages

WHERE poster_id=2";

// returns "Sep 23rd, 2002 at 01:09:30 hrs"

// %b = MONTH Text in 3 characters

// %D = Numeric DAY in the month with suffix (e.g. 1st,2nd,3rd etc)

// %Y = 4 digit YEAR

// %T = TIME, 24 hour format

Output date as: "Monday, 23-09-02"

php:

<?php

$sql = "SELECT DATE_FORMAT(msg_time,'%W, %d-%m-%y')

FROM tbl_messages

WHERE poster_id=2";

// returns "Monday, 23-09-02"

// %W = WEEKDAY Text full

// %d = Numeric DAY in the month with leading 0

// %m = Numeric MONTH with leading 0

// %y = 2 digit YEAR

Output date as: "September 23, 2002 - 01:09 AM"

php:

<?php

$sql = "SELECT DATE_FORMAT(msg_time,'%M %e, %Y - %h:%i %p')

FROM tbl_messages

WHERE poster_id=2";

// returns "September 23, 2002 - 01:09 AM"

// %M = MONTH full text

// %e = Numeric DAY in the month, no leading 0

// %Y = 4 digit YEAR

// %h = 12 HOUR clock with leading 0

// %i = MINUTES, numeric with leading 0

// %p = AM/PM

There are more formatting codes besides the ones listed in the sample queries above but you'd have to seek them out at the MySQL site yourself. ;)

Setting up software RAID

2019-12-06T00:51:00.001-08:00

This should be a relatively straightforward way of setting up your whole system to use RAID. This info was taken from two howtos:

Software-RAID HOWTO^*
Boot+Root+Raid+Lilo HOWTO^*

Remember that this only makes sense after you've done it once... :)
Test PC:
PII-350, 384Mb RAM, and Adaptec 2940U2 SCSI controller, and 3 18Gb Seagate drives.
Test Mac:
Blue & White G3, 256MB RAM, Adaptec 2940 SCSI controller, 3 8GB SCSI drives.
These instructions have been tested on various flavors of OpenLinux, Red Hat, Mandrake, and now Yellow Dog Linux for PowerPC.
IMPORTANT NOTE: According to the howtos, if you're going to use IDE drives for this, you should only have one driver per channel. Slave drives will kill the performance of the RAID, so factor the purchase of a couple of IDE controllers into your equations. I have personally tested the Promise UDMA-100 cards in a RAID configuration, and they work very well.
RAID-5 requires 3 hard drives of the same size, so you should install those and make sure they work before starting this process.
General Partitioning notes:
Since RAID-5 isn't supported by most installers, you must first install Linux to one of the drives. Later on we'll convert that drive to become a part of the RAID. If you have at least 128MB RAM skip the swap partitions. We'll create a swapfile on the RAID later so that if a drive dies the box won't crash. Don't split the mount points up among partitions as you normally would. Put '/' on one of the large Linux partitions and leave the small 50Mb partitions and the large Linux partitions on the other 2 drives empty. To make our job easier later, create two 50Mb partitions at the front of the first 2 drives and leave those partitions empty for now.
Mac partitioning notes:
You may see lots of strange Apple partitions on your disk. As long as you're not dual-booting with MacOS go ahead and delete them. It won't hurt anything, and you can always put them back later with Apple's disk utilities.
IMPORTANT: Don't delete partition 1! The first partition of a Mac disk is the partition table, so that would cause all kinds of havoc.
In addition to the Linux partitions, allocate a 10MB Yaboot boot partition at the beginning of the first two disks. This is where your bootloader will go.
My PC partition structure looks like:

/dev/sda1 - 50Mb, Linux, empty
/dev/sda2 - 17Gb, Linux, /
/dev/sdb1 - 50Mb, Linux, empty
/dev/sdb2 - 17Gb, Linux, empty
/dev/sdc1 - 17Gb, Linux, empty

My Mac partition structure looks like:

/dev/sda1 - Apple partition map
/dev/sda2 - 10MB, Apple Bootstrap
/dev/sda3 - 50MB, Linux, empty
/dev/sda4 - 8GB, Linux, /
/dev/sdb1 - Apple partition map
/dev/sdb2 - 10MB, Apple Bootstrap
/dev/sdb3 - 50MB, Linux, empty
/dev/sdb4 - 8GB, Linux, empty
/dev/sdc1 - Apple partition map
/dev/sdc2 - 8GB, Linux, empty

After installing Linux to the first large partition, the next step toward a complete RAID-5 system is to recompile the kernel. Most distributions ship their SCSI support as modules. This is normally a good thing, but not if you want to load from a RAID device. That means we're recompiling. If you're using SCSI devices, make sure you include SCSI support, SCSI hard disk support, the driver for your SCSI controller in the kernel and not as modules. For IDE devices, include IDE support, IDE disk support, and support for your controller if needed (Promise cards have their own driver for example). Also, whatever filesystem your Linux drives are must be compiled in (ext2, ext3, ReiserFS, etc). I'll be using Reiserfs for this example. Make sure you turn off the extra checking option or Reiserfs can be really slow.
Mac Kernel Notes:
You'll need a recent PPC kernel for this to work on a Mac. These are available at www.ppckernel.org. I used 2.4.20-benh10. You'll also need a new version of Yaboot, available at penguinppc.org. I used 1.3.10. If you're accustomed to building kernels on Intel you generally use 'make bzImage' as your final step. Unfortunately compressed kernels aren't supported on PPC, so you'll have to use 'make vmlinux' instead.
Once the recompile is complete, move the kernel into place and edit grub/lilo/yaboot accordingly. Then reboot and check that all your hardware is seen.
Now we'll create the /etc/raidtab file that will configure your RAID devices. On the PC this should contain the following:

raiddev /dev/md0
raid-level 5
nr-raid-disks 3
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
chunk-size 32
device /dev/sdb2
raid-disk 1
device /dev/sdc1
raid-disk 2
device /dev/sda2
failed-disk 0
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 32
device /dev/sda1
raid-disk 0
device /dev/sdb1
raid-disk 1

On the Mac:

raiddev /dev/md0
raid-level 5
nr-raid-disks 3
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
chunk-size 32
device /dev/sdb4
raid-disk 1
device /dev/sdc2
raid-disk 2
device /dev/sda4
failed-disk 0
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 32
device /dev/sda3
raid-disk 0
device /dev/sdb3
raid-disk 1

This sets up /dev/md0 as our large RAID-5 array which will contain our root ('/') filesystem. But what does all that mean?

raiddev /dev/md0 - specifies that we're creating raid device /dev/md0
raid-level 5 - specifies that this is a RAID-5 array
nr-raid-disks - specifies the number of *active* disks in the array
nr-spare-disks - specifies the number of spare disks in the array (spare disks are used automagically if an active disk fails)
persistent-superblock 1 - puts a block on each RAID device that contains info about its position in the array (among other things). Ever wonder what happens if you physically re-arrange drives in the array by accident, or switch a cable to the wrong drive? Without this, the array wouldn't know and would go to pieces. On the PC this also allows booting from the array, which we'll get to later.
parity-algorithm left-symmetric - specifies the algorithm used to spread the parity info among multiple disks. Don't ask me how it works, I haven't a clue.
chunk-size 32 - specifies the chunk size the array writes in. this has an affect on performance, but since I don't understand all that too well I just use what the docs recommended.
device /dev/sdxx - specifies the device name of each partition to be included in the array.
raid-disk x - specifies a unique number assigned to each device in the array.
failed-disk x - specifies a device that is in a failed state. In this case, we specify our current non-raid boot device so that the raid doesn't try to incorporate it into the array yet. That Would Be Bad(tm).

What's the second RAID device for, you ask? Well, I'm glad you asked. Booting to a RAID-5 array is a bit of a problem, and /dev/md1 is part of the solution. Grub, LILO, and Yaboot do not understand the inner workings of a RAID-5 array, so they can't boot to one directly. LILO and Yaboot, however, can boot to a RAID-1 array. Therefore, once we've created our arrays, we'll make /dev/md1 into our /boot partition. It will contain the kernel, which is the only thing that needs to be accessible to the bootloader. We'll configure the bootloader to boot that kernel, and then we'll have a bootable RAID system.
Now let's create our arrays. This part is easy:

mkraid /dev/md0
mkraid /dev/md1

If all goes well, your arrays should be created without comment. Use the command 'cat /proc/mdstat' to check the status of your RAID devices.(md, by the way, stands for 'multiple devices'. It's the kernel's shorthand for RAID devices.)
NOTE: RAID autodetection steps are PC only, Mac users should skip this section and resume reading at the 'make filesystems' step.
Now that we know our arrays are working, let's stop them and setup auto-detection. Auto-detection makes use of the 'persistent superblock' that we enable in /etc/raidtab. It installs that superblock on each RAID device, and once we've set the partition type correctly, the kernel will see all our RAID devices at boot.

raidstop /dev/md0
raidstop /dev/md1

That stops the arrays so that we can modify them. Now run fdisk on *each disk* to alter the partition type:

fdisk /dev/sda
p
t
1
fd
w

This lists the parition table, selects a partition to work on, and then sets the partition type to RAID. It then writes the new partition table to disk. Do this to *each partition* to be used in the array. Then reboot and watch the kernel auto-detect your arrays.

Now, we'll make filesystems on our arrays. We'll make '/boot' ext2 and '/' Reiserfs. You can also use other filesystems. For the Mac I tested with Ext3.

mke2fs /dev/md1
mkreiserfs /dev/md0

Let's create a directory to mount our RAID to, so that we can copy our existing data over to the array. I used:

mkdir /raid

Now, we'll copy our stuff over to the new '/boot' parition:

mount -t ext2 /dev/md1 /raid
cp -a /boot/* /raid
umount /dev/md1

Now, for copying the '/' partition.

mount -t reiserfs /dev/md0 /raid
for i in `find / -type d -maxdepth 1|egrep -v 'boot|proc|raid|^/$'`
do
cp -a $i /raid
done
mkdir /raid/proc /raid/boot

Now, we need to modify the configuration files on the RAID so that it will mount things correctly. Edit /raid/etc/fstab, modifying the mount point for '/' and adding one for '/boot'. Something like:

/dev/md0 / reiserfs defaults 1 1
/dev/md1 /boot ext2 defaults 1 1

Now, umount '/raid'.
For PC, create a LILO configuration with a backup setting to test things:

umount /raid
vi /etc/lilo.conf

boot=/dev/sda1
install=/boot/boot.b
lba32
prompt
delay=50
timeout=50
default=linux-raid
image=/boot/vmlinuz-2.4.2-raid
label=linux-raid
root=/dev/md0
read-only
image=/boot/vmlinuz-2.4.2-raid
label=fallback
root=/dev/sda2
read-only

Now, simply run /sbin/lilo to setup LILO on your first partition. Note the 'fallback' entry. If something goes wrong you can still boot back to your non-RAID configuration by typing 'fallback' at the LILO prompt. Now, copy your lilo.conf to lilo.sda and lilo.sdb. We need one for each mirror of the RAID-1 partition. The reason is that we're going to install LILO on each so that if the primary disk fails, we can still boot. Essentially, we're making LILO redundant. Change /etc/lilo.sda so that the line reads 'boot=/dev/sda' and change /etc/lilo.sdb so that the line reads 'boot=/dev/sdb' and then install LILO onto the MBR of each drive:

/sbin/lilo -C /etc/lilo.sda
/sbin/lilo -C /etc/lilo.sdb

For Mac, create a Yaboot configuration with a backup setting to test things. Note that you can type 'fallback' at the yaboot prompt and get back into your non-RAID configuration if something goes wrong. Note that unlike the PC configuration, the Mac requires that we define our md devices for the kernel. That's what that 'append=' line is for.
Also, note the 'device=' line. That will be different depending on your machine. Run ofpath /dev/sda to get the Open Firmware path for your first SCSI drive. Put that in your 'device=' line.
Also important is the 'partition=' line. This should be the number of the partition that contains your kernel. In this case, the array /dev/md1 contains our kernel and it's on partition 3.
Now cp /etc/yaboot.conf /etc/yaboot.sda.conf and cp /etc/yaboot.conf /etc/yaboot.sdb.conf. Change the 'boot=' line in the second file to /dev/sdb2 and the 'device=' line to the result of ofpath /dev/sdb. Run ybin -C /etc/yaboot.sdb.conf and ybin -C /etc/yaboot.sda.conf to install Yaboot on both Bootstrap partitions.
Example yaboot.conf:

# ybin options
boot=/dev/sda2
magicboot=/usr/local/lib/yaboot/ofboot
delay=10
defaultos=linux
enablecdboot
# yaboot options
init-message="\nWelcome to Yellow Dog Linux\n\n"
timeout=50
default=linux
# yaboot images
image=/vmlinux-2.4.20-ben10
label=linux
root=/dev/md0
partition=3
append="md=0,/dev/sda4,/dev/sdb4,dev/sdc2 md=1,/dev/sda3,/dev/sdb3"
device=/pci@80000000/pci-bridge@d/ADPT,2940U2B@4/@0:
image=/boot/vmlinux-2.4.20-ben10
label=fallback
root=/dev/sda4
partition=4

Reboot and try it out.

Mac Note: The Blue & White G3 I used seems to have a pretty dumb Open Firmware. If you unplug the primary drive to test the array, be aware that the firmware takes a very long time to figure it out. In my case, it made me type 'mac-boot' before it would even fail over. Not very smart. I've been told that the G4's are better, but I haven't verified that.
If all goes well, you've just booted from the array. Now it's time to add that old partition into your RAID-5 array and enable redundancy. First, edit /etc/raidtab and change the label 'failed-disk' to 'raid-disk'. This tells the RAID the partition is OK for use now. Then add it to the array by running:

raidhotadd /dev/md0 /dev/sda2 (that's /dev/sda4 in our Mac configuration)

Use 'watch cat /proc/mdstat' to see it build the redundancy. You should see a line that says something about 'recovery' and an estimated time for completion. Once it finishes you are running a fully redundant system. You should be able to survive a hard drive failure without data loss.
Now it's time to set up our swapfile. It will exist inside the array so that a dead drive won't crash the machine. Generally you should set up a swapfile that is 2 times the size of your RAM, though for machines with lots of memory this may not be practical. First, figure out how many blocks you'll be using. This is figured out by taking the RAM count in MB and multiplying by 1024 (to convert to KB) and then doubling it. In my case I have 256MB, so 256*1024*2 is 524288.
Then cd / and dd if=/dev/zero of=swapfile bs=1024 count=524288. This will give 512MB of swapspace in /.
Now mkswap /swapfile and swapon /swapfile to create and activate the swapspace.
Next we'll add our new swap space into /etc/fstab so that it will be used automatically. Add a line to /etc/fstab that looks like this:

/swapfile swap swap
defaults 0 0

And we're done.

Written by Aaron Grewell on 11-April-2003.

Hallo My Friend

2018-09-19T06:18:00.001-07:00

I just want to start write in my blog..

see you friend.

Computer threat - continued

2007-07-05T05:08:00.000-07:00

Another threat to the computer and network as follows:

Denial of Service (DoS)

This type entangling the hacker and or a certain party to send a number of ICMP echo request to the broadcast address. Remember that the address of sender request have been disguised so difficult to tracks.

Distributed Denial of Service

DDoS

Spoofing

Is the creation of TCP/IP packets using somebody else's IP address. Routers use the "destination IP" address in order to forward packets through the Internet, but ignore the "source IP" address. That address is only used by the destination machine when it responds back to the source.Broadcast Amplification

By using broadcast amplification, an attacker can direct machines at one site to flood another site with network packets. If huge amounts of packets are sent to a site, it goes down under the load, causing denial of service. To prevent this technique from being used, the document's authors suggest that companies turn off the capability to forward directed broadcast or multicast traffic.TCP SYN attack

Computer threat - Network Security

2007-06-29T20:52:00.000-07:00

Every TCP package have 'flag bit’ defining content and intention of each package.

Example:

SYN or SYNCHRONIZE

ACK

FIN

FINISH

To build a TCP connection, need data transfer package between two host, transfer of this data recognized by the name of "TCP Three-Way Handshake" as below picture.

Computer Network Threat

Threat is very harmful to the entire system and also by application at internal and external network.

The threat as follows:

Remote Login - this matter happened when someone capable to connect to a computer and have ability to control to several things related to resource found on the host or computer.

Application Backdoors - some program have special ability to access with long distance (remote access). Some bug program, exactly contain a backdoor or hidden access providing level control the computer and program.

SMTP session hijacking - SMTP is most commonly method used to deliver E-mail. By getting E-mail mailing-list, someone can deliver undesirable E-mail to thousands of or more users. This matter is called unsolicited junk mail or spam.

Spamming conducted with joining SMTP server which not suspect, then deliver thousands of E-mail called redirecting process, so that complicate to detect who is the real sender of the Mail Spam.

Operating system bugs – In application, some operation system have conducive security gap to be exploited illegally.

E-mail bombs - is an Individual attack, someone send hundreds or thousands of E-mail to one address so the victim E-mail cannot accept E-mail anymore.

Macro - To make simple or facilitate procedure an application, many application program permit us to make command which can be run by the program (script). By exploiting ability of script or macro, attacker can cause damage of data at computer.

Virus – Most known to make trouble at computer. The growth of virus from method, way of, making, effectiveness, damage storey, and also speed of spreading is different each other.

Redirect bombs – Hacker or Cracker can use ICMP to change direction of information and attack to other router.

Source routing - At many case, a data package which work through one or some network determined by router pass to route information by the router, but sometime hacker used the package as the real sender.

Another type of computer attack are from (next posted about this) :

Denial of Service (DoS)

Spoofing

Broadcast Amplification

TCP SYN

The method to run the threat above, can be conducted variously including using virus.

Network security - protecting PC

2007-06-25T02:11:00.000-07:00

Tapping by hacker is an annoying problem when we are on surfing internet.

We have to learn how to hack but shall be used for protection from attack.

Following is tips and some software assisting to protect PC from online tapping.

Often we forget to protect our PC “attacking” from online tapping when we surf the internet.

Many civil people feel enough in protecting its PC with a program a kind of firewall desktop and anti spy firewall.

In fact, still many gap at firewall which you used, can be exploited by online watcher hacking on your PC

Below is a tips to protect PC from internet tapping in a LAN party, W-LAN or home connection as my experience.

Activated your Firewall:

In course of online tapping or infection, usually the first step do by hacker is collect information and data concerning victim to be tapped. Usually hacker use information compiler tools like “ Nmap” ( http://www.insecure.org/nmap), hereinafter hacker will check open port at victim PC and also TCP/IP package sent from PC into Network. This matter to get specific information is called print finger from victim PC.

The others way, hacker usually try to get deeper information by delivering an E-mail bait to victim (victim will open the e-mail through Microsoft Outlook program which integrated in its Windows). From bait E-mail answered, hence hacker directly can check what kind of E-mail software and server client install in victim PC.

A lot of “software bug” site, discuss about weak of E-mail software and server client according to each version, but I’m not talking about that weak at this post.

So how to avoid that attack ?

The way of which you can use as protection early is firewall desktop. If you do not wish to use special firewall or commercial, hence you enough activate personal firewall that found on Windows XP service pack 2. Comprehend firewall application path and activity which you use in order not to harm you.

Ascertaining your pc clear of Virus and Trojan, before install the firewall.
Configure your firewall with carefully in each application requiring to access online and also access sharing file in existing network.

Encrypt the Important Folder and WebMail connection.

After getting information about victim PC, usually hacker can start tapping, it is of course with two important tools that is " Ethereal" and "ARP-Spoofer". With ARP-Spoofer, hacker can take information which pass by victim PC with Gateway Internet access and that information package can be opened with “Ethereal (http://www.ethereal.com)”.

To overcome matter above, we have to encrypt our Webmail connection through https band. Do not use http band, better avoid to use ftp band and telnet, because can be sabotaged by hacker. You can use SSH connection to replace ftp band or the telnet. The existing constraint is there is very rare web server providing https service and the SSH.

One of the common Mail which use HTTPS is GMail. Whereas for the important and confidential folder in the PC better do Encrypt. Its data content with right click on folder that you want to Encrypt, its way open part: Properties – Advanced – Encrypt content to protect data. But this matter can be done if your XP windows system file is use NTFS type. By use NTFS system file, we also can block out to access rights access certain consumer.

Use Good Firewall.

With DNS spoofing, hacker can do deflection instructing PC victim to spurious website. This deflection is easy to do because DNS protocol is not have any security mechanism. This matter can be prevented by using good firewall application.

At firewall nowadays, usually DNS cache keep with elegantly, so when we ever visit to previous website, hence DNS spoofing we can prevent.

Recognize to access autoexec at registry

If hacker have succeeded tap your pc, usually they always prepare backdoor to facilitate hacking access in other opportunity. One of the effort draw up backdoor is by altering victim pc system file. But this matter can be easy to detect to through antivirus program.

The way of more realistic to all hacker by placing Trojan in our PC, then run through one of the "Autoexec" what running with autoexec in other Windows system. In anticipating this matter, which we do with install additional tools “Autorun” from Sysinternalsi (http://www.systernals.com).

With this tool can display lot of autoexec exist in our system. Autoruns also can show signature from autoexec exist in our pc system. If found autoexec entry which unknown and identify as trigger Trojan, hence Autoruns can turn off it. With this tool, we assisted in eliminating against backdoor which is possible left by hacker in our pc.

Besides trick above, to avoid tapping, suggested do not use User Administrator when surf in internet, then arrange your explorer internet security setting to High Level Security setting.

And don't forget to always Update your Windows, especially when newest update improve many Security system on your PC.

Chipset recognized

2007-06-18T23:25:00.000-07:00

The chipset is the heart of the computer and is the hub for all data transfer.
It determines how fast components like the processor, memory, keyboard and various plug-ins can function in relation to each other.

A Chipset is a corps of VLSI chip(Very Large Scale Integration Chips), which vital function execute in a computer system. Each function need one or more chip.

Not all chipsets support all components that you may want with your computer. Before selecting a chipset, decide what features you want with your computer, and then check to see that the chipset supports them.

Below is kind of Chip, replaced by a modern chipset:

Memory Controller
EIDE Controller (Enhanced Integral Drive Electronics) is a new version of IDE and improve maximum of harddisk able to be controlled from 504MB become 8.4GB.
PCI Bridge (Peripheral Component Interface or Peripheral Component Interconnect) is a local bus standard provide by Intel and working with maximum 33Mhz. The bus wide is 32/64 bit, and transfer speed is 133MB/sec for 32 bit and 266MB/sec for 64bit. PCI dissociating (decouple) processor from bus expansion via bridge.
RTC (Real-Time-Clock)
DMA (Direct Memory Access) Controller. DMA is a one of technologies used by some hardware to move data from and to main memory without entangling CPU computer (Processor)
Keyboard controller
PS/2 mouse controller
Secondary cache controller
Low Power CMOS SRAM control

There is not all Chipset replacing all chip function. Chipset is not upgradeble like CPU, memory or harddisk.

Chipset Premier Manufacturer
The famous Chipset maker company like follows:

Intel Corporation:
- Intel® Q965 Express Chipset
- Intel® 5000P Chipset for Dual-Core Intel® Xeon® Processor 5100 Series and Quad-Core Intel® Xeon® Processor 5300 Series
- Intel® 3100 Chipset for Intel® Core™ Duo processors and Intel® Celeron® M processors on 65nm
- Intel® 3100 Chipset for Dual-Core Intel® Xeon® Processors LV and ULV and Intel® Celeron® Processor 1.66 GHz and 1.83 GHz
- Intel® 3100 Chipset for Intel® Pentium® M and Intel® Celeron® M Processors on 90nm process
- Mobile Intel® 945GME Express Chipset
- Intel® E7520 Chipset for Intel® Core™2 Duo Processors and Intel® Core™ Duo Processors
- Intel® E7520 and Intel® E7320 Chipsets for Intel® Pentium® M and Intel® Celeron® M processors on 90nm process
- Intel® E7520 Chipset for Dual-Core Intel® Xeon® Processors LV and ULV, and Intel® Celeron® Processor 1.66 GHz and 1.83 GHz
- Intel® E7520 Chipset For Intel® Xeon® processors
- Intel® E7501 Chipset
- Intel® E7500 Chipset
- Intel® 945G Express Chipset
- Mobile Intel® 915GME Express Chipset
- Mobile Intel® 910GMLE Express Chipset
- Intel® 915GV Express Chipset
- Intel® 875P Chipset
- Intel® 865G Chipset
- Intel® 855GME GMCH and Intel® 6300ESB ICH
- Intel® 855GME GMCH and Intel® ICH-4
- Intel® 854 Chipset
- Intel® 852GME Chipset
- Intel® 852GM Chipset
- Intel® 845 Chipset
- Intel® 845E Chipset
- Intel® 845GV Chipset
- Intel® 815 and 815E Chipsets
- Intel® 810E2 Chipset
- Intel® 810 Chipset
- Intel® 840 Chipset
- Intel® 440BX AGPset
- Intel® 440GX AGPset
- Intel® 440MX Chipset
- Intel® 430HX PCIset
- Intel® 430TX PCIset
Silicon Integrated System Corporation (SiS):
- Intel Core 2 Duo Chipset
  - SiS672FX Fully support DX9, Certified for Windows Vista Premium
  - SiS672 Fully support DX9, Certified for Windows Vista Premium
  - SiS671FX Fully support DX9, Windows Vista ready
  - SiS671 Fully support DX9, Windows Vista ready
  - SiS671DX Support FSB 1066MHz and DDR2-667, Windows Vista Ready
  - SiS662 PCI Express&DDR2-667 Integrated Chipset For Pentium® D/Pentium®4 Processor
- Intel Pentium 4 Chipset
  - SiS656FX - PCI Express&Dual-Channel DDR2/DDR Chipset For Pentium® D/Pentium® 4 Processor
  - SiS649FX - PCI Express&Single-Channel DDR2/DDR Chipset For Pentium® D/Pentium® 4 Processor
  - SiS649 - PCI Express&Single-Channel DDR2-533/DDR400 Chipset For Pentium® 4
  - SiS656 - PCI Express&Dual-Channel DDR2-667/DDR400 Chipset for Pentium® 4
  - SiS655TX - Dual-Channel DDR400 Chipset with HyperStreaming™ Technology for Pentium® 4
  - SiS655FX - Dual-Channel DDR400 Chipset for Intel® Pentium® 4 FSB800
  - SiS648FX - DDR400 Plus AGP 8X Chipset for Intel® Pentium® 4 HT 800
  - SiS661FX - Integrated Mirage™ Graphics Chipset for Pentium® 4
  - SiS661GX - Integrated Mirage™ Graphics Chipset for Pentium® 4
  - SiS655 - Dual-Channel DDR333 Plus AGP 8X Chipset for Intel® Pentium® 4
  - SiS648 - First AGP 8X supporting Chipset with MuTIOL® 1G Technology For Pentium® 4
  - SiS651 - The Integrated Graphics Solution for Pentium® 4 with FSB533
  - SiS650 - Integrated VGA Solution for Intel® Pentium® 4
- AMD 64 Chipset
  - SiS771 - Integrated Mirage™ 3 Graphics Chipset for AMD Socket AM2 CPUs
  - SiS761GX - Integrated Mirage™ 1 Graphics Chipset for AMD Athlon™ 64 FX processors
  - SiS756 - First PCI Express Athlon™ 64 FX North Bridge Chipset
  - SiS755FX - The First AMD Athlon™ 64 FX North Bridge Chipset
  - SiS755 - The First AMD Athlon™ 64 North Bridge Chipset
  - SiS760GX - The Integrated Mirage™ 2 Graphics Chipset for AMD Athlon™ 64
  - SiS760 - The World First Integrated Chipset for AMD Athlon™ 64
- AMD 64 Chipset
  - SiS771 - Integrated Mirage™ 3 Graphics Chipset for AMD Socket AM2 CPUs
  - SiS761GX - Integrated Mirage™ 1 Graphics Chipset for AMD Athlon™ 64 FX processors
  - SiS756 - First PCI Express Athlon™ 64 FX North Bridge Chipset
  - SiS755FX - The First AMD Athlon™ 64 FX North Bridge Chipset
  - SiS755 - The First AMD Athlon™ 64 North Bridge Chipset
  - SiS760GX - The Integrated Mirage™ 2 Graphics Chipset for AMD Athlon™ 64
  - SiS760 - The World First Integrated Chipset for AMD Athlon™ 64
- AMD athlon XP Chipset
  - SiS748 - SiS AGP 8X and DDR400-supporting Chipset for AMD Athlon™ XP
  - SiS741 - The Integrated Mirage™ Graphics Chipset for AMD Athlon™ XP FSB400
  - SiS741GX - The Integrated Mirage™ Graphics Chipset for AMD Athlon™ XP FSB333
- South Bridge
  - SiS968 - The Southbridge for Windows Vista Ready
  - SiS966 - PCI Express MuTIOL® 1G Media I/O
  - SiS966L - PCI Express MuTIOL® 1G Media I/O
  - SiS965 - PCI Express MuTIOL® 1G Media I/O
  - SiS965L - PCI Express MuTIOL® 1G Media I/O
  - SiS964 - MuTIOL® 1G Media I/O
  - SiS964L - MuTIOL® 1G Media I/O
  - SiS963 - MuTIOL® 1G Media I/O
  - SiS963L - MuTIOL® 1G Media I/O
VIA Technologies
- K8 Series: AMD Opteron/Athlon 64/Athlon 64 FX
  - VIA K8T900
  - VIA K8T890
  - VIA K8M890
  - VIA K8N890
  - VIA K8T800 Pro
  - VIA K8N800A (N/IG)
  - VIA K8N800 (N/IG)
- P4 Series: Intel® Core™2 Duo, Pentium®, and Celeron®
  - VIA PT890
  - VIA PT880 Ultra
  - VIA P4M900
  - VIA P4M890
  - VIA P4M800
  - VIA P4M800 Pro
  - VIA PN800
- C Series: VIA C7®, C7®-D, C3™-M, VIA C3™ and VIA Eden™, Intel Pentium® and Celeron®
  - VIA CN896
  - VIA CN800
  - VIA CX700M
  - VIA CX700
  - VIA CN700
  - VIA CN400
  - VIA CLE266
- V Series: VIA C7®-M and VIA C7®-M ULV
  - VIA VN896
  - VIA VN800
  - VIA VX700
- K7 Series: AMD Athlon XP/Duron™
  - VIA KT880
  - VIA KT600
- VIA South Bridge Solutions: VIA Integrated South Bridges
  - VIA VT8251
  - VIA VT8237R Plus
  - VIA VT8237A
  - VIA VT8235
- Embedded & Legacy Chipsets: VIA C3™-M, VIA C3™ and VIA Eden™, Intel Pentium III and Celeron® (Socket 370)
  - VIA PLE133T (I/G)
  - VIA PN133 (N/IG

Using MDaemon PRO as a MAIL Server

2007-06-13T02:50:00.000-07:00

MDaemon is one of the utilized software as server mail besides other mail server software.

Hardware requirement for MDaemeon as a Mail Server is :

For small usage any Pentium Class With RAM 32Mb

For biggest usage min. Pentium III With RAM 128Mb

Operating System: Windows '98, Windows NT, Windows 2000, Windows 2003 (My suggestion is use Windows NT or Windows 2000, Windows 2003 so that security system and the stability can be improved)

Service E-Mail Protocol

protocol

Simple Mail transfer protocol (SMTP)
Post Office Protocol Version 3 (POP3

IMAP

Simple Mail Transfer Protocol (SMTP)

Post Office Protocol version 3 (POP3)

Function of DNS server in Email service

E-Mail Services in LAN
E-Mail service in LAN environment generally aim to facilitate coordination between internal of an organization. The Scope of LAN in fact can be extended in WAN scale. This mode is not used public network or Internet.

Email service in WAN

Forwarding of E-Mail in public network using internet or WAN, an E-Mail will passed through some server, before is finally accepted by address of target. As have been explained at previous, DNS server function is vital as indicator to route passed by the email.

sending email through internet can be use by: Relay SMTP Server and MX Record at DNS Server. To get an email can be choose with ETRN, Domain POP, Multi POP, SMTP.

Setting MDaemon at LAN

Make Domain at Local Network
Make Account and Mailbox each user
Configure E-Mail client each user

Setting Primary Domain

Domain Name: (fill with organization domain)
HELLO Domain: (name of domain which [is] used in SMTP instruction HELLO/ehlo in process delivery of E-Mail.)
Machine Name: (Domain Name)
Domain IP: (Computer IP at Local Network)
Bind listening sockets to this IP only: (Leave it blank for single Domain, usually this fill use for multiple domain)
ISP or Smart host’s IP or domain name: (Leave it blank for E-mail at LAN)

Create Account Mail

Full Name: filled with complete name of user
Mailbox Account: Filled with name to be used as E-Mail address
Allow this account to be accessed with POP/IMAP mail clients: is used to give rights so that the account can be accessed from POP client /IMAP like Outlook and Eudora.
Account password: Password for the account.
Comments on this Account: Column to fill in various note lionized for the account.

Message directory: location of directory path where E-Mail keep
Storage Format: representing depository format of file in folder for every user.
Enable automatic extraction of MIME encoded attachments: if this choice is activated, MDAEMON will extract E-Mail attachment which have found by MIME format to every E-Mail which enter. This facility is used especially for the client of E-Mail which do not have ability of MIME file extract.

Setting MDaemon at WAN
Steps to conduct MDAEMON configuration for internet connection shall be as follows:

Modem Configuration, DialUp Networking to ISP, RAS DialUp/DialDown in MDaemon.
DNS Configuration.
Sending Email Configuration.
Receipt Email Configuration.

RAS DialUp/DialDown

Enable RAS dialup/dialdown engine: To activation Dialup function.
Make this many attemps to establish a session: Is used to determine how many times MDAEMON repeat dial to ISP.
After dialing, wait this many seconds for a valid connection: This shares determine how long MDAEMON await to get link to ISP
Connection persistence: you can decide MDAEMON will continuously
connect, or determined by] certain time interval (in minute) before finally MDAEMON disconnect with ISP, if there is no activity.

Use any currently active dialup session: To determine what is MDAEMON will use conection which is active to deliver of and acceptance of E-Mail,
so that no need to dial.
Logon name: Filled with got account from your ISP.
Logon password: Password for the logon to ISP.
Use this RAS dialup profile: Is available internet connection type choice combo box. This box present networking dialup choice as according to internet connection which have installed in Windows.

DNS Configuration

Sending E-mail using SMTP Relay

Receive E-mail using MultiPOP

If ISP or hosting web do not provide DomainpPOP facility and also ETRN.
MultiPOP using as ETRN and DomainPOP
You wish free E-Mail service host in MDAEMON, so that user in network do not
need connection to internet to get the E-Mail.

The configuration as follows:
1. Enable MultiPOP mail collection for this account: to activate MultiPOP function
2. Server: POP3 server name - got from ISP
3. Logon: User account in POP3 server
4. Password: Password in POP3 server or APOP shared secret
5. Use APOP (password field contains shared secret: Make this active if authentication password is APOP
6. a copy of message on POP server: Keep the E-mail in POP3 server even MDaemon already downloaded, later you can read your mail from other location.
7. messages once [xx] or more have accumulated (0 = never): Maximum Email keeping in POP3 server
8. download messages larger than [xx] kb (0 = no limit: The limit of E-Mail size download.

>>>> I will continue this Mail server setting compare with others apps.

Internet Protocol keyword

2007-06-04T21:16:00.001-07:00

Most Windows have the ability to define Internet Protocol (IP) packet filters for protocol numbers. IP packet filters are commonly used to restrict traffic in and out of each interface.

We used this Protocol number to configure firewalls, routers and proxy. Next session i want to write about network firewall. This is as reference only, so if you want to know more about this visit the associated, like Microsoft, cisco, etc..etc

Internet Protocol Number:

Decimal	Keyword	Protocol
0		Reserved
1	ICMP	Internet Control Message
2	IGMP	Internet Group Management
3	GGP	Gateway-To-Gateway
4	IP	IP in IP (Encapsulation)
5	ST	Stream
6	TCP	Transmission Control
7	UCL	UCL
8	EGP	Exterior Gateway Protocol
9	IGP	Any Private Interior Gateway
10	BBN-RCC-MON	BBN RCC Monitoring
11	NVP-II	Network Voice Protocol
12	PUP	PUP
13	ARGUS	ARGUS
14	EMCON	EMCON
15	XNET	Cross Net Debugger
16	CHAOS	Chaos
17	UDP	User Datagram
18	MUX	Multiplexing
19	DCN-MEAS	DCN Measurement Subsystems
20	HMP	Host Monitoring
21	PRM	Packet Radio Measurement
2	XNS-IDP	Xerox NS IDP
23	TRUNK-1	Trunk-1
24	TRUNK-2	Trunk-2
25	LEAF-1	LEAF-1
26	LEAF-2	LEAF2
27	RDP	Reliable Data Protocol
28	IRTP	Internet Reliable Transaction
29	ISO-TP4	ISO Transport Protocol Class 4
30	NETBLT	Bulk Data Transfer Protocol
31	MFE-NSP	MFE Network Services Protocol
32	MERIT-INP	MERIT Internodal Protocol
33	SEP	Sequential Exchange Protocol
34	3PC	Third Party Connect Protocol
35	IDPR	Inter-Domain Policy Routing Protocol
36	XTP	XTP
37	DDP	Datagram Delivery Protocol
38	IDPR-CMTP	IDPR Control Message Transport Protocol
39	TP++	TP++ Transport Protocol
40	IL	IL Transport Protocol
41	SIP	Simple Internet Protocol
42	SDRP	Source Demand Routing Protocol
43	SIP-SR	SIP Source Route
44	SIP-FRAG	SIP Fragment
45	IDRP	Inter Domain Routing Protocol
46	RSVP	Reservation Protocol
47	GRE	General Routing Encapsulation
48	MHRP	Mobile Host Routing Protocol
49	BNA	BNA
50	SIPP-ESP	SIPP Encap Security Payload
51	SIPP-AH	SIPP Authentication Header
52	I-NLSP	Integrated Net Layer Security TUBA
53	SWIPE	IP With Encryption
54	NHRP	NBMA Next Hoop Resolution Protocol
55 - 60		Unassigned
61		Any Host Internal Protocol
62	CFTP	CFTP
63		Any Local Network
64	SAT-EXPAK	SATNET and Backroom EXPAK
65	KRYPTOLAN	Kryptolan
66	RVD	MIT Remote Virtual Disk Protocol
67	IPPC	Internet Pluribus Packet Core
68		Any distributed File System
69	SAT-MON	SATNET Monitoring
70	VISA	VISA Protocol
71	IPCV	Internet Packet Core Utility
72	CPNX	Computer Protocol Network Executive
73	CPHB	Computer Protocol Heart Beat
74	WSN	Wang Span Network
75	PVP	Packet Video Protocol
76	BR-SAT-MON	Backroom SATNET Monitoring
77	SUN-ND	SUN ND PROTOCOL-Temporary
78	WB-MON	WIDEBAND Monitoring
79	WB-EXPAK	WIDEBAND Expak
80	ISO-IP	ISO Internet Protocol
81	VMTP	VMTP
82	SECURE-VMTP	Secure - VMTP
83	VINES	VINES
84	TTP	TTP
85	NSFNET-IGP	NSFNET-IGP
86	DGP	Dissimilar Gateway Protocol
87	TCF	TCF
88	IGRP	IGRP
89	OSPFIGP	OSPFIGP
90	SPRITE-RPC	Sprite RPC Protocol
91	LARP	Locus Address Resolution Protocol
92	MTP	Multicast Transport Protocol
93	AX.25	AX.25 Frames
94	IPIP	IP-within-IP Encapsulation Protocol
95	MICP	Mobile Internetworking Control Pro
96	SCC-SP	Semaphore Communication Sec. Pro
97	ETHERIP	Ethernet-within-IP Encapsulation
98	ENCAP	Encapsulation Header
99		Any Private Encryption Scheme
100	GMTP	GMTP
101-254		Unassigned
255		Reserved

General Computer Port list

2007-06-04T06:07:00.000-07:00

Just another General Computer port. Computer Network Administrator must know below computer port and my previous posted about Computer Port List.

What is TCP/UDP?
TCP and UDP are transport protocols used for communication between computers.

TCP:Abbreviation of Transmission Control Protocol, and pronounced as separate letters. TCP is one of the main protocols in TCP/IP networks. Whereas the IP protocol deals only with packets, TCP enables two hosts to establish a connection and exchange streams of data. TCP guarantees delivery of data and also guarantees that packets will be delivered in the same order in which they were sent.

UDP:Short for User Datagram Protocol, a connectionless protocol that, like TCP, runs on top of IP networks. Unlike TCP/IP, UDP/IP provides very few error recovery services, offering instead a direct way to send and receive datagrams over an IP network. It's used primarily for broadcasting messages over a network.

Service Name	UDP	TCP
Browsing datagram responses of NETBIOS over TCP/IP	138
Browsing requests of NetBIOS over TCP/IP	137
Client/Server Communication		135
Common Internet File System (CIFS)	445	139,445
Content Replication Service		560
Cybercash Administration		8001
Cybercash Coin Gateway		8002
Cybercash Credit Gateway		8000
DCOM (SCM uses UDP/TCP to dynamically assign ports for DCOM)	135	135
DHCP Client		67
DHCP Server		68
DHCP Manager		135
DNS Administration		139
DNS client to server lookup (varies)	53	53
Exchange Server 5.0
Client Server Communication		135
Exchange Administration		135
IMAP		143
IMAP (SSL)		993
LDAP		389
LDAP (SSL)		636
MTA – X.400 over TCP/IP		102
POP3		110
POP3 (SSL)		995
RPC		135
SMTP		25
NNTP		119
NNTP (SSL)		563
File shares name lookup	137
File shares session		139
FTP		21
FTP-data		20
HTTP		80
HTTP-Secure Sockets Layer (SSL)		443
Internet Information Services (IIS)		80
IMAP		143
IMAP (SSL)		993
IKE	500
IRC		531
ISPMOD (SBA 2^nd tier DNS registration wizard)		1234
Kerberos de-multiplexer		2053
Kerberos klogin		543
Kerberos kpasswd (v5)	464	464
Kerberos krb5	88	88
Kerberos kshell		544
L2TP	1701
LDAP		389
LDAP (SSL)		636
Login Sequence	137, 138	139
Macintosh, File Services (AFP/IP)		548
Membership DPA		568
Membership MSN		569
Microsoft Chat Client to server		6667
Microsoft Chat server to server		6665
Microsoft Message Queue Client	1801	1801
Microsoft Message Queue Server	3527	135,2101
Microsoft Message Queue Server		2103, 2105
MTA – X.400 over TCP/IP		102
NetBT datagrams	138
NetBT name lookups	137
NetBT service sessions		139
NetLogon	138
NetMeeting Audio Call Control		1731
NetMeeting H.323 Call Setup		1720
NetMeeting H.323 streaming RTP over UDP	Dynamic
NetMeeting Internet Locator Server ILS		389
NetMeeting RTP audio stream	Dynamic
NetMeeting T.120		1503
NetMeeting User Location Service		522
NetMeeting user location service ULS		522
Network Load Balancing	2504
NNTP		119
NNTP (SSL)		563
Outlook (see “Exchange” for ports
Pass Through Verification	137, 138	139
POP3		110
POP3 (SSL)		995
PPTP control		1723
Printer sharing name lookup	137
Printer sharing session		139
Radius accounting (Routing and Remote Access)	1646/1813
Radius Authentication (Routing and Remote Acces)	1645/1812
Remote Install TFTP		69
RPC Client Fixed port session Queries		1500
RPC Client Using a Fixed port session Replication		2500
RPC Session Ports		Dynamic
RPC User Manager, Service Manager, Port Manager		135
SCM Used by DCOM	135	135
SMTP		25
SNMP	161
SNMP Trap	162
SQL Named Pipes Encryption Over Other Protocols Name Lookup	137
SQL RPC Encryption Over Other Protocols Name Lookup	137
SQL Session		139
SQL Session		1433
SQL Session		1024 - 5000
SQL Session Mapper		135
SQL TCP Client Name Lookup	53	53
TelNet		23
Terminal Server		3389
UNIX Printing		515
WINS Manager		135
WINS NetBios Over TCP/IP Name Service	137
WINS Proxy	137
WINS Registration		137
WINS Replication		42
X400		102

Blog reaction exchange

2007-06-02T07:09:00.000-07:00

The intention of tagged train or exchange link is to increase your Technorati rating as well as your Google PR and other search engines. That's why every blogger need to exchange link with others blog.

On my review a view month ago, Most bloggers I know have great trouble exchanging links with other blogs, this is also happened with me. So I Just developed this strategy and this strategy called "Blog reaction exchange". It's simple to set up and in theory will work extremely well (if you do as well the blog reaction will shown soon, and the link post will shown under "link to this post" in your joining content), so must leave comment and leave your content posted address once you joined. We need that participants visit yours and leave comment on your joining post.

The rule:

Tell on your posted, you are invited by whom and make a little bit about his/her blog as introduce, but remember, make the link point to the content, not to home site(i.e: I was invited by: Beyond Technology etc..etc...) see the link: http://it-matters-job.blogspot.com/2007/06/blog-reaction.html)

Make tag that you think would like to participate. Write a little bit about your friends blog.(for example:My tag - Only GOD keeps me going. This is talking about etc..etc, Or Why you invite him/her and tell a little bit about your friend blog, whatever belong to their blog

Every your new blog reaction from this train must visit and leave comment in related content

Please do not copy and paste about this post, you have to rewrite and make something different. As my review, when Google detect duplicate post it will be impact to our page rank.

Make your rule, but point 1,2,4 must included, because this is my rule abut blog friends promotion or just follow my rule but remember point 4

So, now this is my promotion blog, to make their blog reaction:

[B][E][A][U][T][I][F][U][L]
This is a blog who love shopping, a lot of interested things on her blog. She is very welcome to the visitor, especially who leave comment. Check it now..!

Nastasshea
This is about her fairy tale, Something fun on her blog, her posted is unpredictable. That's why i often visit her blog. Visit now and you can found a different out there.

Wildheart's Work...
Her name is Joe Cheray, She is the owner and manager of Kansans and Friends In Weight Loss. This is her miscellanious creative works blog. She just tagged me with anothers train.

C e l l T e c h H u b . . .
This blog covers a wide range of topics - from 2G/3G network insights to value added service implementation in cellular systems,from SS7 signaling basics to the most recent 3G mobile phone reviews

Bajaenergy / Energy BLOG
It is an Energy Data Warehouse, you can find news, stats, reports, interviews, videos, etc .. all update to students, companies, universities, whatever who likes to know more about energy sector.

A Nice Place In The Sun
She is a children's writer working on the publication of two easy readers! While researching agents, books, publishers, and writing. She decided to start a blog for parents about children's books, with articles of interest to parents, and book reviews. So visit her..!

Cafe Noche - by Miss Nice
She is my new friend and members in my MyBlogLog community. The 1st thing that I remember from her is the description of her blog "Whatever matters to me gets put up on my blog". I Like the posted about Dubai, nice place for vacation.

Free Books Yaro Starak - By Jennie VW
This Blog all material from E-Book Yaro Starak. Tips for Blogger to earn Money. She has a tips to earn money on blog. Why you blog?, what is your Goal? and how to make money online?. This is the content you can found out there. Even her blog just started, i like to shared and get blog succeed with her. Do you?

I Love Tangerine! - By Sleeping Princes
She is a twisted little loony in a whirl of confusion. The descriptions of this blog is "Of all the pain, the greatest pain is to love, but to love in vain" This is her another blog, Her permanent blog is : Sleeping Princess, so want to know her site?

Odlum Online - Web Page Design For Everyone - By Andrew Odlum
Odlum Online is devoted to exploring the internet and explaining all of the elements of web page design in an easy to understand way. Come learn along with him as he will try to make web page design accessible to everyone.

Love Forever
FAITH, HOPE, LOVE, THESE THREE, BUT THE GREATEST OF THESE IS LOVE. WHAT IS THAT LOVE TRUTHFULLY? PLEASE CLICK AND READ "LOVE" IN BLOG ARCHIVE. Thank's...! "This Blog contain about love and some module study about problem of which can assist others as one of the forming of love.

Il protagonista
This is about personal Blog

Flexible life
Life is easy. Handle it with care. Never Surrender!

If you are not in above list, you can participate also, just leave comment and i will check your site asap, once i review about your site added you to the list.

Computer Port list

2007-05-29T23:32:00.000-07:00

What is Computer port ?

An interface on a computer to which you can connect a device. Personal computers have various types of ports. Internally, there are several ports for connecting disk drives, display screens, and keyboards.

Externally, personal computers have ports for connecting modems, printers, mice, and other peripheral devices.

Almost all personal computers come with a serial RS-232C port or RS-422 port for connecting a modem or mouse and a parallel port for connecting a printer.

On PCs, the parallel port is a Centronics interface that uses a 25-pin connector. SCSI (Small Computer System Interface) ports support higher transmission speeds than do conventional ports and enable you to attach up to seven devices to the same port.

In TCP/IP and UDP networks, an endpoint to a logical connection. The port number identifies what type of port it is.

For Network administrator must know about the computer Port, to identify network attack and network function purposed.

Below is a general computer port list and the service port name:

Service Name	Port Number
Windows Services
Browsing DHCP Lease DHCP Manager Directory Replication DNS Administration DNS Resolution Event Viewer File Sharing Logon Sequence NetLogon Pass Through Validation Performance Monitor PPTP Printing Registry Editor Server Manager Trusts User Manager WinNT Diagnostics WinNT Secure channel Wins Replication Wins Manager Wins Registration Direct Hosting of SMB over TCP/IP	UDP:137,138 UDP:67,68 TCP:135 UDP:138 TCP:139 TCP:135 UDP:53 TCP:139 TCP:139 UDP:137,138 TCP:139 UDP:138 UDP:137,138 TCP:139 TCP:139 TCP:1723 IP Protocol:47 (GRE) UDP:137,138 TCP:139 TCP:139 TCP:139 UDP:137,138 TCP:139 TCP:139 TCP:139 UDP:137,138 TCP:139 TCP:42 TCP:135 TCP:137 TCP,UDP:445

Service Name	Port Number
Windows Load balancing System (WLBS) & convoy for cluster Control
Convoy WLBS	UDP:1717 UDP:2504
Microsoft Exchange
Client/Server Comm. Exchange Administrator IMAP IMAP (SSL) LDAP LDAP (SSL) MTA – X.400 over TCP/IP POP3 POP3 (SSL) RPC SMTP NNTP NNTP (SSL)	TCP:135 TCP:135 TCP:143 TCP:993 TCP:389 TCP:636 TCP:102 TCP:110 TCP:995 TCP:135 TCP:25 TCP:119 TCP:563
Windows Terminal Services
RDP Client (Microsoft) ActiveX Client (TSAC) ICA Client (Citrix) Terminal Server IPSec ISAKMP ESP AH Karberos Karberos RSVP RSVP	TCP:3389 TCP:80,3389 TCP:1494 TCP:3389 UDP:500 IP Protocol 50 IP Protocol 51 TCP;UDP:88 IP Protocol:46

Callback connection setting

2007-05-25T20:20:00.000-07:00

The callback feature instructs your remote access server to disconnect, and then to call you back, after you dial in.

What does it mean and what for ?
Call the server from your home, then immediately hanging up by the server and then server dialing you back.
Required callback enhances network security by ensuring that only users from specific locations can access the server. By dropping the call, and then calling back a moment later to the preassigned callback number, most impersonators can be thwarted.

How it work ?

You call the server to the server via modem, once your server modem response, your connection automatically disconnected then your server call you back.

What for ?
For example, you need some file from your network server while you are at home or you are out of office, and this is reduce your phone charge and the others one, you can used internet trough your server network as a gateway.

How to Setting ?

Office/Server Setting:
step 1: Incoming Connection

Open Network Connection -> Create a new connection -> Next -> Select Set up an Advance Connection -> Next -> Accept incoming connection -> Select your modem device -> Do not allow virtual private connection -> select User Permission -> Next -> Finish.

step 2:
Set Remote Access Server (RAS)
Of course this part must configured by your administrator (if you want to know how to configure RAS, ask me). If you are as a user, put the modem to your computer as your network client, then do the only step1, and of course you have to let your computer on when you leave.

Your Home Computer setting:
step 1:

Open Network Connection -> Create a new connection -> Next -> Connect to the Internet -> Next -> Setup my connection manually -> Connect using a dial-up modem -> Type connection name -> Next -> Type the Phone Number -> Type User Name and password that you has been permission to connect as above (server configuration) -> Next -> Finish.

step 2:
Open Network Connections.
On the Advanced menu, click Dial-up Preferences.
On the Callback tab, do one of the following:
1. If you do not want to use callback, click No callback.

2. If you want to decide whether to use callback at the time you connect, click Ask me during dialing when the server offers.

3.If you want to use callback consistently, click Always call me back at the number(s) below, and select the modem or device on which you want to be called back.

4.If Phone number is blank for the device you have selected, click Edit, and then type the number.

5.If you want to remove a modem or device from the list of possible callback devices, click the modem or device, and then click Delete.

(see the final setting screen)

Now try connect to your computer office.
The surprised is,
1. The phone cost become to your office computer phone line. Your cost only on the first called.
2. If your office computer able to connect the internet via you server connection, you can used internet too from your home (must check your office computer firewall setting).

Who will be joint next Alexa redirect train

2007-05-23T07:31:00.000-07:00

Understand that we need rank for our blog. They say size doesn't matter, but rank does.

Let us play Alexa redirect train. See your Alexa rank before joint this, then We will dance for better Alexa rank and next week let's us see your Alexa rank next week.

This is the train: ~Start Copying Here~
Alexa Redirect Train by Carl Ocab

Rules:

1. Put anything you like above this list – Chit Chat, talkies, introduce what this is. Something like that
2. Start copying on the “~Start Copying Here~” and copy all the things listed without removing the links (Of course, the train would be no use without those links)
3. Move all the sites labeled “Newbies” to the list labeled “Oldies”
4. Add 5 sites that you want to include in the train and make their link like this: http://redirect.alexa.com/redirect?www.example.com then invite them to join the train.
5. Visit all the listed sites! (That’s not much work! Remember, if you plant good seeds they will also grow good) and look at your high Alexa ranking next week!
Newbies
PandaCube-A Digital Notebook

My Life and my Views

chococherrycoco

Love Forever

Il protagonista

Oldies
Beyond Technology
Only GOD keeps me going
Mr & Mrs Imran
My Fairy-Tale
Life in the Fast Lane
The BenSpark
[B][E][A][U][T][I][F][U][L]
7Confessions
Celebrity Brands
Still Frames
Connected Internet
DoshDosh
Lyte Byte
Refelctions Of Time
The Cure For Silence
Blog About Money Online
Manila Mom
ScottPot
How to earn money online?
Quasi Fictional
Make Money Blogging!
Make Money Online 2.0
Nate Whitehill
Jozzua
Grow your Writing Business
CultureShiok
Gary Lee
Smart Wealthy Rich
TechZi
Erik Karey: Internet Entrepreneur
Tjantunen.com
Hate The Grind
Earn Money Blogging
be the change - tread the path
Money making Ideas in Blog
cymru66
Cell Rater
Click Fire

~End Copying Here~

BIOS signal error message

2007-05-19T22:37:00.000-07:00

PC is not response once you turn on and got "Beep" sound. Don't panic.

How to construe the beep signal message from the PC.

AMI-BIOS:
1Beep:RAM damaged or unplugged correctly
6Beep:Gate A20 error - Keyboard unplugged or damaged
8Beep:Card Graphic damaged or unplugged correctly
11Beep:Checksum-Error, check CMOS Battery on motherboard

Award-BIOS:
1Long beep:RAM problem, plug RAM correctly
1Long beep + 2short beep: Graphic card problem
1Long beep + 3short beep: Keyboard problem (Version 4.5 above this signal means graphic card problem)
un-break beep: RAM or graphic card not found

Phoenix-BIOS:
1beep+1beep+4beep: BIOS damaged
1beep+2beep+1beep: Motherboard problem or damaged
1beep+3beep+1beep: RAM problem, check RAM position
3beep+1beep+1beep: Motherboard problem or damaged
3beep+3beep+4beep: Graphic card problem or unplugged.

Now you know the BIOS signal, keep it for easy to find and solved your PC problem.

How to setting Thera for flexi

2007-05-19T11:43:00.000-07:00

As the first Pocket PC to have integrated wireless communication capabilities, the Audiovox Thera 2032 (Toshiba 2032) opens the door to the next generation of feature-rich Pocket PCs. Manufactured by Toshiba and marketed by Audiovox, the compact and user-friendly Thera 2032, delivers the comprehensive functionality of Microsoft Windows Powered Pocket PC 2002 software. In addition, the Thera 2032 boasts a TFT screen with a touch-screen interface, as well as an on-screen keyboard and handwriting recognition.

Audiovox Thera (PDA-Phone) or Toshiba SP-2032

1. Start - Program- Watcher - Admin
2. Activation Wizard - Next - Manual Activation - Next - Next
3. Enter ESN
4. Enter Activation Code (Default: 000000) Next
5. Enter MIN (10 Digits, without 0), re-enter verification MIN, Next
6. Enter SID Flexi 10496
7. initialization process Service: wait for 3 minute, message "not in service" that’s okay.
8. Restart Terminal
9. Watcher - Tools Option - choose Select System: Home Only, Save

Advance Menu, two number for manage easier:
1. Watcher
2. Ctrl-D
3. exit from Advanced Menu, enter password: ##debug
4. modem configuration, enter password: nozirevpst
5. programming Code, enter password: ##nozirevpst or
979797 or 000000

Specification:
- Modes CDMA 800 / CDMA 1900
- Weight : 7.00 oz (198 g)
- Dimensions : 128 x 77 x 20 mm
- Stub Antenna
- Battery Life Talk: 3.00 hours (180 minutes)
- Standby: 100 hours (4.2 days)10 hours in PDA mode (without wireless activity)
- Battery Type LiIon
- Display Type: LCD (Color TFT/TFD)
- Colors: 65,536 (16-bit)
- Size: 240 x 320 pixels
- Reflective TFT LCD
- Platform / OS Windows Mobile for Pocket PCs, Memory 32 MB (built-in, shared flash memory)
- Alarm : Yes
- Calculator : Yes
- Calendar : Yes
- E-Mail Client : Yes
- Expansion Card Card Type : MultiMediaCard (MMC) / Secure Digital (SD)
- Games : Solitaire included / other Pocket PC games can be added
- Headset Jack (2.5 mm) located on top
- High-Speed Data Technology: 1xRTT
- Infrared (IR) Yes
- Integrated PDA OS: Microsoft Pocket PC 2002
Intel Strong ARM 206-MHz processor / 32 MB SDRAM / 32 MB Flash ROM
- Multiple Numbers per Name : Yes
- PC Sync ActiveSync 3.5
- Side Keys voice memo key
- Speaker Phone : Yes
- Text Messaging 2-Way : Yes
- To-Do List : Yes
- Touch Screen : Yes
- USB : Yes
- Vibrate : Yes
- Voice Memo : Yes
- Wireless Internet Browser Software: Pocket Internet Explorer

Network security - Firewall setting

2007-05-17T20:56:00.000-07:00

You probably know that you need firewall security; in fact, you may even already have a firewall management program in place. But what exactly is firewall security, and what does firewall management entail?

The word firewall originally referred literally to a wall, which was constructed to halt the spread of a fire. In the world of computer firewall protection, a firewall refers to a network device which blocks certain kinds of network traffic, forming a barrier between a trusted and an untrusted network. It is analogous to a physical firewall in the sense that firewall security attempts to block the spread of computer attacks.

How Does Firewall Management Work?

A firewall management program can be configured one of two basic ways:

* A default-deny policy. The firewall administrator lists the allowed network services, and everything else is denied.
* A default-allow policy. The firewall administrator lists network services which are not allowed, and everything else is accepted.

A default-deny approach to firewall security is by far the more secure, but due to the difficulty in configuring and managing a network in that fashion, many networks instead use the default-allow approach. Let's assume for the moment that your firewall management program utilizes a default-deny policy, and you only have certain services enabled that you want people to be able to use from the Internet. For example, you have a web server which you want the general public to be able to access. What happens next depends on what kind of firewall security you have.

Below is a firewall security script, has been tested with Kerio Personal Firewall, may this rule can accepted to others firewall:

LSA Shell (lsass.exe) -> Ask - Permit - Ask - Ask
Windows NT Logon Application (winlogon.exe) -> Ask - Permit - Ask - Ask (log)
Userinit Logon Application (userinit.exe) -> Ask - Permit - Ask - Ask
Generic Host Process (svchost.exe) -> Ask - Permit - Ask - Ask (log)
Microsoft File & Printer Sharing -> Deny All (For LAN can be: Ask - Permit - Ask - Ask)
Any Other Application -> Deny - Ask - Deny - Ask (log & alert). invisible mode
Internet Browser Application -> ask - deny - deny - permit (log)
Kaspersky AntiVirus/ Kaspersky Internet Security -> ask - deny - deny - permit (log)
FTP Manager Application -> permit - permit - permit - permit (log & alert)
Yahoo Messenger -> deny - ask - deny - permit (log & alert)

Below is the rule script for Filter packet in Ferio Firewall or Tiny firewall and may can accepted to others firewall:

RULE 1
Description: ISP Domain Name Server Any App UDP
Protocol: UDP
Direction: Both
Local Port: Any
Local App.: Any
Remote Address Type: Single
Host address: IP number (Your ISP DNS server)
Port type: Single
Port number: 53
Action PERMIT

RULE 2
Description: Other DNS
Protocol: TCP and UDP
Direction: Both
Local Port: Any
Local App.: Any
Remote Address Type: Any
Port type: Single
Port number: 53
Action DENY

RULE 3
Description: Back Orifice Block (Logged)
Protocol: TCP and UDP
Direction: Incoming
Port type: List of Ports
Local App.: Any
List of Ports: 54320,54321,31337
Remote Address Type: Any
Port type: Any
Action DENY

RULE 4
Description: Netbus Block (Logged)
Protocol: TCP
Direction: Incoming
Port type: List of Ports
Local App.: Any
List of Ports: 12456,12345,12346,20034
Remote Address Type: Any
Port type: Any
Action DENY

RULE 5
Description: RPCSS (Logged)
Protocol: UDP
Direction: Incoming
Port type: Single port
Local App.: Any
Port number: 135
Remote Address Type: Any
Port type: Any
Action DENY

RULE 6
Description: Block Low Trojan Ports TCP UDP (Notify)
Protocol: TCP and UDP
Direction: Both
Port type: Port/range
Local App.: Any
First port number: 1
Last port number: 79
Remote Address Type: Any
Port type: Any
Action DENY

RULE 7
Description: Block High Trojan Ports TCP UDP (Notify)
Protocol: TCP and UDP
Direction: Both
Port type: Port/range
Local App.: Any
First port number: 5000
Last port number: 65535
Remote Address Type: Any
Port type: Any
Action DENY

RULE 8
Description: Block Outbound Unauthorized Apps TCP UDP
(Notify)
Protocol: TCP and UDP
Direction: Outgoing
Port type: Any
Local App.: Any
Remote Address Type: Any
Port type: Any
Action DENY
Nb: Kaspersky Antivirus 6 & Kaspersky Internet Security 6 usage, the remote port address choose Any)

RULE 9
Description: Block Inbound Unknown Apps TCP UDP
(Notify)
Protocol: TCP and UDP
Direction: Incoming
Port type: Any
Local App.: Any
Remote Address Type: Any
Port type: Any
Action DENY

RULE 10
Description: Block ICMP (Logged)
Protocol: ICMP
Direction: Both
ICMP Type: Echo Reply, Destination Unreachable, Source
Quench, Redirect,
Echo, Time Exceeded, Parameter Prob, Time Stamp, Time
StampReply, Info
Request, Info Reply, Address, Address Reply, Router
Advertisement, Router
Solicitation (ALL)
Remote Endpoint: Any
Action DENY

RULE 11
Description: In Block Ping and TraceRoute ICMP
(Notify)
Protocol: ICMP
Direction: Incoming
ICMP Type: Echo
Remote Endpoint: Any
Action DENY

RULE 12
Description: Out Block Ping and Trace Route ICMP
(Notify)
Protocol: ICMP
Direction: Outgoing
ICMP Type: Echo Reply, Destination Unreachable, Time
Exceeded
Remote Endpoint: Any
Action DENY

RULE 13
Description: Block Common Ports (Logged)
Protocol: TCP and UDP
Direction: Incoming
Port type: List of Ports
Local App.: Any
List of Ports:
113,79,21,80,443,8080,143,110,25,23,22,42,53,98
Remote Address Type: Any
Port type: Any
Action DENY

RULE 14
Description: Loopback
Protocol: TCP and UDP
Direction: Both
Local Port: Any
Local App.: Any
Remote Address Type: Single
Host address: 127.0.0.1
Port type: Any
Action PERMIT

RULE 15
Description: Block Inbound NetBIOS TCP UDP (Notify)
Protocol: TCP and UDP
Direction: Incoming
Port type: Port/Range
First Port: 137
Last Port: 139
Local App.: Any
Remote Address Type: Any
Port type: Any
Action DENY

RULE 16
Description: Block Outbound NetBIOS TCP UDP (Notify)
Protocol: TCP and UDP
Direction: Outgoing
Local Port: Any
Local App.: Any
Remote Address Type: Any
Port type: Port/Range
First Port: 137
Last Port: 139
Action DENY

RULE 17
Description: Bootpc (Logged)
Protocol: TCP and UDP
Direction: Incoming
Port type: Single port
Local App.: Any
Port number: 68
Remote Address Type: Any
Port type: Any
Action DENY

RULE 18
Description: Out Needed To Ping And TraceRoute Others
Protocol: ICMP
Direction: Outgoing
ICMP Type: Echo
Remote Endpoint: Any
Action PERMIT

RULE 19
Description: In Needed To Ping And TraceRoute Others
Protocol: ICMP
Direction: Incoming
ICMP Type: Echo Reply, Destination Unreachable, Time
Exceeded
Remote Endpoint: Any
Action PERMIT

RULE 20
Description: Internet Explorer-Web browsing (logged)
Protocol: TCP
Direction: Outgoing
Port type: Any
Local App.: Only selected below => iexplore.exe
Remote Address Type: Any
Port type: Any
List of ports: Any
Action PERMIT

RULE 21
Description: Outlook Express
Protocol: TCP
Direction: Outgoing
Port type: Any
Local App.: Only selected below => msimn.exe
Remote Address Type: Any
Port type: List of ports
List of ports: 25,110,119,143
Action PERMIT

RULE 22
Description: Yahoo Messenger
Protocol: TCP
Direction: Outgoing
Port Type: Any
Local App.: Only selected below => yahoomessenger.exe
Remote Address Type: Any
Port Type: List of ports
List of ports: 443,80,5050
Action PERMIT

RULE 23
Description: Yahoo Messenger
Protocol: UDP
Direction: Outgoing
Port Type: Any
Local App.: Only selected below => yahoomessenger.exe
Remote Address Type: Any
Port Type: single
List of ports: 3478
Action PERMIT

RULE 24
Description: Download Manager (logged)
Protocol: TCP
Direction: Outgoing
Port Type: Any
Local App.: Only selected below => (your download manager file)
Remote Address Type: Any
Port Type: List of ports
List of ports: 80,21
Action PERMIT

For filter packet setting on Local Area Network (LAN) can added with below rule script to allow NetBIOS access at specific port:

RULE 15a
Description: Trusted Inbound NetBIOS TCP UDP
Protocol: TCP and UDP
Direction: Incoming
Port type: Port/Range
First Port: 137
Last Port: 139
Local App.: Any
Remote Address Type: Trusted Address Group
Port type: Any
Action PERMIT

RULE 16b
Description: Trusted Outbound NetBIOS TCP UDP
Protocol: TCP and UDP
Direction: Outgoing
Local Port: Any
Local App.: Any
Remote Address Type: Trusted Address Group
Port type: Port/Range
First Port: 137
Last Port: 139
Action PERMIT

My Visitor

2007-05-17T07:22:00.000-07:00

This site started on Wednesday, May 2, 2007, This site is talking about the Computer Technology, networking, gadgets and others regarding to Technology information. (author: Jan Pieter Marbun)

This site is my experience as an IT worker at manufactured company. I dedicated this site to my friends, my staff and reader's who loved the Information Technology jobs.

Thanks to my visitor and my readers for stopped by this site, please do leave comment when you visit this site and i Appreciate for your review.

Below is my visitor and some of my comment about their site:

From MyBlogLog:
1.

chemstudioster

Member Since: 22nd Mar 2007

Tech_tube

Member Since: 27th Apr 2007

Der0nITE

Member Since: 27th Apr 2007

charleyhtb

Member Since: 3rd May 2007

sylvied

Member Since: 20th Mar 2007

baLooT

Member Since: 8th Feb 2007

imaginarydivabc

Member Since: 29th Nov 2006

kkama67

Member Since: 24th Feb 2007

shokthx

Member Since: 19th Mar 2007

10.

Rouvanne

Member Since: 13th Feb 2007

11.

sexyinred

Member Since: 18th Jan 2007

12.

wildheart4vr

Member Since: 3rd May 2007

13.

singaporecutegirl

Member Since: 21st Apr 2007

14.

wizcoder

Member Since: 25th Oct 2006

15.

RES

Member Since: 14th Apr 2007

16.

dmgparis

Member Since: 21st Mar 2007

17.

dunn

Member Since: 15th Mar 2007

18.

kyutbabe

Member Since: 24th Apr 2007

19.

echathost

Member Since: 15th Feb 2007

20.

security

Member Since: 13th Apr 2007

21.

Brunail

Member Since: 5th Sep 2006

22.

suntze

Member Since: 23rd Mar 2007

23.

fastfastlane

Member Since: 12th Apr 2007

24.

akijinn

Member Since: 5th Apr 2007

25.

mrjoe46

Member Since: 16th May 2007

26.

LJP

Member Since: 1st Apr 2007

I love their site, visit their site often. Need your response and comment to improved this site.

Testing Audio card Quality using RMAA

2007-05-13T08:19:00.000-07:00

Microsoft suggested to installed audio component at PC for standard facility, In the middle of year 1990

Now sound Card is included in the PC motherboard as responded to Microsoft suggestion. Many type and kind of sound card used on the PC motherboard at the moment, but sometimes PC consumer is not care about the quality of the sound.

Four criteria to determine quality of sound card as below:

1. Resolution
2. Sampling rate
3. Signal/noise ratio (SNR)
4. Channel quantity

The explanation of sound criteria:

1. Resolution

This is a level of original sound compression.
Resolution is higher, compression level make distantly spaced and the sound quality more high. Sound resolution about 16 bit, but some already 20 – 24 bit.

2. Sampling rate:

Conversion analog to digital by second value. Sampling standard value is 44.1Khz, almost sound card work with 48Khz and at the moment thru 192Khz.

3. Signal to Noise Ratio (SNR)

Major sound and minor sound differential result by sound card. This parameter is important to build the sound clearly. The standard of SNR is 80db. High end chip audio, the value thru 100db

4. Channel quantity.

In the past the channel of sound is only two, left speaker and right speaker. Now, most sound chip produced 6 channel or 5.1 (left and right speaker, in front and behind plus 2 center speaker for bass and sound vocal)
The latest system is 7.1, this is 6(5.1) channel plus 2 speaker in the center.

To check our sound card on pc, physically we can see.
“Open the pc chasing, look at the sound card. The position of sound card is different for each motherboard, belong to the brand, check the manual book for sure and follow the above that informed sound card specification".

Quality tested

It is difficult to check quality of PC sound card, caused the result almost subjective disposed.

We can used RightMark Audio analyzer (RMAA) (download), to test with scientific method.

RMAA suite is designed for testing quality of analog and digital paths of any audio devices, be it a sound card, an MP3 player, a consumer CD/DVD player or an acoustic set. The results are obtained by playing and recording test signals passed through the tested audio path by means of frequency analysis algorithms. A more common mark is also provided for those unfamiliar with measured technical parameters.

How to used the program ? see my tested.

First, you must have supporting component (audio cable, to connect in-audio port and out-audio port)

The steps run is:

1. Connect in-audio port (red color) with out-audio port (green color) with the cable.

2. Run program RMAA 5.5, for easy choose wizard, this is simple running tested.

3. Choose test parameter, included playback/recording source, resolution and sampling rate.

4. Follow the step, the most important is set volume output and input to standardized supposed. Pre requirement input sound is about 1db.

5. To set input and output as pre requirement, set the volume at volume panel. Most The important set is “Wave out” and “Master” for playback and “Line in” for recording.

6. When the box indicator light is green, the test be run. Click start button, and wait the process.

7. Once the process finish, you can save the result with HTML format. In the result will shown the sound quality with any variable, included the explanation. Done.

Resolution canal type SNR (db) manufactured:

Analog Devices AD1885 16 bit 2 90
Analog Devices AD1985 18/20 bit 6 80-90
C-Media CMI9738 18 bit 4 72-82
C-Media CM19761 16/20 bit 6 90-95
Realtek ALC201A 18 bit 2 90
Realtek ALC650 18/20 bit 6 90
Realtek ALC655 16 bit 6 90
Realtek ALC658 18/20 bit 6 100
Realtek ALC850 16 bit 8 100
Realtek ALC880 24 bit 8 103
Via Envy24 24 bit 8 N/A

Sound dictionary:

1.Frequency response: is the measure of any system's response at the output to a signal of varying frequency (but constant amplitude) at its input. It is usually referred to in connection with electronic amplifiers, loudspeakers and similar systems. The frequency response is typically characterized by the magnitude of the system's response, measured in dB, and the phase, measured in radians, versus frequency

2.Noise Level: is the noise power of the longitudinal sound wave relative to a point of reference.
Note: Noise level is usually measured in dB for relative power or picowatts for absolute power

3.Dynamic Range: The ratio between the loudest and softest sounds

4.THD (Total Harmonic Distortion): The total harmonic distortion, or THD, of a signal is a measurement of the harmonic distortion present and is defined as the ratio of the sum of the powers of all harmonic components to the power of the fundamental.

5.IMD+Noise: Intermodulation Distorsion (IMD): Distortion in sound output as a failed in the sound card. Lowest is better

6.Stereo Crosstalk: physical defect happened when the sound should be in the right speaker, sound in the left speaker