Friday, August 23, 2013

New Linux Ubuntu

Features the latest ubuntu shutdown dialogs, unity preview animations, window snap animation and others - others. At the time this latest post will Kolombloggratis.Org searching articles on the latest ubuntu software that maybe some people are still unfamiliar with this name because most do computer or laptop using the os from windows and just some people who know that using ubuntu. because of its exciting Free Blog Column recommend ubuntu to try, if you are interested in downloading apps in the download link below, ...

Some features of ubuntu are updated on the newest version of ubuntu from keamaanan, stability, speed, increased software or performance of a variety of programs and services ubuntu center that allows users to access various applications and to install Ubuntu OS on pc free, ...

Features - Features Latest Ubuntu Linux Software

     Speed ​​and baby
     window switching
     New lenses
     New bluetooth menu
     Workspace item
     New sync menu
     Per-App toggles account
     shutdown dialogs
     Unity preview animations
     Window snap animation

Ubuntu is an alternative to something different with the free app, app penjelah ubuntu is mozilla firefox browser with the user which is the most current, flagship applications of ubuntu is open its office which is not inferior to microsoft office. Open Office is a word processing device, figure drawing, and presentation. all licenses of programs free and open office open source, Ubuntu OS can be run concurrently with OS windows with dual boot so that the inside of the laptop or computer can have 2 OS is ubuntu and windows without error, after selesei ubuntunya download applications please go to tutorial




Wednesday, August 21, 2013

Info : Wireless Tools for Linux

 Presentation


The Linux Wireless Extension and the Wireless Tools are an Open Source project sponsored by Hewlett Packard (through my contribution) since 1996, and build with the contribution of many Linux users all over the world.
The Wireless Extension (WE) is a generic API allowing a driver to expose to the user space configuration and statistics specific to common Wireless LANs. The beauty of it is that a single set of tool can support all the variations of Wireless LANs, regardless of their type (as long as the driver support Wireless Extension). Another advantage is these parameters may be changed on the fly without restarting the driver (or Linux).
The Wireless Tools (WT) is a set of tools allowing to manipulate the Wireless Extensions. They use a textual interface and are rather crude, but aim to support the full Wireless Extension. There are many other tools you can use with Wireless Extensions, however Wireless Tools is the reference implementation.
  • iwconfig manipulate the basic wireless parameters
  • iwlist allow to initiate scanning and list frequencies, bit-rates, encryption keys...
  • iwspy allow to get per node link quality
  • iwpriv allow to manipulate the Wireless Extensions specific to a driver (private)
  • ifrename allow to name interfaces based on various static criteria
Most Linux distributions also have integrated Wireless Extensions support in their networking initialisation scripts, for easier boot-time configuration of wireless interfaces. They also include Wireless Tools as part of their standard packages.
Wireless configuration can also be done using the Hotplug or uDev scripts and distribution specific support, this enable the proper support of any removable wireless interface (Pcmcia, CardBus, USB...).
Any versions of the Pcmcia package offer the possibility to do wireless configuration of Pcmcia and Cardbus card through thefile wireless.opts. This allow to fully integrate wireless settings in the Pcmcia scheme mechansism. However, this method is now deprecated in favor of distribution specific methods.
Please note that the Wireless Tools (starting with version 19) supports fully IEEE 802.11 parameters and devices, support older style of devices and most proprietary protocols, and are prepared to handle HiperLan as well. More recent versions of course adds more 802.11 support.
But, unfortunately not all drivers support all these features...

Documentation & errata

The Wireless Tools package include extensive for each of the tools, which are the most up to date and most detailed documentation on the capability of these tools. The latest stable version of Wireless Tools is , it is stable, most of the stupid bugs have been removed and it supports all Wireless Extensions (from version v11 to v21).
man pages
The Wireless Tools package also includes two text documents on the usage of Wireless Tools to configure wireless cards automatically :
  • DISTRIBUTIONS.txt describes how various Linux distributions implement Wireless Extensions in their specific configuration scripts. Please read this, as most distributions no longer use wireless.opts. I need your help making this document better.
  • HOTPLUG-UDEV.txt describes how to manage wireless interfaces using the HotPlug subsystem and the distribution specific support for wireless, and includes some more advanced material. This is a complement to DISTRIBUTIONS.txt.
  • PCMCIA.txt describes the use of Pcmcia schemes and wireless.opts (i.e. configuration with the default Pcmcia scripts). This method is deprecated, but still work and has some advantages.
Some driver documentations (man page, web, README) describe what the driver support in term of Wireless Extension and how the various Wireless Extension parameters map to the capability of the card.
The Linux Wireless LAN Howto contains a section about the Wireless Extensions, but it's a bit out of date for the details...

I have also the following errata and comments :
  • In the rare cases where your kernel isn't compiled with Wireless Extensions (/proc/net/wireless non-existent), you need to recompile it with Wireless Extensions (CONFIG_NET_RADIO enabled).
  • After recompiling a kernel with Wireless Extension, you have to recompile your driver or the Pcmcia package as well (and restart it).
  • All versions of Wireless Tools up to version 26 need to be compiled for the precise version of Wireless Extension present on the system. Starting with Wireless Tools 27, Wireless Tools can handle multiple versions of Wireless Extension without recompile.
  • The Wireless Extensions and Wireless Tools version numbers will not match with each other. The Wireless Tools and the Wireless Extensions (the underlying API) evolve independantly of each other. The command iwconfig --version gives you the detail of your setup.
  • Compilation of the Wireless Tools used to be tricky, especially in the header area. I believe this has been fixed for good.
  • For kernels before 2.2.14/2.3.30, use Wireless Tools version 19.
  • For kernel after 2.2.14/2.3.30 use Wireless Tools version 20 or greater.
  • For kernel after 2.6.13 use Wireless Tools version 27 or greater.
  • The tools and the wireless library are GPL.
  • In the old time, you could upgrade Wireless Extensions by just changing wireless.h. Starting with Wireless Extensions v12, this is no longer true, you need to apply the full patch to the kernel. See below for the patches.
  • Further down, you will find a FAQ about common problems.

version 29 You can download Wireless Tools on this server :
  • Download the latest wireless tools package
For historical purpose, you can get earlier version here : version 19, version 20, version 21, version 22, version 23, version 24, version 25, version 26, version 27, version 28 and version 29. There is no point in using an old version, as the latest version can support all versions of Wireless Extensions.
The main features of the latest beta is support for non-ASCII ESSIDs (such as localised ESSID), support for displaying Scanning Capabilities, slightly bigger scan buffer, fixing minor bug iwconfig parser and minor enhancement to ifrename :
Experimental version of Wireless Tools (at your own risk) :
The detailed changelog of the Wireless Tools is in the package, what follows is a human readable version of it ;-).

Monday, March 22, 2010

Suse 10 Connection Internet

Here that I set up:
1. Sign yast2 (Yast Control Center)
2. Sign in to Network Devices
3. Sign in to Network Card
4. ">Tap Edit to Lan Card that will connect to the network ->
Edit.
5. When Want to use Static IP Address Static press option Setup
6. Press the button Host Name and Name Server
7. At the same Host Name Server free.
8. In the Name Server with the No. 1 insert that gives the computer IP
Internet Connection Sharing
9. Domain Search my fill 1 mshome.net
10. it

Friday, March 19, 2010

Netsend in linux can use LinPopUp

Netsend in linux can use LinPopUp, condition just smbclient
it should be up ...
Already in the repo, so stay "sudo apt-get install LinPopUp"
byte @ delta: ~ $ sudo apt-cache search LinPopUp
LinPopUp - X Window System port of Winpopup, running over Samba
http://freshmeat.net/projects/linpopup/
"LinPopUp is a GTK port of Winpopup, running over Samba. It permits
communication with a Windows-running computer that runs Winpopup,
sending or receiving messages " GoodLuck yach

Wednesday, March 10, 2010

An easy way in Linux file sharing with SAMBA

Samba (server message block) is a protocol file sharing and printer sharing to compete with the existing protocols of Novell's IPX-based.SMB is a protocol file sharing and printer sharing Dapa first run on start protocol: TCP / IP, Ne BEUI , IPX / SPX. In other words, the SMB server can replace the position Novell server without having to change the infrastructure of the network will sendiri.Disini author briefly explains the samba server settings in Open Suse 10.0 is langkah2 following it:

1. Make sure that the samba server has been installed.
rpm-qa | grep samba
yast2-samba-server-2.13.9-8
samba-3.0.22-11
samba-client-3.0.22-11
kdebase3-samba-3.5.1-69
samba-vscan-0.3.6b-40
yast2-samba-client-2:13:18-4
samba-doc-3.0.22-16
samba-winbind-3.0.22-11
2. Edit the samba configuration file. If in OpenSuse, the existence of / etc / samba / smb.conf. On the other distributions
should be about / etc / as well.
In the smb.conf file is already there bagian2 configurations, namely with the [Global], [homes],
[printers], etc.

[global]

workgroup = HOME
server string = FSHENDRO
interfaces = 192.168.5.1
bind only = true interfaces
# Printing = cups
# Printcup name = cups
# Printer admin = @ ntadmin, root, administrator
map to guest = Bad User
passwd program = / usr / bin / passwd% u
passwd chat = * password *% n \ n * password *% n \ n * changed *
passwd chat debug = Yes
unix password sync = Yes
logon script = profile.bat
logon path = \ \ N% \ profiles \% u
logon drive = H:
logon home = \ \ N% \% u
domain logons = Yes
domain master = Yes
wins support = Yes

[homes]
comment = Home Directories
valid users =% S
browseable = Yes
read only = No

[share]
comment = share to all users
path = / samba / share
read only = No
writeable = Yes
create mask = 0666
inherit permissions = Yes

[groups]
comment = All groups
path = / home2 /% g
writeable = Yes
inherit permissions = Yes
create mask = 0666

comment = Intaller
path = / samba / source
read only = No
writable = No
inherit permissions = No

# [printers]

# Comment = All Printers

# Path = / var / tmp

# Printable = Yes

# Create mask = 0600

# Browseable = No

# [print $]

# Comment = Printer Drivers

# Path = / var / lib / samba / drivers

# Write list = @ root ntadmin

# Force group = ntadmin

# Create mask = 0664

# Directory mask = 0775

Saturday, March 6, 2010

Print process of the Linux computer to Windows

Print process of the Linux computer to Windows computer probably inevitable when migrating an operating system where the position of the system is still a mixture of Linux-based computer with Windows-based computers. There are various ways to print process for this situation, both print via samba and print protocol over TCP-IP.

Based on experience, here's how a "must" succeed in doing print process. Of course both computers are connected using a network system.

regular use LPD protocol instead of Samba to connect from Linux to Windows computers. The trick is as follows:

In Computer Windows, using Windows 2000 and above (direct connection to the printer)

1. Going to Settings | Control Panel | Add-Remove Programs
2. Log in to Windows Components
3. Select Other Network File and Print Services (check)
4. Select Next and so on until it finished the service components installed
5. Enable services to run automatically every time the computer boots by selecting Settings | Control Panel | Administrative Tools | Services
6. Perform printer sharing has been connected. Create a simple connection and easy to remember
7. Check the Windows computer's IP. Can use the Ipconfig command at the command prompt.

On the Linux computer (client)

1. Apply settings and select the LPD printer queue
2. Enter the IP Address your Windows computer and printer share names on the existing settings
3. Test your printer.

Tuesday, February 23, 2010

Sharing Internet at Ubuntu

Devices that use a server with 2 Network 10/100 Mbps Internet network from the ISP (Speedy), Switch that connects to the LAN and PC Client with each assumed to be 1 LAN card using the PC client 25.

The first step: Determining IP Address Server for Connection to ISP

Data obtained from ISP (Speedy) obtained an IP address such as 125,162,149,201

Subnetnya 255,255,255,254

Acquired ISP's DNS: 202.93.40.174 and 202.152.165.36

ISP Gateway obtained: 125.162.54.1

The second step determines IP Address for Connections Local / LAN

Because the client is assumed to be 25 units then you should select the IP Address 172.16.17.1/27 means Subnetnya is 255,255,255,224

We specify IP Address Server that connects to the LAN we set: 172.16.17.1

Obtained from the ISP's DNS: 202.93.40.174 and 202.152.165.36

The third step determines the Client IP Address:

Client - 1

IP Address: 172.16.17.2

subnet mask: 255,255,255,224

DNS from ISP: 202.93.40.174 and 202.152.165.36

Gateway: 172.16.17.1 (IP address server connected to LAN)

Client - 2

IP Address: 172.16.17.3

subnet mask: 255,255,255,224

DNS from ISP: 202.93.40.174 and 202.152.165.36

Gateway: 172.16.17.1 (IP address server connected to LAN)

The fourth step Setting Internet sharingnya

To make such sharing internet connection from client 1 to client 2

1. In Computer Server

Administration > Network pilih wired connection (eth0) kemudian klik Properties pada Connection Setting isikan seperti berikut ini :" onmouseover="this.style.backgroundColor='#ebeff9'" onmouseout="this.style.backgroundColor='#fff'">Open the network settings: System> Administration> Network select wired connection (eth0) and then click Properties on the Connection Settings insert the following:
Administration > Network pilih wired connection (eth0) kemudian klik Properties pada Connection Setting isikan seperti berikut ini :" onmouseover="this.style.backgroundColor='#ebeff9'" onmouseout="this.style.backgroundColor='#fff'">
Administration > Network pilih wired connection (eth0) kemudian klik Properties pada Connection Setting isikan seperti berikut ini :" onmouseover="this.style.backgroundColor='#ebeff9'" onmouseout="this.style.backgroundColor='#fff'">Configuration: Static IP Address

IP Address: 125,162,149,201

Subnetmask: 255,255,255,254

Gateway: 125.162.54.1

Click OK and then back into the Network Settings control click and add the DNS address from your ISP (202.93.40.174 and 202.152.165.36)

Connect the cable from the ISP to the NIC (eth0) and then open a terminal ping to google in type

ping www.google.com

If no replay is an internet connection is OK

Back to Network Settings window select Wired Connection (eth1) and then click Properties, make the following configuration:

Configuration: Static IP Address

sesuaikan dengan LAN yang kita buat" onmouseover="this.style.backgroundColor='#ebeff9'" onmouseout="this.style.backgroundColor='#fff'">IP address: 172.16.17.1 -> adjust the LAN that we make
sesuaikan dengan LAN yang kita buat" onmouseover="this.style.backgroundColor='#ebeff9'" onmouseout="this.style.backgroundColor='#fff'">
sesuaikan dengan LAN yang kita buat" onmouseover="this.style.backgroundColor='#ebeff9'" onmouseout="this.style.backgroundColor='#fff'">Subnetmask: 255,255,255,224

Gateway address: Clear

Click OK and close the Network Settings window and plug the network cable to the Switch

2. Setting the Client Computer

Setting IP on the client do as much as we do on the server

Client-1

IP: 172.16.17.2

Subnet mask: 255,255,255,224

Gateway: 172.16.17.1 (IP LAN servers)

Client 2

IP: 172.16.17.3

Subnetmask: 255,255,255,224

Gateway: 172.16.17.1 (IP Address Server LAN) ... etc with the same thing for each existing client.

After the settings to try pinging the server, the terminal type ping 172.16.17.1 if reply then the connection is OK.

The next step is sharing the internet, the Ubuntu software tinggall use Firestarter. Kalo is not installed open a terminal typing using apt-get install Firestarter.

Run Firestarter just follow wizzardnya, select the Internet connection from eth0 and eth1 network of local.