LQWiki - User contributions [en]

HTML editor

2012-04-16T13:50:15Z

Sag47: /* Specific applications */

Given that [http://en.wikipedia.org/wiki/Html HTML] is simply text, any [[text editor]] is an [[HTML editor]]. However, calling an [[application]] an HTML editor implies it has special HTML features like [[WYSIWYG]].

= Specific applications =
* [http://www.w3.org/Amaya/ amaya]
* [http://www.aptana.com/ Aptana Studio]
* [http://bluefish.openoffice.nl/ blueFish]
* [http://en.wikipedia.org/wiki/Mozilla_composer Mozilla Composer]
* [http://www.nvu.com/ nvu]
* [http://www.screem.org/ screem]

= See also =
* [[Web Design]]

User talk:ThorstenStaerk

2011-11-23T14:51:41Z

Sag47:

== Vandalism ==

There's a guy by the name of "Linux" going around and blanking all the pages. Can you block him and clean it up please? [[User:Linux|Linux]] 19:02, June 7, 2007 (EDT)
: why ? In most cases, your blanked pages are better than the blahblah before. And if you want to stop, I do not need to block you, just quit. --[[User:ThorstenStaerk|ThorstenStaerk]] 08:04, June 8, 2007 (EDT)

== Proper Way To Start Sysadmin Page ==

What do you recommend as a starting point for sysadmin, just pick a topic and write it?

--[[User:Cmnorton|Cmnorton]] 15:25, March 24, 2008 (EDT)

== Comparison of Linux distributions ==

Hi ThorstenStaerk, it didn't seem to be significant to me, but I can see what you mean about the small details. Perhaps it would be better stated as something like "Includes many common shortcuts to save time (such as the 'll' command, etc.)" - [[User:Blackice|Blackice]] 18:21, October 1, 2008 (UTC)

== beep ==

i added the author's name to distinguish it from the normal system beep or 'printf("\a")'.

Couple questions:

first, is this the right place to ask you something? or is there a message link i'm missing

second, was removing the redirect for previous 'beep' -> 'Turn off system beep' ok? I included it in the new beep article in 'see also' because I thought it was still relevant.

i'm discovering there are a lot of programs out there called beep!

I'm new to wwiki so please let me know if i ever do anything taboo or whatever, i'm just killing time and helping where i can

Hi ThorstenStaerk: I know you've seen me darting around editing stuff, but now I'm running out of ideas, I'm not techy, and I'm a linux newbie. if you know of something, even boring stuff, that needs done, please offer suggestions and I'll get right to it. I kill time while at work, read, edit where I know a little about it, learning lots. have a good week -Scott

Thank you for the ideas, and thanks for having LiVES in your favorite list - I had not heard of that software - I compiled it from source with no problems and having fun editing some video now :]

""""""

hi, biorezonanta is not spam , can i edit please.
thank you
biorezonanta

== How do you get a new page recognized? ==

A quick question:

How can you get a new file recognized as having been written?
I ask because of the submission I made for [[File:Hosts]] is still showing up on the [[Special:WantedPages|Most Wanted]] list.

TIA.

[[User:ShadowCat8|ShadowCat8]] 21:27, November 18, 2009 (UTC)

: This seems to be a mediawiki bug. I stopped caring about this entry in the [[Special:WantedPages|Most Wanted]] list after I wasted a lot of time on it. But thanks for your willingness to contribute --[[User:ThorstenStaerk|ThorstenStaerk]] 05:49, November 19, 2009 (UTC)

== Fuzzy redirects ==
Hi Thorsten,

What's the use of those myriads of (imo) meaningless redirects with only one (middle) differing capital. Initial Capitals: ok, ALLCAPS, sometimes ok, but sillyCapS means only noise... - [[User:Bemoeial|Bemoeial]] 00:07, November 25, 2009 (UTC)
: Hey, you are right, I started realizing this as well... a bit slowly. The basic idea was that we had stupid dupliates (like and article CUPS and an article Cups) and I wanted to get rid of it. Anyway I exaggerated, stopping it now :) thanks --[[User:ThorstenStaerk|ThorstenStaerk]] 06:00, November 25, 2009 (UTC)

== Who/Where do I ask questions about this wiki? ==
I'm new to this wiki and I have some questions. [http://wiki.linuxquestions.org/wiki/LQWiki:Site_discussion The Official mailing list] dosen't seem to work so I'm asking here instead. 
====Starting with two questions:====
Who (if any) is/are in charge here? 
Who can I ask or where can I ask it if I got questions about and/or suggestions for this wiki? 
-- [[User:Lingonberga|Lingonberga]] 19:04, November 30, 2009 (UTC)

: [[User:Jeremy]] --[[User:ThorstenStaerk|ThorstenStaerk]] 08:31, December 1, 2009 (UTC)

== interesting website and stuff ==

It's not often I find another user who knows how to ninja himself around the Windows registry like one can with the Linux terminal.

Interesting articles and stuff.

By the way I added two styles to the wiki FYI.

One for tables and one for author credit.

They are: [[Template:PageAuthor]] and [[Template:Rh]].

The PageAuthor style goes at the head of an article for an original creator. It is written like so...
<pre>{{PageAuthor|Sag47}}</pre>

For references on usage of the table style please refer to the tables in [[Set up FTP server]]. You can also see an example of the author credit tag at the beginning of that article.

SAM

:: you got my weak spot, it my mantra that you cannot judge the Linux way of doing a particular thing without knowing the Windows way. I saw your templates, what is Rh for? I don't get this. Thanks for your contributions, I seldom see this good quality. --[[User:ThorstenStaerk|ThorstenStaerk]] 05:38, August 24, 2010 (UTC)

== Re: templates Rh ==

I got the Rh style template from another [http://en.wikipedia.org/wiki/Template:Rh wiki]. It's to point out main entries and separate them from the values within it. Many tables just have a header along a top line but some times have both a sidebar and a header. I added Rh because it better distinguishes this and in the case of a Software vs. OS compatibility it works well.

I feel your mantra works well with all operating systems. I try to learn as much as I can about any OS I touch. Thanks for the props on article quality. I've got more up my sleeve so you'll be seeing more entries like that. Eventually I'll run out of experience though and have to venture into new ground for writing articles (that's kind of what I had to do for proftpd, I answered a users question in the forums with that and then created the wiki article).

I got the author template from the [http://nsis.sourceforge.net/Template:PageAuthor NSIS wiki]. I didn't write it myself.

I know Wikipedia has strict copy infringement policies when it comes to content but it is not clear to how they apply to style templates.

By the way, how do you get the timestamp of your username when signing your replies? Do you write it out yourself or is there a wiki quickie that does it automatically?

--[[User:Sag47|Sag47]] 1018, August 24, 2010 (EST, GMT -5)

: I use four tildes ~, this is automatically replaced by my name and the date. Wanted to send you [http://www.joelonsoftware.com/articles/Biculturalism.html this article], hope you like it. --[[User:ThorstenStaerk|ThorstenStaerk]] 15:04, August 24, 2010 (UTC)

== invaluable windows tool ==

Have you ever heard of [https://sourceforge.net/projects/regshot/ regshot]? It takes a snapshot of the file system and registry before and after install and tells you the changes that have been made.

I wrote an interpreter which takes the plain txt output of regshot and converts it into an [http://nsis.sf.net/ NSIS] script which removes all entries and files added to the system.

[https://sourceforge.net/projects/registrykeyremo/ Registry Key Remover] is what it is called. It needs an update because I have to clean up the crap other developers have done. But I wrote the interpreter that converts regshot to [http://nsis.sf.net/ NSIS] script so that works 100% well.

-- [[User:Sag47|Sag47]] 18:43, August 24, 2010 (UTC)
: thank you for the pointer, I will test in my next Windows project --[[User:ThorstenStaerk|ThorstenStaerk]] 05:35, August 25, 2010 (UTC)

It's kind of like using the find, grep, and diff command together but on a Windows system (run as root)...
cd /
find / | grep -v '^/proc' > snapshot1
#install your program now
find / | grep -v '^/proc' > snapshot2
diff -crB snapshot1 snapshot2 > difference
vim difference

And thus you can see what files have been added/removed from your system when you install software. Just a thought --[[User:Sag47|Sag47]] 19:23, August 25, 2010 (UTC)

== Replied ==

Hey thorsten I replied to your user talk.
http://wiki.linuxquestions.org/wiki/Talk:Set_up_FTP_server

Is there an easy way to check what talk pages have been modified since my last login? I just caught your question by chance because I was looking over the article for errors and noticed a discussion page for it.
--[[User:Sag47|Sag47]] 02:35, October 7, 2010 (UTC)

== man ==

I was just looking at recent changes in the wiki and it's mostly filled with you. You're like a one man army!
--[[User:Sag47|Sag47]] 00:25, October 19, 2010 (UTC)

== Cannot change "link" page. ==

I created it not long ago, but can no longer save any edits to it because of some cryptic spam filter and its associated message. Any idea why?

I found the problem went away when I reconstructed the page without links to Wikipedia articles on URL and URI. I dunno why. I wonder if you were able to edit them before because moderators have more power? --[[User:4dummies|4dummies]] 13:56, April 19, 2011 (UTC)

== What I'm up to. ==

Just so you know: I'm letting myself add mere stubs with very little if any exposition because I don't dare get bogged down in details. I think I can finish coreutils in the current fashion, and do a clean-up pass before my span of attention expires. I'll have the satisfaction of completing something that really should have consistency across many pages. And at least all of the coreutils commands will have a skeleton page with a link to the author's documentation. Some, of course, already have a great deal more. But it surprised me that _none_ of them linked to the coreutils docs before I started this, but used a variety of man page sites from here and there, and it was not always clear that the man page was even for Linux.

After that, anyone can add exposition, and perhaps I'll be one of the people who does, but in lots of cases it would take me considerable effort just to do one page because it I would take the time to become _really_ proficient in each command and try to get the details right. Some of these commands are things I had never even known existed, let alone actually used, but I have a pretty clear idea about what the page structure should be.

--[[User:4dummies|4dummies]] 14:10, April 19, 2011 (UTC)

== PXE got lost ==

Somehow in sorting out double redirects, I lost track of the destination page for 'pxe boot'. I know it was there, because otherwise I would not know it stood for "Program Exexcution Environment".

However, the list of my recent contributions does not help, nor do the other searches I've tried. It seems it went into a black hole. Can you figure out what I did?
-- [[User:4dummies|4dummies]] 20:45, May 3, 2011 (UTC)
: Hehe, you talking about [[PXE]] :) --[[User:ThorstenStaerk|ThorstenStaerk]] 03:14, May 4, 2011 (UTC)
:: Yes, and they are all linked together now. Did you change something? They weren't last night, or else I had some weird caching going on in my browser. Oh, well, on I go... -- [[User:4dummies|4dummies]] 15:06, May 4, 2011 (UTC)
::: Yes, I did change something - I redirected [[pxe boot]] to [[PXE]] and so the recursion was stopped. Thanks for your work --[[User:ThorstenStaerk|ThorstenStaerk]] 19:40, May 4, 2011 (UTC)

== Who's really here? ==

I checked recent contributions, 30 days and 500 entries, and cannot find any blue names except yours and mine -- so has everyone else removed themselves, or is it just that they didn't create a user page? --[[User:4dummies|4dummies]] 19:26, May 23, 2011 (UTC)
: No one has removed themselves. I have never seen people contributing sustainably. Does this matter? --[[User:ThorstenStaerk|ThorstenStaerk]] 12:50, May 24, 2011 (UTC)
: I guess not. I will come and go myself. -- [[User:4dummies|4dummies]] 20:00, November 6, 2011 (UTC)
:: I think it matters and am certainly open to ideas on how we can get more members consistently contributing. [[User:Jeremy|Jeremy]] 16:10, November 9, 2011 (UTC)

== Blocked site ==
I tried to add a category to [bug reporting list], but the link was refused.
It said
The following text is what triggered our spam filter: http://akismet.com blacklist error
but "akismet" does not appear in the page's text. Can this be fixed? -- [[User:4dummies|4dummies]] 19:52, November 6, 2011 (UTC)

What's more, it required confirmation but allowed that link to show up in the above text. Curiouser. -- [[User:4dummies|4dummies]] 19:54, November 6, 2011 (UTC)

What I really wanted to do was add the https bugs.launchpad.net/ubuntu site, but that failed in the same way. It still fails on adding a category, so the fault's not with launchpad. Can you make this happen? -- [[User:4dummies|4dummies]] 19:59, November 6, 2011 (UTC)

: I've added you to the whitelist. Thanks for your contributions. [[User:Jeremy|Jeremy]] 16:16, November 9, 2011 (UTC)
: It worked. Thanks. -- [[User:4dummies|4dummies]] 06:51, November 11, 2011 (UTC)

== /dev/zero entry needs renaming ==

I tried to create a /dev/zero entry, like the existing /dev/urandom, but the wiki mangled it to Dev/zero. This is a poor name, and looks strange on its category page. Can you fix it to be like /dev/urandom? -- [[User:4dummies|4dummies]] 23:02, November 6, 2011 (UTC)
You'll know you've got it when they no longer show up on the uncategorized special page in spite of containing a category. -- [[User:4dummies|4dummies]] 23:18, November 6, 2011 (UTC)
: It appears there are actually two pages involved here: http://wiki.linuxquestions.org/index.php?title=/dev/zero&action=edit and http://wiki.linuxquestions.org/index.php?title=dev/zero&action=edit - looking into this further now. [[User:Jeremy|Jeremy]] 16:21, November 9, 2011 (UTC)
:: Indeed. But they're linked in a weird way. If I make a change to the first one and save it, it takes me to the page of the second one. In fact, I can see no way to link to the first one at all; it seems the wiki autoremoves the leading "/" of any wikilink.

== How to sub-categorize ==

I notice that Category:Command has sub-categories. It seems to me that Category:Application needs the same treatment.
Reading the page sources has not helped me to understand how this can be done. Any hints? [[User:4dummies|4dummies]] 07:25, November 11, 2011 (UTC)
: Answered my own question: Categorize the sub-category -- [[User:4dummies|4dummies]] 15:01, November 11, 2011 (UTC)

== I keep getting blocked by spam filter when editing the proftpd page ==
What is wrong with my user?
[[User:Sag47|Sag47]] 14:51, November 23, 2011 (UTC)

Vim

2011-02-16T20:47:00Z

Sag47:

'''vim''' ('''vi''' i'''m'''proved) is a contemporary version of the classic [[vi]] editor, with additional capabilites.

== Introduction ==
All [[UNIX]] machines typically come with the [[vi]] [[text editor]]. However, vi lacks some more contemporary features (for example, syntax highlighting). This is where '''vim''' comes in. If you know how to use vi, you'll find vim to be the same except it has a number of useful features added to make editing easier. If you don't yet know how to use vi or vim, and you didn't come from using [[ed]], you'll find the learning curve quite steep (which means, it might take you a while to learn to achieve maximum proficiency).

Vim was originally written by (and is still primarily maintained by) Bram Moolenaar. It started as a personal desire to have a useful vi-clone for the Amiga, but eventually grew as more features were added. It now runs on a variety of platforms (including Unix work-a-likes, e.g. GNU/Linux, Mac OS X, and *BSD; Amiga; Windows; Mac "Classic"; and OS/2) and supports a variety of graphical toolkits (including GTK, QT, and Carbon) in addition to the command-line interface. VIM is also the latin word for "power" or "force".

Vim has a compatibility mode which produces an almost vi-compatible experience (the version of vi used seems to be one released with Sun OS 4.x, from Version 3.7 dated on 6/7/85). This is enabled by using the ":set compatible" ex-command or by running Vim with the -C option.

== Tips ==

=== Learning ===
To learn [[vim]], [[open a console]] and call
[http://linuxcommand.org/man_pages/vimtutor1.html vimtutor]

==== A tutorial ====
While vim is not as easy to learn initially as it is to learn nano, there are plenty advantages to using it. Some great features of vim are copy, cut, and paste. Also there is code styling for programmers and there's also an undo/redo feature which is awesome.

There are three modes for vim (That I know of right now). There is the visual mode, insert mode, and the command mode. Before I start breaking down the different modes let me say this: every time you delete or copy text in the command or visual mode, the deleted text is loaded into a special buffer. This buffer continues to hold the text until you delete more text/characters/lines in which case the buffer will be replaced with the newly deleted text. I say that because the buffer is also used for copying and pasting. So if you copy text and then delete some text, the next time you paste you'll be pasting the last text you deleted instead of what you copied.

When you first open a file with command vim myfile you start out in the command mode. If the file myfile exists then it will load myfile into the editor. If the file myfile does not exist then it will create a blank file with myfile as its save path which can be modified but myfile will not be created on your hard drive until you save the document.

Pressing the i key will put the editor into insert mode. Go ahead and put the editor into insert mode and type some random text you can play with. In fact you should type a couple of lines.

Pressing the Esc while in insert mode will take the editor out of insert mode and back into command mode. Now each letter on your keyboard has turned into a command which manipulates the document instead of keys which insert text into the document.

Pressing the v key puts the editor into visual mode. Visual mode is used to highlight text in the document so you can apply different commands just to that text. If you accidentally go into visual mode or you've highlighted text and don't want to do anything to it then press the v key to go back into command mode.

While in command mode, pressing the colon key (: ) opens the editors command line where you can type a command for the editor to manipulate the whole document and not just some text or a few lines. For example in the editors command line you can save the document, quit the document, quit without saving, undo change, and redo change to name a few. You can even combine commands to do them at the same time such as save and quit at the same time.

That's most of the explanation behind it. Now remember the three modes: command, insert, and visual. Everything is centralized around the command mode. Also remember the editor command line which is accessed when in the command mode. Now that I've explained all that here is what happens when pressing different keys in the different modes.

When in command mode press the colon (: ) to enter the editor command line. Here are different editor commands.
command - explanation
{| border="1"
| :w
| write/save the document
|-
| :q
| quit vim
|-
| :q!
| quit vim without saving
|-
| :u
| undo
|-
| :r
| redo
|-
| :wq
| write/save the document and then quit vim
|}
If you accidentally enter the editor command line pressing Esc twice will put you back into command mode.

When you're in the command mode different keys have different functions. The commands are case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left
|-
| j
| move cursor down
|-
| k
| move cursor up
|-
| l
| move cursor right
|-
| w
| move the cursor right and down the document accross each word instead of each character.
|-
| ZZ
| same as :wq. write/save the document and then quit vim. Double tap the z key while holding the shift key (double click).
|-
| dd
| cuts/deletes an entire line of text. Double tab the d key (double click).
|-
| dw
| cuts/deletes a words of text
|-
| yy
| copies an entire line of text. Double tap the y key (double click).
|-
| p
| paste text after: if copied entire line then it will paste text after the current line. if copied a few characters then paste them after the current character.
|-
| P
| same as p but pastes text before the current character/line.
|-
| i
| enters editor into insert mode
|-
| o
| inserts a new line after the current line and then places the editor into insert mode.
|-
| u
| Undo the last edit. Same as :u.
|-
| v
| enters the editor into visual mode.
|-
| r
| replace. When you push a key after pressing r the letter the cursor is currently located on is replaced with the key pressed. You are still in command mode.
|-
| R
| replace. puts the editor into insert mode however it overwrites replacing each character if one already exists.
|-
| x
| delete a character
|}

When you're in insert mode every key on the keyboard types text into the document like a normal text editor. When you wish to leave insert mode press the Esc key.

When you're in the visual mode you can highlight text and apply different commands to it. The commands are similar to command mode and are also case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left (highlighting text)
|-
| j
| move cursor down (highlighting text)
|-
| k
| move cursor up (highlighting text)
|-
| l
| move cursor right (highlighting text)
|-
| y
| copy the highlighted text and enter back into command mode
|-
| d
| cut/delete the hightlighted text and enter back into command mode
|-
| p
| paste the text from the buffer replacing the highlighted text.
|}

The following command opens myfile and automatically goes to line 23.
vim +23 myfile

It's a bit of a task remembering all those commands. The best way to learn them is to try to use vim regularly referring to those commands for the different modes. There's a lot more commands and tricks you can do in vim. Those are just the basic ones.

==== Interactive tutorial ====
If you installed vim on your GNU/Linux machine then vimtutor was also installed. vimtutor is an interactive tutorial which can be run from the terminal.
vimtutor
It's easy to learn that way.

=== ~/.vimrc ===
To make a config file for vim, create a file in your home directory called .vimrc, and fill it with stuff that you'd normally type into vim's "ex" mode. For example, if you regularly do ":syntax on" from inside vim, put "syntax on" (no colon or quotes) on a line by itself in your ~/.vimrc file.

Here's the contents of a useful .vimrc file:
<pre>
syntax on
set number
set expandtab
set tabstop=4
set shiftwidth=4
set autoindent
</pre>

Where:
* "syntax on" turns on syntax highlighting
* "set number" turns on line numbers
* "set expandtab" makes vim insert spaces (instead of tabs) whenever you hit the tab key
* "set tabstop=4" sets tabs to equal 4 spaces
* "set shiftwidth=4" makes it so when you use the text shifting command, it shifts over using 4-space indents.
* "set autoindent" has vim use "smart indenting", ie. when you are tabbed out to, say, the 8th column, and you type something then hit enter, the cursor is helpfully placed at the 8th column again for you.

Additionally you can turn any single argument command off by adding an exclamation point (!). So "set number" can be turned off by "set number!"

(You can shut off line numbering from command mode by typing <tt>:set nonumber</tt>.)

=== Syntax highlighting ===

You can turn syntax highlighting on/off with:
:syntax off
:syntax on

If you have syntax highlighting on, but are using a dark background and the colors don't show up well, you can use this command:
:set background=dark

==External links==
*[http://www.vim.org Vim Homepage] (''www.vim.org'')
*[http://vi-improved.org/wiki/index.php #vim wiki] (''vi-improved.org'')

[[Category:Editors]]

Vim

2011-02-16T20:34:13Z

Sag47: /* A tutorial */

'''vim''' ('''vi''' i'''m'''proved) is a contemporary version of the classic [[vi]] editor, with additional capabilites.

== Introduction ==
All [[UNIX]] machines typically come with the [[vi]] [[text editor]]. However, vi lacks some more contemporary features (for example, syntax highlighting). This is where '''vim''' comes in. If you know how to use vi, you'll find vim to be the same except it has a number of useful features added to make editing easier. If you don't yet know how to use vi or vim, and you didn't come from using [[ed]], you'll find the learning curve quite steep (which means, it might take you a while to learn to achieve maximum proficiency).

Vim was originally written by (and is still primarily maintained by) Bram Moolenaar. It started as a personal desire to have a useful vi-clone for the Amiga, but eventually grew as more features were added. It now runs on a variety of platforms (including Unix work-a-likes, e.g. GNU/Linux, Mac OS X, and *BSD; Amiga; Windows; Mac "Classic"; and OS/2) and supports a variety of graphical toolkits (including GTK, QT, and Carbon) in addition to the command-line interface. VIM is also the latin word for "power" or "force".

Vim has a compatibility mode which produces an almost vi-compatible experience (the version of vi used seems to be one released with Sun OS 4.x, from Version 3.7 dated on 6/7/85). This is enabled by using the ":set compatible" ex-command or by running Vim with the -C option.

== Tips ==

=== Learning ===
To learn [[vim]], [[open a console]] and call
[http://linuxcommand.org/man_pages/vimtutor1.html vimtutor]

==== A tutorial ====
While vim is not as easy to learn initially as it is to learn nano, there are plenty advantages to using it. Some great features of vim are copy, cut, and paste. Also there is code styling for programmers and there's also an undo/redo feature which is awesome.

There are three modes for vim (That I know of right now). There is the visual mode, insert mode, and the command mode. Before I start breaking down the different modes let me say this: every time you delete or copy text in the command or visual mode, the deleted text is loaded into a special buffer. This buffer continues to hold the text until you delete more text/characters/lines in which case the buffer will be replaced with the newly deleted text. I say that because the buffer is also used for copying and pasting. So if you copy text and then delete some text, the next time you paste you'll be pasting the last text you deleted instead of what you copied.

When you first open a file with command vim myfile you start out in the command mode. If the file myfile exists then it will load myfile into the editor. If the file myfile does not exist then it will create a blank file with myfile as its save path which can be modified but myfile will not be created on your hard drive until you save the document.

Pressing the i key will put the editor into insert mode. Go ahead and put the editor into insert mode and type some random text you can play with. In fact you should type a couple of lines.

Pressing the Esc while in insert mode will take the editor out of insert mode and back into command mode. Now each letter on your keyboard has turned into a command which manipulates the document instead of keys which insert text into the document.

Pressing the v key puts the editor into visual mode. Visual mode is used to highlight text in the document so you can apply different commands just to that text. If you accidentally go into visual mode or you've highlighted text and don't want to do anything to it then press the v key to go back into command mode.

While in command mode, pressing the colon key (: ) opens the editors command line where you can type a command for the editor to manipulate the whole document and not just some text or a few lines. For example in the editors command line you can save the document, quit the document, quit without saving, undo change, and redo change to name a few. You can even combine commands to do them at the same time such as save and quit at the same time.

That's most of the explanation behind it. Now remember the three modes: command, insert, and visual. Everything is centralized around the command mode. Also remember the editor command line which is accessed when in the command mode. Now that I've explained all that here is what happens when pressing different keys in the different modes.

When in command mode press the colon (: ) to enter the editor command line. Here are different editor commands.
command - explanation
{| border="1"
| :w
| write/save the document
|-
| :q
| quit vim
|-
| :q!
| quit vim without saving
|-
| :u
| undo
|-
| :r
| redo
|-
| :wq
| write/save the document and then quit vim
|}
If you accidentally enter the editor command line pressing Esc twice will put you back into command mode.

When you're in the command mode different keys have different functions. The commands are case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left
|-
| j
| move cursor down
|-
| k
| move cursor up
|-
| l
| move cursor right
|-
| w
| move the cursor right and down the document accross each word instead of each character.
|-
| ZZ
| same as :wq. write/save the document and then quit vim. Double tap the z key while holding the shift key (double click).
|-
| dd
| cuts/deletes an entire line of text. Double tab the d key (double click).
|-
| dw
| cuts/deletes a words of text
|-
| yy
| copies an entire line of text. Double tap the y key (double click).
|-
| p
| paste text after: if copied entire line then it will paste text after the current line. if copied a few characters then paste them after the current character.
|-
| P
| same as p but pastes text before the current character/line.
|-
| i
| enters editor into insert mode
|-
| o
| inserts a new line after the current line and then places the editor into insert mode.
|-
| u
| Undo the last edit. Same as :u.
|-
| v
| enters the editor into visual mode.
|-
| r
| replace. When you push a key after pressing r the letter the cursor is currently located on is replaced with the key pressed. You are still in command mode.
|-
| R
| replace. puts the editor into insert mode however it overwrites replacing each character if one already exists.
|-
| x
| delete a character
|}

When you're in insert mode every key on the keyboard types text into the document like a normal text editor. When you wish to leave insert mode press the Esc key.

When you're in the visual mode you can highlight text and apply different commands to it. The commands are similar to command mode and are also case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left (highlighting text)
|-
| j
| move cursor down (highlighting text)
|-
| k
| move cursor up (highlighting text)
|-
| l
| move cursor right (highlighting text)
|-
| y
| copy the highlighted text and enter back into command mode
|-
| d
| cut/delete the hightlighted text and enter back into command mode
|-
| p
| paste the text from the buffer replacing the highlighted text.
|}

The following command opens myfile and automatically goes to line 23.
vim +23 myfile

It's a bit of a task remembering all those commands. The best way to learn them is to try to use vim regularly referring to those commands for the different modes. There's a lot more commands and tricks you can do in vim. Those are just the basic ones.

=== ~/.vimrc ===
To make a config file for vim, create a file in your home directory called .vimrc, and fill it with stuff that you'd normally type into vim's "ex" mode. For example, if you regularly do ":syntax on" from inside vim, put "syntax on" (no colon or quotes) on a line by itself in your ~/.vimrc file.

Here's the contents of a useful .vimrc file:
<pre>
syntax on
set number
set expandtab
set tabstop=4
set shiftwidth=4
set autoindent
</pre>

Where:
* "syntax on" turns on syntax highlighting
* "set number" turns on line numbers
* "set expandtab" makes vim insert spaces (instead of tabs) whenever you hit the tab key
* "set tabstop=4" sets tabs to equal 4 spaces
* "set shiftwidth=4" makes it so when you use the text shifting command, it shifts over using 4-space indents.
* "set autoindent" has vim use "smart indenting", ie. when you are tabbed out to, say, the 8th column, and you type something then hit enter, the cursor is helpfully placed at the 8th column again for you.

Additionally you can turn any single argument command off by adding an exclamation point (!). So "set number" can be turned off by "set number!"

(You can shut off line numbering from command mode by typing <tt>:set nonumber</tt>.)

=== Syntax highlighting ===

You can turn syntax highlighting on/off with:
:syntax off
:syntax on

If you have syntax highlighting on, but are using a dark background and the colors don't show up well, you can use this command:
:set background=dark

==External links==
*[http://www.vim.org Vim Homepage] (''www.vim.org'')
*[http://vi-improved.org/wiki/index.php #vim wiki] (''vi-improved.org'')

[[Category:Editors]]

User:Sag47

2010-10-21T02:38:52Z

Sag47: /* My Professional Certifications */

= My =

[http://www.gleske.net/ My website]

[[Special:Contributions/Sag47|My Contributions]]

[http://sourceforge.net/users/sag47 My Sourceforge]

[http://www.ece.drexel.edu/ My Passion]

[http://notepad-plus-plus.org/ My favorite IDE]

= My Operating Systems =
* Windows (all editions from Dos and 3.1 all the way up to Windows 7)
* Linux (many distros, once you know your way around the terminal any distro becomes more easy) [http://www.linuxfromscratch.org/ Linux From Scratch] was my most challenging.
* FreeBSD
* Mac OS (the NeXT version. I don't have any experience with OS 9)

Ordered by frequency of use.

= My Languages =
* AutoCAD
* AJAX
* Assembly (MIPs and Pentium)
* C++
* C#
* C
* CSS
* CVS
* Cypress PSoC 3/PSoC Designer
* DHTML
* HTML
* Java
* JavaScript
* Labview
* Linux Shell
* Maple
* Matlab
* MySQL
* Neuron C
* NSIS
* PHP
* Python
* Subversion
* UPMACS
* VHDL
* Windows Batch/INI/CSV
* XHTML
* XML
= My Life in meatspace =
Gun shooting (pistol, skeet, rifle, you name it and I love it), scuba diving, sailing (15 yrs), motocross racing and fourwheeling (trucks and quads) (8 yrs), microprocessor design, wake boarding, snow boarding (18 yrs), skiing (19 yrs), repelling, caving, jetski riding (this one is recent and a blast), roller hockey, cycling, riding motorcycles, driving manual cars, going out dancing, studying and reading on subjects of interest (which include everything), and tons more which I can't think of off the top of my head. That's all stuff I try to do as often as possible. My list would be bigger if I was rich and had unlimited time. All of it is in no particular order. I have a passion for most of what I do and try to learn it to a professional level.

= My Professional Certifications =
* BS Electrical and Computer Engineering Dual Major, anticipated and in progress
* CompTIA A+ Certification, 2004
* CompTIA Network+ Certification, 2005
* [http://www.pages.drexel.edu/~sag47/scuba_diving.html PADI Certifications]

= My Plans =
Most people say I would do well as a computer science major. But that is just a hobby and Linux is something I enjoy participating in my free time.

As a professional I want to design microprocessors and so Engineering is the path I chose. I may master in something like Biomedical Engineering in the future but that is far off and only because I feel processors of the future will contain biological components since we are reaching the limits to the size of atoms with processors in modern day for electrical paths. Now instead of decreasing size and increasing speed (Hz) they are adding cores and improving CPI (cycles per instruction) time with lowered cycle rates. It won't be long before our electronics depend on chemical signals for processing much like our brain depends on.

This is the future I see and want to be a part of. I have many other plans but those are secret ;)

User talk:ThorstenStaerk

2010-10-19T00:25:09Z

Sag47: /* man */

User talk:ThorstenStaerk

2010-10-19T00:24:51Z

Sag47: /* man */ new section

Regshot for Linux

2010-10-19T00:22:24Z

Sag47: /* Regshot for Linux */

{{PageAuthor|Sag47}}
== Introduction ==
There are two primary tools for Windows which make analyzing the file system and registry easy for Windows installed programs. [http://sourceforge.net/projects/regshot/ Regshot] and [http://sourceforge.net/projects/registrykeyremo/ Registry Key Remover] are compliments of each other designed to take snapshots of a Windows system before and after and then generate an [http://nsis.sourceforge.net/ NSIS] script which can be compiled to undo the changes.

This small guide was written to replicate the functionality of those programs but use Linux native commands which are already designed to do that.
== Regshot for Linux ==
Unix provides multiple tools for easily recreating the functionality of the Windows utility Regshot. The first method I show only allows one to view which files have been added or removed. The second method only reveals which files have been changed or removed. It is recommended to use both methods to figure out what files have been added, removed, or changed.

If you're using this functionality because you have a problem with your system then you may want to [http://www.linuxquestions.org/questions/blog/sag47-492023/kernel-panic-3242/ check my blog] for how to effectively search your system logs for keywords.

=== Compare for files added/removed ===
This method uses the find command to list out the file system before and after an install. Then by comparing the two listings one could figure out what files have specifically been added/removed. This method does not work, however, for files which have been changed. Skip to the next section for finding files which have been changed.

Run the following commands as root. This will replicate the functionality of regshot which takes two snapshots and then compares the differences.
find / | grep -v '^/proc' > snapshot1

#Install software on to your system. After you install the software continue.

find / | grep -v '^/proc' > snapshot2
diff -crB snapshot1 snapshot2 > changes

Now you can view the changes that were made by your system in a pager (less) or the editor vim (use :q to quit).
less changes
vim changes

=== Compare for files changed/removed ===
This method uses the find command to list out the filesystem and then run an md5 checksum on every file. This method allows the user to figure out which files have been changed by an install by checking all files against their md5 checksums. If any checksums fail then it means the file has either been changed or deleted. One could use grep to further filter out failed checksums for deleted files to list just files which have been changed.

Run the following commands as root and be sure to be mindful of your working directory when working with the output files.
find / -type f -wholename '/proc' -prune -print0 | xargs -0 md5sum | tee md5sum.txt

Now install your software and check your whole filesystem against the previously generated md5 checksums.
md5sum -c md5sum.txt 2> /dev/null | grep -i 'FAIL' > failed.txt

Now you can view the changes that were made by your system in a pager (less) or the editor vim (use :q to quit).
less failed.txt
vim failed.txt

=== Things to notice ===
You may have already noticed this but then again you may not if you're new to Linux. In all of the above commands I have excluded the /proc directory because it is associated with the PIDs of currently running processes. Basically you don't need to list these our or checksum it because you can't. It is best to leave it alone in this instance.

[[Category:Guides]]

Talk:Regshot for Linux

2010-10-19T00:18:13Z

Sag47:

good, now how do we relate this to
strace -e open
? --[[User:ThorstenStaerk|ThorstenStaerk]] 20:32, August 25, 2010 (UTC)
: I've been reading the man page on [http://linux.die.net/man/1/strace strace]. Since I've never worked with it then it may take a little while for me to figure out how it effectively works. I certainly wouldn't mind knowing how to utilize it. It reminds me of using [http://unixhelp.ed.ac.uk/CGI/man-cgi?strings strings] on a binary file to dump all strings out of it :). --[[User:Sag47|Sag47]] 00:18, October 19, 2010 (UTC)

Regshot for Linux

2010-10-19T00:10:56Z

Sag47:

{{PageAuthor|Sag47}}
== Introduction ==
There are two primary tools for Windows which make analyzing the file system and registry easy for Windows installed programs. [http://sourceforge.net/projects/regshot/ Regshot] and [http://sourceforge.net/projects/registrykeyremo/ Registry Key Remover] are compliments of each other designed to take snapshots of a Windows system before and after and then generate an [http://nsis.sourceforge.net/ NSIS] script which can be compiled to undo the changes.

This small guide was written to replicate the functionality of those programs but use Linux native commands which are already designed to do that.
== Regshot for Linux ==
Unix provides multiple tools for easily recreating the functionality of the Windows utility Regshot. The first method I show only allows one to view which files have been added or removed. The second method only reveals which files have been changed or removed. It is recommended to use both methods to figure out what files have been added, removed, or changed.

If you're using this functionality because you have a problem with your system then you may want to [http://www.linuxquestions.org/questions/blog/sag47-492023/kernel-panic-3242/ check my blog] for how to effectively search your system logs for keywords.

=== Compare for files added/removed ===
This method uses the find command to list out the file system before and after an install. Then by comparing the two listings one could figure out what files have specifically been added/removed. This method does not work, however, for files which have been changed. Skip to the next section for finding files which have been changed.

Run the following commands as root. This will replicate the functionality of regshot which takes two snapshots and then compares the differences.
find / | grep -v '^/proc' > snapshot1

#Install software on to your system. After you install the software continue.

find / | grep -v '^/proc' > snapshot2
diff -crB snapshot1 snapshot2 > changes

Now you can view the changes that were made by your system in a pager (less) or the editor vim (use :q to quit).
less changes
vim changes

=== Compare for files changed/removed ===
This method uses the find command to list out the filesystem and then run an md5 checksum on every file. This method allows the user to figure out which files have been changed by an install by checking all files against their md5 checksums. If any checksums fail then it means the file has either been changed or deleted. One could use grep to further filter out failed checksums for deleted files to list just files which have been changed.

Run the following commands as root and be sure to be mindful of your working directory when working with the output files.
find . -type f -wholename './proc' -prune -print0 | xargs -0 md5sum | tee md5sum.txt

Now install your software and check your whole filesystem against the previously generated md5 checksums.
md5sum -c md5sum.txt 2> /dev/null | grep -i 'FAIL' > failed.txt

Now you can view the changes that were made by your system in a pager (less) or the editor vim (use :q to quit).
less failed.txt
vim failed.txt

[[Category:Guides]]

Regshot for Linux

2010-10-19T00:08:52Z

Sag47:

{{PageAuthor|Sag47}}
== Introduction ==
There are two primary tools for Windows which make analyzing the file system and registry easy for Windows installed programs. [http://sourceforge.net/projects/regshot/ Regshot] and [http://sourceforge.net/projects/registrykeyremo/ Registry Key Remover] are compliments of each other designed to take snapshots of a Windows system before and after and then generate an [http://nsis.sourceforge.net/ NSIS] script which can be compiled to undo the changes.

This small guide was written to replicate the functionality of those programs but use Linux native commands which are already designed to do that.
== Regshot for Linux ==
Unix provides multiple tools for easily recreating the functionality of the Windows utility Regshot. The first method I show only allows one to view which files have been added or removed. The second method only reveals which files have been changed or removed. It is recommended to use both methods to figure out what files have been added, removed, or changed.

If you're using this functionality because you have a problem with your system then you may want to [http://www.linuxquestions.org/questions/blog/sag47-492023/kernel-panic-3242/ check my blog] for how to effectively search your system logs for keywords.

=== Compare for files added/removed ===
This method uses the find command to list out the file system before and after an install. Then by comparing the two listings one could figure out what files have specifically been added/removed. This method does not work, however, for files which have been changed. Skip to the next section for finding files which have been changed.

Run the following commands as root. This will replicate the functionality of regshot which takes two snapshots and then compares the differences.
find / | grep -v '^/proc' > snapshot1

#Install software on to your system. After you install the software continue.

find / | grep -v '^/proc' > snapshot2
diff -crB snapshot1 snapshot2 > changes

Now you can view the changes that were made by your system in a pager (less) or the editor vim (use :q to quit).
less changes
vim changes

=== Compare for files changed/removed ===
This method uses the find command to list out the filesystem and then run an md5 checksum on every file. This method allows the user to figure out which files have been changed by an install by checking all files against their md5 checksums. If any checksums fail then it means the file has either been changed or deleted. One could use grep to further filter out failed checksums for deleted files to list just files which have been changed.

Run the following commands as root and be sure to be mindful of your working directory when working with the output files.
find / -type f -print0 | xargs -0 md5sum | tee md5sum.txt

Now install your software and check your whole filesystem against the previously generated md5 checksums.
md5sum -c md5sum.txt 2> /dev/null | grep -i 'FAIL' > failed.txt

Now you can view the changes that were made by your system in a pager (less) or the editor vim (use :q to quit).
less failed.txt
vim failed.txt

[[Category:Guides]]

User talk:ThorstenStaerk

2010-10-07T02:35:04Z

Sag47: /* Replied */

Talk:Set up FTP server

2010-10-06T20:58:28Z

Sag47:

why would I need to have [[apache]] [[install]]ed? --[[User:ThorstenStaerk|ThorstenStaerk]] 13:07, August 21, 2010 (UTC)

:Apache needs to be installed because in the tutorial I show how to get an FTP login specifically for web servers/directories. [http://www.linuxquestions.org/questions/linux-server-73/a-simple-ftp-server-825926/ A user in the LQ Forum] had asked how to install FTP to modify their web directory content. This wiki article spawned out of my response for that. It can be removed to be more generic but that user specifically said that they couldn't find information like that all in one place so I thought this to be a valuable article. --[[User:Sag47|Sag47]] 20:53, October 6, 2010 (UTC)

User talk:ThorstenStaerk

2010-10-06T20:56:13Z

Sag47: /* Replied */ new section

Talk:Set up FTP server

2010-10-06T20:54:31Z

Sag47:

why would I need to have [[apache]] [[install]]ed? --[[User:ThorstenStaerk|ThorstenStaerk]] 13:07, August 21, 2010 (UTC)

:Apache needs to be installed because in the tutorial I show how to get an FTP login specifically for web servers/directories. A user in the LQ Forum had asked how to install FTP to modify their web directory content. This wiki article spawned out of my response for that. It can be removed to be more generic but that user specifically said that they couldn't find information like that all in one place so I thought this to be a valuable article. --[[User:Sag47|Sag47]] 20:53, October 6, 2010 (UTC)

Talk:Set up FTP server

2010-10-06T20:53:44Z

Sag47:

why would I need to have [[apache]] [[install]]ed? --[[User:ThorstenStaerk|ThorstenStaerk]] 13:07, August 21, 2010 (UTC)

Apache needs to be installed because in the tutorial I show how to get an FTP login specifically for web servers/directories.
A user in the LQ Forum had asked how to install FTP to modify their web directory content. This wiki article spawned out of my response for that.
It can be removed to be more generic but that user specifically said that they couldn't find information like that all in one place so I thought this to be a valuable article.
[[User:Sag47|Sag47]] 20:53, October 6, 2010 (UTC)

Talk:Set up FTP server

2010-10-06T20:53:29Z

Sag47:

why would I need to have [[apache]] [[install]]ed? --[[User:ThorstenStaerk|ThorstenStaerk]] 13:07, August 21, 2010 (UTC)

Apache needs to be installed because in the tutorial I show how to get an FTP login specifically for web servers/directories.

A user in the LQ Forum had asked how to install FTP to modify their web directory content. This wiki article spawned out of my response for that.

It can be removed to be more generic but that user specifically said that they couldn't find information like that all in one place so I thought this to be a valuable article.

User talk:Genogebot

2010-08-26T00:13:07Z

Sag47: Created page with 'So you use Linux Mint huh? What's that experience like? --~~~~'

So you use Linux Mint huh? What's that experience like? --[[User:Sag47|Sag47]] 00:13, August 26, 2010 (UTC)

Regshot for Linux

2010-08-25T19:45:35Z

Sag47: /* Regshot for Linux */

{{PageAuthor|Sag47}}
== Introduction ==
There are two primary tools for Windows which make analyzing the file system and registry easy for Windows installed programs. Regshot and Registry Key Remover are compliments of each other designed to take snapshots of a Windows system before and after and then generate an NSIS script which can be compiled to undo the changes.

This small guide was written to replicate the functionality of those programs but use Linux native commands which are already designed to do that.
== Regshot for Linux ==
Run the following commands as root. This will replicate the functionality of regshot which takes two snapshots and then compares the differences.
find / | grep -v '^/proc' > snapshot1

#Install software on to your system. After you install the software continue.

find / | grep -v '^/proc' > snapshot2
diff -crB snapshot1 snapshot2 > changes

Now you can view the changes that were made by your system in vim (use :q to quit).
vim changes

[[Category:Guides]]

Regshot for Linux

2010-08-25T19:45:12Z

Sag47: Created page with '{{PageAuthor|Sag47}} == Introduction == There are two primary tools for Windows which make analyzing the file system and registry easy for Windows installed programs. Regshot an…'

Howto

2010-08-25T19:34:31Z

Sag47: /* Disk and archive manipulation */

A '''Howto''', '''Tutorial''' or '''Guide''' is a ''documentation for accomplishing tasks''. If you wish to find a listing of all howtos on this wiki, look at the [[:Category:Guides|Category Guides]].

Here is a selection:

= Introducing Linux =
* [[LinuxIntro]] - your starting point
** [[Choose a Linux distribution]]
** [[install Linux]]
** [[open a console]]
* [[Interoperability]]
** [[Run Windows software]]
** [[Share files with Windows]]
** [[Install Windows fonts]]
** [[Beginner's Command Line]] - migrating from windows to the linux command line

= Disk and archive manipulation =
* [[Clone a disk using dd]]
* [[Configure storage devices]]
* [[Create software RAID and volume groups]]
* [[Embed a zip file into an image]]
* [[Make a USB disk bootable]]
* [[Make backups]]
* [[Encrypt a disk]]
* [[Regshot for Linux]]
* [[Pack and unpack files]]

= Setup and Office =
* [[Creating startup scripts]]
* Do [[Office tasks]] - word processing, spreadsheet, presentation, image manipulation and other
* [[Install Software]]
* [[Print]]
* [[Scan]]
* [[Schedule Tasks]]
* [[Set up lm sensors]] - for monitoring CPU/Motherboard temperature, fan speeds, voltage information, etc.
* [[Browsing tasks|Surf the web]] / [[Connect to the net]]
= Fun Stuff =
* [[Burn a CDROM]]
* Play [[Games]]
* Do [[Multimedia tasks]] - listen to music, extract CDs, watch videos and DVDs
** [[Configure Sound]]
** [[make your computer speak]]
** [[Use Digital Cameras and Linux]]
** [[Use Camcorders and Linux]]
** [[Use Webcams and Linux]]
** [[Watch tv]]
* [[Talk to friends online]] - how to access common instant messaging networks, see also [[IM]].

= See also =
* [[TroubleShooting]] - you have a problem and need a solution
* [[Tips & Tricks]] - you want new ideas

Howto

2010-08-25T19:34:20Z

Sag47: /* Disk and archive manipulation */

A '''Howto''', '''Tutorial''' or '''Guide''' is a ''documentation for accomplishing tasks''. If you wish to find a listing of all howtos on this wiki, look at the [[:Category:Guides|Category Guides]].

Here is a selection:

= Introducing Linux =
* [[LinuxIntro]] - your starting point
** [[Choose a Linux distribution]]
** [[install Linux]]
** [[open a console]]
* [[Interoperability]]
** [[Run Windows software]]
** [[Share files with Windows]]
** [[Install Windows fonts]]
** [[Beginner's Command Line]] - migrating from windows to the linux command line

= Disk and archive manipulation =
* [[Clone a disk using dd]]
* [[Configure storage devices]]
* [[Create software RAID and volume groups]]
* [[Embed a zip file into an image]]
* [[Make a USB disk bootable]]
* [[Make backups]]
* [[Regshot for Linux]]
* [[Encrypt a disk]]
* [[Pack and unpack files]]

= Setup and Office =
* [[Creating startup scripts]]
* Do [[Office tasks]] - word processing, spreadsheet, presentation, image manipulation and other
* [[Install Software]]
* [[Print]]
* [[Scan]]
* [[Schedule Tasks]]
* [[Set up lm sensors]] - for monitoring CPU/Motherboard temperature, fan speeds, voltage information, etc.
* [[Browsing tasks|Surf the web]] / [[Connect to the net]]
= Fun Stuff =
* [[Burn a CDROM]]
* Play [[Games]]
* Do [[Multimedia tasks]] - listen to music, extract CDs, watch videos and DVDs
** [[Configure Sound]]
** [[make your computer speak]]
** [[Use Digital Cameras and Linux]]
** [[Use Camcorders and Linux]]
** [[Use Webcams and Linux]]
** [[Watch tv]]
* [[Talk to friends online]] - how to access common instant messaging networks, see also [[IM]].

= See also =
* [[TroubleShooting]] - you have a problem and need a solution
* [[Tips & Tricks]] - you want new ideas

User talk:ThorstenStaerk

2010-08-25T19:25:46Z

Sag47: /* invaluable windows tool */

User talk:ThorstenStaerk

2010-08-25T19:23:50Z

Sag47: /* invaluable windows tool */

Connect to a wireless local area network

2010-08-25T17:45:34Z

Sag47: /* Autostarting network configuration */

This covers how to get '''wireless''', or '''Wi-Fi''' [[networks]] to work under Linux, and the various applications that go along with them.

= Start =
You should start by means of your [[distribution]] - most probably, it works out of the box. Make sure you enabled WLAN on your laptop (there is mostly a button for it). Put it next to your WLAN router. Install your WLAN card as a network card, it will be called eth1,wlan0 or so. Use <code>[[iwconfig]]</code> to find out how it is called. You should be able to scan for wireless networks then, e.g. by
$ iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 00:0F:C9:01:F5:F4
ESSID:"foo"
Mode:Managed
Channel:10
Encryption key:off
Bit Rates:0 kb/s

$

If you get a <code>Command not found</code> error, install the [[Wireless tools]] and try again. 
If you do not get a list like the above, see the next section [[#Wireless_Configuration|Wireless configuration]]. 
If it works, you can continue with the section [[#Connect_to_an_Accesspoint|Connect to an Accesspoint]].

= Wireless Configuration =
The following provides the general steps required to get wireless networking enabled on your Linux machine.

== Gaining root access ==

[[open a console]] and type ''su'' to log into root (you must type your root password. If you're on an Ubuntu-like where the root user is disabled then don't bother typing ''su'' but instead add ''sudo'' at the beginning of each command. If you're on Ubuntu and, like me, hate using the sudo command so much then run ''sudo bash'' which logs you into root just like su.

== Find out your wifi card's chipset ==

In order to get your card working you will have to determine its chipset.
There is one, generic, way for [http://en.wikipedia.org/wiki/Conventional_PCI PCI] and [http://en.wikipedia.org/wiki/PC_Card PCMCIA] cards, and one for [[USB]] cards:

*'''The generic way'''
**Run "[[hwinfo]] --wlan"
:If this command does not succeed, this can mean that you have an old [[kernel]] that does not recognize your card as a WLAN card. In this case, you cannot use it. Anyway, to find out its type use <code>hwinfo --[http://en.wikipedia.org/wiki/Conventional_PCI pci]</code> or <code>hwinfo --pcmcia</code>.

*'''Methods for [[USB]] cards'''
**Run <code>hwinfo --usb</code>.
:This will give you information about the chipset and tell you a ''Driver activation command'' (like "modprobe rt73usb").

Hopefully you now have a chipset name but...

== Which driver to load and how? ==

To find out which driver you have to load, use
hwinfo --wlan|grep -i driver
See below for additional relevant information on given chipsets or drivers.

'''Open Source'''
* [[WiFi Link 5100]]
* [[Intel PRO/Wireless 3945ABG]]
* [[Intel_Pro_Wireless]] 2100/2200/2915 -- Note that this requires http://sourceforge.net/projects/ieee80211
** ipw2200 on Suse 10.0, see [[Suse100ipw2200]]
* Prism 2/2.5/3: [[Prism_2_Drivers]]
* Ralink RT2400/2500, RT61, RT73: [[Ralink_Wireless_Drivers]]
* Atheros AR5210/5211/5212: [[MADWIFI]]
* Prism GT/Duette/Indigo: [[Prism54]]
* [[Broadcom 4318 Airforce one 54g card]]
* Texas Instruments ACX100/111: [http://acx100.sourceforge.net/ acx100]
* Atmel: [[AT76C5XXx]]
* [[Belkin_F5D6020_ver.2]]
* [[Net_Gear_WG121_on_Mandrake_10.0_Linux]]
* Linksys [[WMP54G Wireless how-to for Ubuntu 8.10]] Intrepid Ibex
* Almost every other chipset: [[NDIS_Wrapper]]
'''Proprietary'''
* [[Linuxant Driverloader]]

Note that [[building]] a [[kernel module]] requires the kernel sources.
Download your driver sources in .tar.gz format and [[compile from source]].

= Connect to an Accesspoint =

This chapter covers how to connect to an unencrypted or WEP encrypted accesspoint. [[wpa|For WPA encryption, have a look here]]. The example interface will be called wlan0.

To set up the interface, start by:

$ ifconfig wlan0 up

If you want, you could scan for an accesspoint first:

$ iwlist wlan0 scanning

You will then see the available accesspoints, their ESSID's, the frequency, etc.
To associate with an accesspoint (for example "test"), run:
$ iwconfig wlan0 essid test
Most drivers will automatically find the right channel in a minute.
You should now be able to see something like this when you run iwconfig:
$ iwconfig
lo no wireless extensions

wlan0 IEEE 802.11b ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key: off
Power Management:off
Link Quality=0/0 Signal level=0/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This means that everything has been installed properly.

== Using WEP encryption ==

If the accesspoint uses WEP, you set the encryption like so:
$ iwconfig wlan0 key s:"the_ascii_key"
Or you can use a hexadecimal key:
$ iwconfig wlan0 key 00000000000
The bits of encryption is determined by the key length. Note that this command, along with the key, can be seen in "ps aux".

# ifconfig ath0 down
# iwconfig ath0 essid disaster-master enc 1234abcdef mode Managed channel auto
# ifconfig ath0 up
# dhclient ath0

If you don't like typing a large command sequence to reconnect your login each time then here is a helpful script which can speed up the process.
#!/bin/sh
#this is a comment
#all commands must be run as root (script must be run as root or as startup script)

#Router WEP settings
iface=ath0
ssid=disaster-master
wephexkey=1234abcdef
chan=auto

#setting up and applying wireless config, no need to edit beyond this point
ifconfig $iface down
iwconfig $iface essid $ssid enc $wephexkey mode Managed channel $chan
ifconfig $iface up
dhclient $iface

== Use WPA/WPA2 Personal ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-PSK or WPA2-PSK.

My network SSID is called disaster-master and it's currently running WPA2-PSK encryption on it. My WPA2 passphrase is "hindrance".

First create two text files and save them as wireless-wpa.sh and wireless-wpa.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa.sh'''
#!/bin/sh
iface=ath0

#shut down interface
ifconfig $iface down

#set ad-hoc/management of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#stop any persistent wireless wpa2 sessions
killall wpa_supplicant

#apply WPA/WPA2 personal settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa.conf'''
# disaster-master network using WPA2-PSK

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="disaster-master"
scan_ssid=1
key_mgmt=WPA-PSK
psk="hindrance"
}
Don't forget to edit wireless-wpa.sh and set iface equal to your wireless device and edit wireless-wpa.conf with your WPA settings. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''). Run the following command sequence:
# chmod 755 wireless-wpa.sh
# chmod 644 wireless-wpa.conf
# ./wireless-wpa.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa.sh every time you restart your computer.

You can read up on the wpa_supplicant setup by viewing it's man pages. Just type:
man wpa_supplicant
man wpa_supplicant.conf

== Use WPA/WPA2 Enterprise ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-Enterprise or WPA2-Enterprise.

My enterprise network SSID is called dragonfly3 and it has a radius login server at radius.irt.drexel.edu (which is automatically detected and not needed to be set up). The Enterprise network is currently running WPA2-Enterprise encryption with IEEE 802.1X login using EAP-TTLS/MSCHAPv2. My login (not real) at radius.irt.drexel.edu is "abc123" and my password is "hindrance".

First create two text files and save them as wireless-wpa-enterprise.sh and wireless-wpa-enterprise.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa-enterprise.sh'''
#!/bin/sh
iface=ath0

#stop any persistent wireless wpa2 authentication sessions
killall wpa_supplicant

#shut down wireless interface
ifconfig $iface down

#set working mode of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#apply dragonfly3 settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa-enterprise.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa-enterprise.conf'''
# Drexel dragonfly3 IEEE 802.1X login using EAP-TTLS/MSCHAPv2

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dragonfly3"
scan_ssid=0
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS
phase2="auth=MSCHAPV2"
identity="abc123"
password="hindrance"
}
Don't forget to edit wireless-wpa-enterprise.sh and set iface equal to your wireless device and edit wireless-wpa-enterprise.conf with your network SSID and enterprise login information. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''. Run the following command sequence:
# chmod 755 wireless-wpa-enterprise.sh
# chmod 644 wireless-wpa-enterprise.conf
# ./wireless-wpa-enterprise.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa-enterprise.sh every time you restart your computer.

You can read up on the wpa_supplicant setup by viewing it's man pages. Just type:
man wpa_supplicant
man wpa_supplicant.conf

== Getting an IP address ==

If you have associated properly, you should see the accesspoint's mac address in from iwconfig instead of 00:00:00:00:00:00. If the network you have connected to uses dhcp, it is time to obtain an ip address:
$ dhclient wlan0
Or:
$ dhcpcd wlan0
You should see "DHCPOFFER" or similar in a minute if all went well. If it sits there for a while with no DHCPOFFER, then something is wrong. Perhaps the encryption key was incorrect.

However, if you would connect to a AP that doesn't have a dhcp server, you can do the following:

First scan for the AP so you can see the ESSID and the mac address. Do the following
$ iwconfig wlan0 essid "MyAP" (if that's the ESSID)
$ iwconfig wlan0 ap 00:40:CA:45:10:9C (if that's the mac)
$ ifconfig wlan0 192.168.0.20 up
$ route add -net default gw 192.168.0.1
Provided that the AP has the IP 192.168.0.1.

== Autostarting network configuration ==
I found a really good post which tells you how to do this [http://www.howtoforge.com/forums/showthread.php?p=22384#post22384 located here] and create the necessary system startup links. Depending on your distribution you can do it with chkconfig (RedHat, Fedora, CentOS, Mandriva, SuSE) or update-rc.d (Debian, Ubuntu). I'm going to proceed explaining how to manually set up a startup script rather than using the automated method like update-rc.d. This is per the documentation from the [http://www.debian.org/doc/debian-policy/ch-opersys.html Debian Policy Manual Section 9.3].

The directory for startup scripts is located in ''/etc/rcS.d''. Do a quick listing and see what is in your bootup script directory using ''ls /etc/rcS.d'':
: '''ls /etc/rcS.d'''
README S35mountall.sh
S01mountkernfs.sh S36mountall-bootclean.sh
S01readahead S37apparmor
S02hostname.sh S37mountoverflowtmp
S06keyboard-setup S37udev-finish
S07linux-restricted-modules-common S39readahead-desktop
S08hwclockfirst.sh S39ufw
S08loopback S40networking
S10udev S45mountnfs.sh
S11hwclock.sh S46mountnfs-bootclean.sh
S11mountdevsubfs.sh S49console-setup
S13pcmciautils S55bootmisc.sh
S15module-init-tools S55dns-clean
S17procps S55pppd-dns
S20checkroot.sh S55urandom
S22mtab.sh S70screen-cleanup
S25brltty S70x11-common
S30checkfs.sh S90console-screen.kbd.sh
Here is what my readme readme says:
: '''cat /etc/rcS.d/README'''
The scripts in this directory whose names begin with an 'S' are executed
once when booting the system, even when booting directly into single user
mode.

The scripts are all symbolic links whose targets are located in
/etc/init.d/ .

To disable a script in this directory, rename it so that it begins with
a 'K'.

For more information see /etc/init.d/README.

The following sequence points are defined at this time:

* After the S40 scripts have executed, all local file systems are mounted
and networking is available. All device drivers have been initialized.

* After the S60 scripts have executed, the system clock has been set, NFS
filesystems have been mounted (unless the system depends on the automounter,
which is started later) and the filesystems have been cleaned.
As a quick side note, if you are using WPA then you need to edit your ''wireless-wpa.sh'' script and change ''./wireless-wpa.conf'' to ''/etc/init.d/wireless-wpa.conf''. Here's the newly formatted command:
wpa_supplicant -B -Dwext -i $iface -c /etc/init.d/wireless-wpa.conf -dd
And also please note from the README that ''"After the S40 scripts have executed, all local file systems are mounted and networking is available. All device drivers have been initialized."'' As you can see from my listing that I have no S41 script so I'm going to make that my wireless networking startup script and call it ''S41wlan_net_connect'' (you can call it ''S41'' whatever you want if you don't like it). Browse to the directory where you have your wireless-wpa.sh, then switch to root user and run the following command sequence:
cp ./wireless-wpa.sh /etc/init.d/wireless-wpa.sh
cp ./wireless-wpa.conf /etc/init.d/wireless-wpa.conf
chmod 755 /etc/init.d/wireless-wpa.sh
chmod 644 /etc/init.d/wireless-wpa.conf
ln -s /etc/init.d/wireless-wpa.sh /etc/rcS.d/S41wlan_net_connect
We just finished creating the symbolic link (ln -s) so now test it by restarting. It should be set up as a startup script now.

=== Turn off wireless Tx when computer starts ===
I used the iwconfig utility to switch off power to the wireless card at startup, and wrote a shell script to switch it back on again when I need to use it.

I added this line to the /etc/rc.local file:

/sbin/iwconfig wlan0 txpower off

and that powers off the wireless card at boot time.

The shell script just reverses that, and brings the card into the 'up' network state:

#!/bin/bash
sudo /sbin/iwconfig wlan0 txpower on
sleep 1
sudo /sbin/ifconfig wlan0 up

= Create an access point =

It is fairly simple to setup an AP in linux. This is how I did.

I purchased a D-Link DWL-G520 pci card. You need a card that supports Master mode. Check [http://linux-wless.passys.nl this] (''linux-wless.passys.nl'') site for compatibility with Linux, I think ndiswrapper doesn't have support for Master mode, not sure though.

'''Creating the AP'''

Then if your interface is ath0:

$ iwconfig ath0 mode Master
$ iwconfig ath0 essid "LinuxAP"
$ ifconfig ath0 192.168.1.1 up

I chose an IP that wasn't in my wired LANs subnet.
Now you should be able to see the AP if you scan for APs.

'''Configure statically your client's card'''

Then on the client side (if your interface is ath0) you do:

$ iwconfig ath0 mode Managed
$ iwconfig essid "LinuxAP"
$ iwconfig ap 00:11:22:AA:22:11
$ ifconfig ath0 192.168.1.10 netmask 255.255.255.0 up
$ route add -net default gw 192.168.1.1

It's not always necessary to specify the mac address for the ap, but sometimes it's a good thing. As you can see I chose an ip that was in the same subnet as the ap, it's important.

== DHCP server, firewall and stuff ==

Now, that was the static ip way and you probably want a dhcp-server and some firewall-rules for the ap. Guess what... here they come!

'''iptables'''

I have some rules with iptables in a script:

#!/bin/sh
IPTABLES='/sbin/iptables'
EXTIF='eth0'
INTIF='eth1'
WLAN='ath0'
WAN='85.235.31.133'

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

$IPTABLES -F
$IPTABLES -X

$IPTABLES -X -t nat
$IPTABLES -F -t nat

$IPTABLES -X -t filter
$IPTABLES -F -t filter

# enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

# forward LAN traffic from $INTIF1 to Internet interface $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

# allow ping
$IPTABLES -A INPUT -p icmp -i $EXTIF -j ACCEPT

# Allowing access to the FTP server"
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 21 -j ACCEPT

# Allowing access to the ssh server on port 2200 (I've changed it)
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 2200 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP

'''dnsmasq'''

And my dnsmasq.config looks like this:

resolv-file=/etc/resolv.conf
no-poll
domain-needed
bogus-priv
strict-order

interface=ath0
dhcp-range=192.168.1.10,192.168.1.50,12h

interface=eth1
dhcp-range=192.168.0.10,192.168.0.50,12h

# alice and bob are declared in /etc/hosts
dhcp-host=00:0A:E4:52:6B:12,alice
dhcp-host=00:40:CA:45:10:9C,bob

dhcp-authoritative

And that's it! Just run the script, start dnsmasq and connect to the ap described in the top of this wiki.

'''stuff'''

By the way, if you want to ping some host in the 192.168.0.0 subnet make sure that you don't have another interface that's not alive with an ip in that subnet. So if you have an ordinary wired card eth0 with an ip in the 192.168.0.0 subnet (but no cable in maybe) make sure that you bring that interface down.
$ ifconfig eth0 down
Now you can ping hosts in that subnet with your wifi card.

= External links =
== Howtos,Guides ==
*[http://www-106.ibm.com/developerworks/library/wi-enable.html?ca=dgr-lnxw82Linux4Wireless A nice overview] (''www-106.ibm.com'')
*[http://www.rustyspigot.com/groovyweb/?page_name=Linux%20Wireless&category=linux Wireless Tutorial] (''www.rustyspigot.com'')
*[http://www.ubuntuforums.org/showthread.php?t=202834 Wireless Security - WPA1 WPA2 LEAP AES, etc.] (''www.ubuntuforums.org'')

== Chipset list ==
*[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz list of all possible wlan chipsets] (''wiki.uni-konstanz.de'')
*[http://linux-wless.passys.nl Supported cards by manufacturer, chipset and interface (PCI, USB, PCMCIA)] (''linux-wless.passys.nl'')

== Specific cards ==
*[http://www.wmconnolley.org.uk/linux-wireless.html D-LINK DWL-650 (and/or DRC-650) under RH 8.0, kernel 2.4.18] (''www.wmconnolley.org.uk'')
*[http://www.netdigix.com/downloads/debian-linksys-wireless-howto.html Linksys WMP54G - 802.11G - kernel 2.4 - debian 3.0] (''www.netdigix.com'')
*[http://kennethjor.blogspot.com/2006/10/linksys-wusb54gc-ralink-rt73-and.html Linksys WUSB54GC - kernel 2.6.15 - Ubuntu 6.06] (''kennethjor.blogspot.com'')
*[http://wwwu.uni-klu.ac.at/agebhard/WUSB54GC/ Kernel module package for Ralink RT73 based USB WLAN adapters, such as Linksys WUSB54GC - Kernel 2.6.15 - Ubuntu 6.06] (''www.uni-klu.ac.at'')

[[Category:Networking]]
[[Category:Example]]
[[Category:Guides]]

User talk:ThorstenStaerk

2010-08-24T18:43:54Z

Sag47: /* invaluable windows tool */

User talk:ThorstenStaerk

2010-08-24T18:43:39Z

Sag47: /* invaluable windows tool */ new section

Connect to a wireless local area network

2010-08-24T15:11:19Z

Sag47: /* Use WPA/WPA2 Enterprise */

This covers how to get '''wireless''', or '''Wi-Fi''' [[networks]] to work under Linux, and the various applications that go along with them.

= Start =
You should start by means of your [[distribution]] - most probably, it works out of the box. Make sure you enabled WLAN on your laptop (there is mostly a button for it). Put it next to your WLAN router. Install your WLAN card as a network card, it will be called eth1,wlan0 or so. Use <code>[[iwconfig]]</code> to find out how it is called. You should be able to scan for wireless networks then, e.g. by
$ iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 00:0F:C9:01:F5:F4
ESSID:"foo"
Mode:Managed
Channel:10
Encryption key:off
Bit Rates:0 kb/s

$

If you get a <code>Command not found</code> error, install the [[Wireless tools]] and try again. 
If you do not get a list like the above, see the next section [[#Wireless_Configuration|Wireless configuration]]. 
If it works, you can continue with the section [[#Connect_to_an_Accesspoint|Connect to an Accesspoint]].

= Wireless Configuration =
The following provides the general steps required to get wireless networking enabled on your Linux machine.

== Gaining root access ==

[[open a console]] and type ''su'' to log into root (you must type your root password. If you're on an Ubuntu-like where the root user is disabled then don't bother typing ''su'' but instead add ''sudo'' at the beginning of each command. If you're on Ubuntu and, like me, hate using the sudo command so much then run ''sudo bash'' which logs you into root just like su.

== Find out your wifi card's chipset ==

In order to get your card working you will have to determine its chipset.
There is one, generic, way for [http://en.wikipedia.org/wiki/Conventional_PCI PCI] and [http://en.wikipedia.org/wiki/PC_Card PCMCIA] cards, and one for [[USB]] cards:

*'''The generic way'''
**Run "[[hwinfo]] --wlan"
:If this command does not succeed, this can mean that you have an old [[kernel]] that does not recognize your card as a WLAN card. In this case, you cannot use it. Anyway, to find out its type use <code>hwinfo --[http://en.wikipedia.org/wiki/Conventional_PCI pci]</code> or <code>hwinfo --pcmcia</code>.

*'''Methods for [[USB]] cards'''
**Run <code>hwinfo --usb</code>.
:This will give you information about the chipset and tell you a ''Driver activation command'' (like "modprobe rt73usb").

Hopefully you now have a chipset name but...

== Which driver to load and how? ==

To find out which driver you have to load, use
hwinfo --wlan|grep -i driver
See below for additional relevant information on given chipsets or drivers.

'''Open Source'''
* [[WiFi Link 5100]]
* [[Intel PRO/Wireless 3945ABG]]
* [[Intel_Pro_Wireless]] 2100/2200/2915 -- Note that this requires http://sourceforge.net/projects/ieee80211
** ipw2200 on Suse 10.0, see [[Suse100ipw2200]]
* Prism 2/2.5/3: [[Prism_2_Drivers]]
* Ralink RT2400/2500, RT61, RT73: [[Ralink_Wireless_Drivers]]
* Atheros AR5210/5211/5212: [[MADWIFI]]
* Prism GT/Duette/Indigo: [[Prism54]]
* [[Broadcom 4318 Airforce one 54g card]]
* Texas Instruments ACX100/111: [http://acx100.sourceforge.net/ acx100]
* Atmel: [[AT76C5XXx]]
* [[Belkin_F5D6020_ver.2]]
* [[Net_Gear_WG121_on_Mandrake_10.0_Linux]]
* Linksys [[WMP54G Wireless how-to for Ubuntu 8.10]] Intrepid Ibex
* Almost every other chipset: [[NDIS_Wrapper]]
'''Proprietary'''
* [[Linuxant Driverloader]]

Note that [[building]] a [[kernel module]] requires the kernel sources.
Download your driver sources in .tar.gz format and [[compile from source]].

= Connect to an Accesspoint =

This chapter covers how to connect to an unencrypted or WEP encrypted accesspoint. [[wpa|For WPA encryption, have a look here]]. The example interface will be called wlan0.

To set up the interface, start by:

$ ifconfig wlan0 up

If you want, you could scan for an accesspoint first:

$ iwlist wlan0 scanning

You will then see the available accesspoints, their ESSID's, the frequency, etc.
To associate with an accesspoint (for example "test"), run:
$ iwconfig wlan0 essid test
Most drivers will automatically find the right channel in a minute.
You should now be able to see something like this when you run iwconfig:
$ iwconfig
lo no wireless extensions

wlan0 IEEE 802.11b ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key: off
Power Management:off
Link Quality=0/0 Signal level=0/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This means that everything has been installed properly.

== Using WEP encryption ==

If the accesspoint uses WEP, you set the encryption like so:
$ iwconfig wlan0 key s:"the_ascii_key"
Or you can use a hexadecimal key:
$ iwconfig wlan0 key 00000000000
The bits of encryption is determined by the key length. Note that this command, along with the key, can be seen in "ps aux".

# ifconfig ath0 down
# iwconfig ath0 essid disaster-master enc 1234abcdef mode Managed channel auto
# ifconfig ath0 up
# dhclient ath0

If you don't like typing a large command sequence to reconnect your login each time then here is a helpful script which can speed up the process.
#!/bin/sh
#this is a comment
#all commands must be run as root (script must be run as root or as startup script)

#Router WEP settings
iface=ath0
ssid=disaster-master
wephexkey=1234abcdef
chan=auto

#setting up and applying wireless config, no need to edit beyond this point
ifconfig $iface down
iwconfig $iface essid $ssid enc $wephexkey mode Managed channel $chan
ifconfig $iface up
dhclient $iface

== Use WPA/WPA2 Personal ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-PSK or WPA2-PSK.

My network SSID is called disaster-master and it's currently running WPA2-PSK encryption on it. My WPA2 passphrase is "hindrance".

First create two text files and save them as wireless-wpa.sh and wireless-wpa.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa.sh'''
#!/bin/sh
iface=ath0

#shut down interface
ifconfig $iface down

#set ad-hoc/management of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#stop any persistent wireless wpa2 sessions
killall wpa_supplicant

#apply WPA/WPA2 personal settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa.conf'''
# disaster-master network using WPA2-PSK

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="disaster-master"
scan_ssid=1
key_mgmt=WPA-PSK
psk="hindrance"
}
Don't forget to edit wireless-wpa.sh and set iface equal to your wireless device and edit wireless-wpa.conf with your WPA settings. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''). Run the following command sequence:
# chmod 755 wireless-wpa.sh
# chmod 644 wireless-wpa.conf
# ./wireless-wpa.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa.sh every time you restart your computer.

You can read up on the wpa_supplicant setup by viewing it's man pages. Just type:
man wpa_supplicant
man wpa_supplicant.conf

== Use WPA/WPA2 Enterprise ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-Enterprise or WPA2-Enterprise.

My enterprise network SSID is called dragonfly3 and it has a radius login server at radius.irt.drexel.edu (which is automatically detected and not needed to be set up). The Enterprise network is currently running WPA2-Enterprise encryption with IEEE 802.1X login using EAP-TTLS/MSCHAPv2. My login (not real) at radius.irt.drexel.edu is "abc123" and my password is "hindrance".

First create two text files and save them as wireless-wpa-enterprise.sh and wireless-wpa-enterprise.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa-enterprise.sh'''
#!/bin/sh
iface=ath0

#stop any persistent wireless wpa2 authentication sessions
killall wpa_supplicant

#shut down wireless interface
ifconfig $iface down

#set working mode of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#apply dragonfly3 settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa-enterprise.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa-enterprise.conf'''
# Drexel dragonfly3 IEEE 802.1X login using EAP-TTLS/MSCHAPv2

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dragonfly3"
scan_ssid=0
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS
phase2="auth=MSCHAPV2"
identity="abc123"
password="hindrance"
}
Don't forget to edit wireless-wpa-enterprise.sh and set iface equal to your wireless device and edit wireless-wpa-enterprise.conf with your network SSID and enterprise login information. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''. Run the following command sequence:
# chmod 755 wireless-wpa-enterprise.sh
# chmod 644 wireless-wpa-enterprise.conf
# ./wireless-wpa-enterprise.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa-enterprise.sh every time you restart your computer.

You can read up on the wpa_supplicant setup by viewing it's man pages. Just type:
man wpa_supplicant
man wpa_supplicant.conf

== Getting an IP address ==

If you have associated properly, you should see the accesspoint's mac address in from iwconfig instead of 00:00:00:00:00:00. If the network you have connected to uses dhcp, it is time to obtain an ip address:
$ dhclient wlan0
Or:
$ dhcpcd wlan0
You should see "DHCPOFFER" or similar in a minute if all went well. If it sits there for a while with no DHCPOFFER, then something is wrong. Perhaps the encryption key was incorrect.

However, if you would connect to a AP that doesn't have a dhcp server, you can do the following:

First scan for the AP so you can see the ESSID and the mac address. Do the following
$ iwconfig wlan0 essid "MyAP" (if that's the ESSID)
$ iwconfig wlan0 ap 00:40:CA:45:10:9C (if that's the mac)
$ ifconfig wlan0 192.168.0.20 up
$ route add -net default gw 192.168.0.1
Provided that the AP has the IP 192.168.0.1.

== Autostarting network configuration ==
I found a really good post which tells you how to do this [http://www.howtoforge.com/forums/showthread.php?p=22384#post22384 located here] and create the necessary system startup links. Depending on your distribution you can do it with chkconfig (RedHat, Fedora, CentOS, Mandriva, SuSE) or update-rc.d (Debian, Ubuntu). I'm going to proceed explaining how to manually set up a startup script rather than using the automated method like update-rc.d. This is per the documentation from the [http://www.debian.org/doc/debian-policy/ch-opersys.html Debian Policy Manual Section 9.3].

The directory for startup scripts is located in ''/etc/rcS.d''. Do a quick listing and see what is in your bootup script directory using ''ls /etc/rcS.d'':
: '''ls /etc/rcS.d'''
README S35mountall.sh
S01mountkernfs.sh S36mountall-bootclean.sh
S01readahead S37apparmor
S02hostname.sh S37mountoverflowtmp
S06keyboard-setup S37udev-finish
S07linux-restricted-modules-common S39readahead-desktop
S08hwclockfirst.sh S39ufw
S08loopback S40networking
S10udev S45mountnfs.sh
S11hwclock.sh S46mountnfs-bootclean.sh
S11mountdevsubfs.sh S49console-setup
S13pcmciautils S55bootmisc.sh
S15module-init-tools S55dns-clean
S17procps S55pppd-dns
S20checkroot.sh S55urandom
S22mtab.sh S70screen-cleanup
S25brltty S70x11-common
S30checkfs.sh S90console-screen.kbd.sh
Here is what my readme readme says:
: '''cat /etc/rcS.d/README'''
The scripts in this directory whose names begin with an 'S' are executed
once when booting the system, even when booting directly into single user
mode.

The scripts are all symbolic links whose targets are located in
/etc/init.d/ .

To disable a script in this directory, rename it so that it begins with
a 'K'.

For more information see /etc/init.d/README.

The following sequence points are defined at this time:

* After the S40 scripts have executed, all local file systems are mounted
and networking is available. All device drivers have been initialized.

* After the S60 scripts have executed, the system clock has been set, NFS
filesystems have been mounted (unless the system depends on the automounter,
which is started later) and the filesystems have been cleaned.
As a quick side note, if you are using WPA then you need to edit your ''wireless-wpa.sh'' script and change ''./wireless-wpa.conf'' to ''/etc/init.d/wireless-wpa.conf''. Here's the newly formatted command:
wpa_supplicant -B -Dwext -i $iface -c /etc/init.d/wireless-wpa.conf -dd
And also please note from the README that ''"After the S40 scripts have executed, all local file systems are mounted and networking is available. All device drivers have been initialized."'' As you can see from my listing that I have no S41 script so I'm going to make that my wireless networking startup script and call it ''S41wlan_net_connect'' (you can call it ''S41'' whatever you want if you don't like it). Browse to the directory where you have your wireless-wpa.sh, then switch to root user and run the following command sequence:
cp ./wireless-wpa.sh /etc/init.d/wireless-wpa.sh
cp ./wireless-wpa.conf /etc/init.d/wireless-wpa.conf
chmod 755 /etc/init.d/wireless-wpa.sh
chmod 644 /etc/init.d/wireless-wpa.conf
ln -s /etc/init.d/wireless-wpa.sh /etc/rcS.d/S41wlan_net_connect
We just finished creating the symbolic link (ln -s) so now test it by restarting. It should be set up as a startup script now.

= Create an access point =

It is fairly simple to setup an AP in linux. This is how I did.

I purchased a D-Link DWL-G520 pci card. You need a card that supports Master mode. Check [http://linux-wless.passys.nl this] (''linux-wless.passys.nl'') site for compatibility with Linux, I think ndiswrapper doesn't have support for Master mode, not sure though.

'''Creating the AP'''

Then if your interface is ath0:

$ iwconfig ath0 mode Master
$ iwconfig ath0 essid "LinuxAP"
$ ifconfig ath0 192.168.1.1 up

I chose an IP that wasn't in my wired LANs subnet.
Now you should be able to see the AP if you scan for APs.

'''Configure statically your client's card'''

Then on the client side (if your interface is ath0) you do:

$ iwconfig ath0 mode Managed
$ iwconfig essid "LinuxAP"
$ iwconfig ap 00:11:22:AA:22:11
$ ifconfig ath0 192.168.1.10 netmask 255.255.255.0 up
$ route add -net default gw 192.168.1.1

It's not always necessary to specify the mac address for the ap, but sometimes it's a good thing. As you can see I chose an ip that was in the same subnet as the ap, it's important.

== DHCP server, firewall and stuff ==

Now, that was the static ip way and you probably want a dhcp-server and some firewall-rules for the ap. Guess what... here they come!

'''iptables'''

I have some rules with iptables in a script:

#!/bin/sh
IPTABLES='/sbin/iptables'
EXTIF='eth0'
INTIF='eth1'
WLAN='ath0'
WAN='85.235.31.133'

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

$IPTABLES -F
$IPTABLES -X

$IPTABLES -X -t nat
$IPTABLES -F -t nat

$IPTABLES -X -t filter
$IPTABLES -F -t filter

# enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

# forward LAN traffic from $INTIF1 to Internet interface $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

# allow ping
$IPTABLES -A INPUT -p icmp -i $EXTIF -j ACCEPT

# Allowing access to the FTP server"
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 21 -j ACCEPT

# Allowing access to the ssh server on port 2200 (I've changed it)
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 2200 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP

'''dnsmasq'''

And my dnsmasq.config looks like this:

resolv-file=/etc/resolv.conf
no-poll
domain-needed
bogus-priv
strict-order

interface=ath0
dhcp-range=192.168.1.10,192.168.1.50,12h

interface=eth1
dhcp-range=192.168.0.10,192.168.0.50,12h

# alice and bob are declared in /etc/hosts
dhcp-host=00:0A:E4:52:6B:12,alice
dhcp-host=00:40:CA:45:10:9C,bob

dhcp-authoritative

And that's it! Just run the script, start dnsmasq and connect to the ap described in the top of this wiki.

'''stuff'''

By the way, if you want to ping some host in the 192.168.0.0 subnet make sure that you don't have another interface that's not alive with an ip in that subnet. So if you have an ordinary wired card eth0 with an ip in the 192.168.0.0 subnet (but no cable in maybe) make sure that you bring that interface down.
$ ifconfig eth0 down
Now you can ping hosts in that subnet with your wifi card.

= External links =
== Howtos,Guides ==
*[http://www-106.ibm.com/developerworks/library/wi-enable.html?ca=dgr-lnxw82Linux4Wireless A nice overview] (''www-106.ibm.com'')
*[http://www.rustyspigot.com/groovyweb/?page_name=Linux%20Wireless&category=linux Wireless Tutorial] (''www.rustyspigot.com'')
*[http://www.ubuntuforums.org/showthread.php?t=202834 Wireless Security - WPA1 WPA2 LEAP AES, etc.] (''www.ubuntuforums.org'')

== Chipset list ==
*[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz list of all possible wlan chipsets] (''wiki.uni-konstanz.de'')
*[http://linux-wless.passys.nl Supported cards by manufacturer, chipset and interface (PCI, USB, PCMCIA)] (''linux-wless.passys.nl'')

== Specific cards ==
*[http://www.wmconnolley.org.uk/linux-wireless.html D-LINK DWL-650 (and/or DRC-650) under RH 8.0, kernel 2.4.18] (''www.wmconnolley.org.uk'')
*[http://www.netdigix.com/downloads/debian-linksys-wireless-howto.html Linksys WMP54G - 802.11G - kernel 2.4 - debian 3.0] (''www.netdigix.com'')
*[http://kennethjor.blogspot.com/2006/10/linksys-wusb54gc-ralink-rt73-and.html Linksys WUSB54GC - kernel 2.6.15 - Ubuntu 6.06] (''kennethjor.blogspot.com'')
*[http://wwwu.uni-klu.ac.at/agebhard/WUSB54GC/ Kernel module package for Ralink RT73 based USB WLAN adapters, such as Linksys WUSB54GC - Kernel 2.6.15 - Ubuntu 6.06] (''www.uni-klu.ac.at'')

[[Category:Networking]]
[[Category:Example]]
[[Category:Guides]]

Connect to a wireless local area network

2010-08-24T15:11:01Z

Sag47: /* Use WPA/WPA2 Personal */

This covers how to get '''wireless''', or '''Wi-Fi''' [[networks]] to work under Linux, and the various applications that go along with them.

= Start =
You should start by means of your [[distribution]] - most probably, it works out of the box. Make sure you enabled WLAN on your laptop (there is mostly a button for it). Put it next to your WLAN router. Install your WLAN card as a network card, it will be called eth1,wlan0 or so. Use <code>[[iwconfig]]</code> to find out how it is called. You should be able to scan for wireless networks then, e.g. by
$ iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 00:0F:C9:01:F5:F4
ESSID:"foo"
Mode:Managed
Channel:10
Encryption key:off
Bit Rates:0 kb/s

$

If you get a <code>Command not found</code> error, install the [[Wireless tools]] and try again. 
If you do not get a list like the above, see the next section [[#Wireless_Configuration|Wireless configuration]]. 
If it works, you can continue with the section [[#Connect_to_an_Accesspoint|Connect to an Accesspoint]].

= Wireless Configuration =
The following provides the general steps required to get wireless networking enabled on your Linux machine.

== Gaining root access ==

[[open a console]] and type ''su'' to log into root (you must type your root password. If you're on an Ubuntu-like where the root user is disabled then don't bother typing ''su'' but instead add ''sudo'' at the beginning of each command. If you're on Ubuntu and, like me, hate using the sudo command so much then run ''sudo bash'' which logs you into root just like su.

== Find out your wifi card's chipset ==

In order to get your card working you will have to determine its chipset.
There is one, generic, way for [http://en.wikipedia.org/wiki/Conventional_PCI PCI] and [http://en.wikipedia.org/wiki/PC_Card PCMCIA] cards, and one for [[USB]] cards:

*'''The generic way'''
**Run "[[hwinfo]] --wlan"
:If this command does not succeed, this can mean that you have an old [[kernel]] that does not recognize your card as a WLAN card. In this case, you cannot use it. Anyway, to find out its type use <code>hwinfo --[http://en.wikipedia.org/wiki/Conventional_PCI pci]</code> or <code>hwinfo --pcmcia</code>.

*'''Methods for [[USB]] cards'''
**Run <code>hwinfo --usb</code>.
:This will give you information about the chipset and tell you a ''Driver activation command'' (like "modprobe rt73usb").

Hopefully you now have a chipset name but...

== Which driver to load and how? ==

To find out which driver you have to load, use
hwinfo --wlan|grep -i driver
See below for additional relevant information on given chipsets or drivers.

'''Open Source'''
* [[WiFi Link 5100]]
* [[Intel PRO/Wireless 3945ABG]]
* [[Intel_Pro_Wireless]] 2100/2200/2915 -- Note that this requires http://sourceforge.net/projects/ieee80211
** ipw2200 on Suse 10.0, see [[Suse100ipw2200]]
* Prism 2/2.5/3: [[Prism_2_Drivers]]
* Ralink RT2400/2500, RT61, RT73: [[Ralink_Wireless_Drivers]]
* Atheros AR5210/5211/5212: [[MADWIFI]]
* Prism GT/Duette/Indigo: [[Prism54]]
* [[Broadcom 4318 Airforce one 54g card]]
* Texas Instruments ACX100/111: [http://acx100.sourceforge.net/ acx100]
* Atmel: [[AT76C5XXx]]
* [[Belkin_F5D6020_ver.2]]
* [[Net_Gear_WG121_on_Mandrake_10.0_Linux]]
* Linksys [[WMP54G Wireless how-to for Ubuntu 8.10]] Intrepid Ibex
* Almost every other chipset: [[NDIS_Wrapper]]
'''Proprietary'''
* [[Linuxant Driverloader]]

Note that [[building]] a [[kernel module]] requires the kernel sources.
Download your driver sources in .tar.gz format and [[compile from source]].

= Connect to an Accesspoint =

This chapter covers how to connect to an unencrypted or WEP encrypted accesspoint. [[wpa|For WPA encryption, have a look here]]. The example interface will be called wlan0.

To set up the interface, start by:

$ ifconfig wlan0 up

If you want, you could scan for an accesspoint first:

$ iwlist wlan0 scanning

You will then see the available accesspoints, their ESSID's, the frequency, etc.
To associate with an accesspoint (for example "test"), run:
$ iwconfig wlan0 essid test
Most drivers will automatically find the right channel in a minute.
You should now be able to see something like this when you run iwconfig:
$ iwconfig
lo no wireless extensions

wlan0 IEEE 802.11b ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key: off
Power Management:off
Link Quality=0/0 Signal level=0/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This means that everything has been installed properly.

== Using WEP encryption ==

If the accesspoint uses WEP, you set the encryption like so:
$ iwconfig wlan0 key s:"the_ascii_key"
Or you can use a hexadecimal key:
$ iwconfig wlan0 key 00000000000
The bits of encryption is determined by the key length. Note that this command, along with the key, can be seen in "ps aux".

# ifconfig ath0 down
# iwconfig ath0 essid disaster-master enc 1234abcdef mode Managed channel auto
# ifconfig ath0 up
# dhclient ath0

If you don't like typing a large command sequence to reconnect your login each time then here is a helpful script which can speed up the process.
#!/bin/sh
#this is a comment
#all commands must be run as root (script must be run as root or as startup script)

#Router WEP settings
iface=ath0
ssid=disaster-master
wephexkey=1234abcdef
chan=auto

#setting up and applying wireless config, no need to edit beyond this point
ifconfig $iface down
iwconfig $iface essid $ssid enc $wephexkey mode Managed channel $chan
ifconfig $iface up
dhclient $iface

== Use WPA/WPA2 Personal ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-PSK or WPA2-PSK.

My network SSID is called disaster-master and it's currently running WPA2-PSK encryption on it. My WPA2 passphrase is "hindrance".

First create two text files and save them as wireless-wpa.sh and wireless-wpa.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa.sh'''
#!/bin/sh
iface=ath0

#shut down interface
ifconfig $iface down

#set ad-hoc/management of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#stop any persistent wireless wpa2 sessions
killall wpa_supplicant

#apply WPA/WPA2 personal settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa.conf'''
# disaster-master network using WPA2-PSK

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="disaster-master"
scan_ssid=1
key_mgmt=WPA-PSK
psk="hindrance"
}
Don't forget to edit wireless-wpa.sh and set iface equal to your wireless device and edit wireless-wpa.conf with your WPA settings. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''). Run the following command sequence:
# chmod 755 wireless-wpa.sh
# chmod 644 wireless-wpa.conf
# ./wireless-wpa.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa.sh every time you restart your computer.

You can read up on the wpa_supplicant setup by viewing it's man pages. Just type:
man wpa_supplicant
man wpa_supplicant.conf

== Use WPA/WPA2 Enterprise ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-Enterprise or WPA2-Enterprise.

My enterprise network SSID is called dragonfly3 and it has a radius login server at radius.irt.drexel.edu (which is automatically detected and not needed to be set up). The Enterprise network is currently running WPA2-Enterprise encryption with IEEE 802.1X login using EAP-TTLS/MSCHAPv2. My login (not real) at radius.irt.drexel.edu is "abc123" and my password is "hindrance".

First create two text files and save them as wireless-wpa-enterprise.sh and wireless-wpa-enterprise.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa-enterprise.sh'''
#!/bin/sh
iface=ath0

#stop any persistent wireless wpa2 authentication sessions
killall wpa_supplicant

#shut down wireless interface
ifconfig $iface down

#set working mode of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#apply dragonfly3 settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa-enterprise.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa-enterprise.conf'''
# Drexel dragonfly3 IEEE 802.1X login using EAP-TTLS/MSCHAPv2

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dragonfly3"
scan_ssid=0
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS
phase2="auth=MSCHAPV2"
identity="abc123"
password="hindrance"
}
Don't forget to edit wireless-wpa-enterprise.sh and set iface equal to your wireless device and edit wireless-wpa-enterprise.conf with your network SSID and enterprise login information. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''. Run the following command sequence:
# chmod 755 wireless-wpa-enterprise.sh
# chmod 644 wireless-wpa-enterprise.conf
# ./wireless-wpa-enterprise.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa-enterprise.sh every time you restart your computer.

== Getting an IP address ==

If you have associated properly, you should see the accesspoint's mac address in from iwconfig instead of 00:00:00:00:00:00. If the network you have connected to uses dhcp, it is time to obtain an ip address:
$ dhclient wlan0
Or:
$ dhcpcd wlan0
You should see "DHCPOFFER" or similar in a minute if all went well. If it sits there for a while with no DHCPOFFER, then something is wrong. Perhaps the encryption key was incorrect.

However, if you would connect to a AP that doesn't have a dhcp server, you can do the following:

First scan for the AP so you can see the ESSID and the mac address. Do the following
$ iwconfig wlan0 essid "MyAP" (if that's the ESSID)
$ iwconfig wlan0 ap 00:40:CA:45:10:9C (if that's the mac)
$ ifconfig wlan0 192.168.0.20 up
$ route add -net default gw 192.168.0.1
Provided that the AP has the IP 192.168.0.1.

== Autostarting network configuration ==
I found a really good post which tells you how to do this [http://www.howtoforge.com/forums/showthread.php?p=22384#post22384 located here] and create the necessary system startup links. Depending on your distribution you can do it with chkconfig (RedHat, Fedora, CentOS, Mandriva, SuSE) or update-rc.d (Debian, Ubuntu). I'm going to proceed explaining how to manually set up a startup script rather than using the automated method like update-rc.d. This is per the documentation from the [http://www.debian.org/doc/debian-policy/ch-opersys.html Debian Policy Manual Section 9.3].

The directory for startup scripts is located in ''/etc/rcS.d''. Do a quick listing and see what is in your bootup script directory using ''ls /etc/rcS.d'':
: '''ls /etc/rcS.d'''
README S35mountall.sh
S01mountkernfs.sh S36mountall-bootclean.sh
S01readahead S37apparmor
S02hostname.sh S37mountoverflowtmp
S06keyboard-setup S37udev-finish
S07linux-restricted-modules-common S39readahead-desktop
S08hwclockfirst.sh S39ufw
S08loopback S40networking
S10udev S45mountnfs.sh
S11hwclock.sh S46mountnfs-bootclean.sh
S11mountdevsubfs.sh S49console-setup
S13pcmciautils S55bootmisc.sh
S15module-init-tools S55dns-clean
S17procps S55pppd-dns
S20checkroot.sh S55urandom
S22mtab.sh S70screen-cleanup
S25brltty S70x11-common
S30checkfs.sh S90console-screen.kbd.sh
Here is what my readme readme says:
: '''cat /etc/rcS.d/README'''
The scripts in this directory whose names begin with an 'S' are executed
once when booting the system, even when booting directly into single user
mode.

The scripts are all symbolic links whose targets are located in
/etc/init.d/ .

To disable a script in this directory, rename it so that it begins with
a 'K'.

For more information see /etc/init.d/README.

The following sequence points are defined at this time:

* After the S40 scripts have executed, all local file systems are mounted
and networking is available. All device drivers have been initialized.

* After the S60 scripts have executed, the system clock has been set, NFS
filesystems have been mounted (unless the system depends on the automounter,
which is started later) and the filesystems have been cleaned.
As a quick side note, if you are using WPA then you need to edit your ''wireless-wpa.sh'' script and change ''./wireless-wpa.conf'' to ''/etc/init.d/wireless-wpa.conf''. Here's the newly formatted command:
wpa_supplicant -B -Dwext -i $iface -c /etc/init.d/wireless-wpa.conf -dd
And also please note from the README that ''"After the S40 scripts have executed, all local file systems are mounted and networking is available. All device drivers have been initialized."'' As you can see from my listing that I have no S41 script so I'm going to make that my wireless networking startup script and call it ''S41wlan_net_connect'' (you can call it ''S41'' whatever you want if you don't like it). Browse to the directory where you have your wireless-wpa.sh, then switch to root user and run the following command sequence:
cp ./wireless-wpa.sh /etc/init.d/wireless-wpa.sh
cp ./wireless-wpa.conf /etc/init.d/wireless-wpa.conf
chmod 755 /etc/init.d/wireless-wpa.sh
chmod 644 /etc/init.d/wireless-wpa.conf
ln -s /etc/init.d/wireless-wpa.sh /etc/rcS.d/S41wlan_net_connect
We just finished creating the symbolic link (ln -s) so now test it by restarting. It should be set up as a startup script now.

= Create an access point =

It is fairly simple to setup an AP in linux. This is how I did.

I purchased a D-Link DWL-G520 pci card. You need a card that supports Master mode. Check [http://linux-wless.passys.nl this] (''linux-wless.passys.nl'') site for compatibility with Linux, I think ndiswrapper doesn't have support for Master mode, not sure though.

'''Creating the AP'''

Then if your interface is ath0:

$ iwconfig ath0 mode Master
$ iwconfig ath0 essid "LinuxAP"
$ ifconfig ath0 192.168.1.1 up

I chose an IP that wasn't in my wired LANs subnet.
Now you should be able to see the AP if you scan for APs.

'''Configure statically your client's card'''

Then on the client side (if your interface is ath0) you do:

$ iwconfig ath0 mode Managed
$ iwconfig essid "LinuxAP"
$ iwconfig ap 00:11:22:AA:22:11
$ ifconfig ath0 192.168.1.10 netmask 255.255.255.0 up
$ route add -net default gw 192.168.1.1

It's not always necessary to specify the mac address for the ap, but sometimes it's a good thing. As you can see I chose an ip that was in the same subnet as the ap, it's important.

== DHCP server, firewall and stuff ==

Now, that was the static ip way and you probably want a dhcp-server and some firewall-rules for the ap. Guess what... here they come!

'''iptables'''

I have some rules with iptables in a script:

#!/bin/sh
IPTABLES='/sbin/iptables'
EXTIF='eth0'
INTIF='eth1'
WLAN='ath0'
WAN='85.235.31.133'

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

$IPTABLES -F
$IPTABLES -X

$IPTABLES -X -t nat
$IPTABLES -F -t nat

$IPTABLES -X -t filter
$IPTABLES -F -t filter

# enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

# forward LAN traffic from $INTIF1 to Internet interface $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

# allow ping
$IPTABLES -A INPUT -p icmp -i $EXTIF -j ACCEPT

# Allowing access to the FTP server"
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 21 -j ACCEPT

# Allowing access to the ssh server on port 2200 (I've changed it)
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 2200 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP

'''dnsmasq'''

And my dnsmasq.config looks like this:

resolv-file=/etc/resolv.conf
no-poll
domain-needed
bogus-priv
strict-order

interface=ath0
dhcp-range=192.168.1.10,192.168.1.50,12h

interface=eth1
dhcp-range=192.168.0.10,192.168.0.50,12h

# alice and bob are declared in /etc/hosts
dhcp-host=00:0A:E4:52:6B:12,alice
dhcp-host=00:40:CA:45:10:9C,bob

dhcp-authoritative

And that's it! Just run the script, start dnsmasq and connect to the ap described in the top of this wiki.

'''stuff'''

By the way, if you want to ping some host in the 192.168.0.0 subnet make sure that you don't have another interface that's not alive with an ip in that subnet. So if you have an ordinary wired card eth0 with an ip in the 192.168.0.0 subnet (but no cable in maybe) make sure that you bring that interface down.
$ ifconfig eth0 down
Now you can ping hosts in that subnet with your wifi card.

= External links =
== Howtos,Guides ==
*[http://www-106.ibm.com/developerworks/library/wi-enable.html?ca=dgr-lnxw82Linux4Wireless A nice overview] (''www-106.ibm.com'')
*[http://www.rustyspigot.com/groovyweb/?page_name=Linux%20Wireless&category=linux Wireless Tutorial] (''www.rustyspigot.com'')
*[http://www.ubuntuforums.org/showthread.php?t=202834 Wireless Security - WPA1 WPA2 LEAP AES, etc.] (''www.ubuntuforums.org'')

== Chipset list ==
*[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz list of all possible wlan chipsets] (''wiki.uni-konstanz.de'')
*[http://linux-wless.passys.nl Supported cards by manufacturer, chipset and interface (PCI, USB, PCMCIA)] (''linux-wless.passys.nl'')

== Specific cards ==
*[http://www.wmconnolley.org.uk/linux-wireless.html D-LINK DWL-650 (and/or DRC-650) under RH 8.0, kernel 2.4.18] (''www.wmconnolley.org.uk'')
*[http://www.netdigix.com/downloads/debian-linksys-wireless-howto.html Linksys WMP54G - 802.11G - kernel 2.4 - debian 3.0] (''www.netdigix.com'')
*[http://kennethjor.blogspot.com/2006/10/linksys-wusb54gc-ralink-rt73-and.html Linksys WUSB54GC - kernel 2.6.15 - Ubuntu 6.06] (''kennethjor.blogspot.com'')
*[http://wwwu.uni-klu.ac.at/agebhard/WUSB54GC/ Kernel module package for Ralink RT73 based USB WLAN adapters, such as Linksys WUSB54GC - Kernel 2.6.15 - Ubuntu 6.06] (''www.uni-klu.ac.at'')

[[Category:Networking]]
[[Category:Example]]
[[Category:Guides]]

Connect to a wireless local area network

2010-08-24T15:06:33Z

Sag47: /* Gaining root access */

This covers how to get '''wireless''', or '''Wi-Fi''' [[networks]] to work under Linux, and the various applications that go along with them.

= Start =
You should start by means of your [[distribution]] - most probably, it works out of the box. Make sure you enabled WLAN on your laptop (there is mostly a button for it). Put it next to your WLAN router. Install your WLAN card as a network card, it will be called eth1,wlan0 or so. Use <code>[[iwconfig]]</code> to find out how it is called. You should be able to scan for wireless networks then, e.g. by
$ iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 00:0F:C9:01:F5:F4
ESSID:"foo"
Mode:Managed
Channel:10
Encryption key:off
Bit Rates:0 kb/s

$

If you get a <code>Command not found</code> error, install the [[Wireless tools]] and try again. 
If you do not get a list like the above, see the next section [[#Wireless_Configuration|Wireless configuration]]. 
If it works, you can continue with the section [[#Connect_to_an_Accesspoint|Connect to an Accesspoint]].

= Wireless Configuration =
The following provides the general steps required to get wireless networking enabled on your Linux machine.

== Gaining root access ==

Type ''su'' in your Terminal to log into root (you must type your root password. If you're on an Ubuntu-like where the root user is disabled then don't bother typing ''su'' but instead add ''sudo'' at the beginning of each command. If you're on Ubuntu and, like me, hate using the sudo command so much then run ''sudo bash'' which logs you into root just like su.

In the command examples do not type '$' or '#' because $ signifies that the command is run as a normal user and # means the command is being run as the root user.

== Find out your wifi card's chipset ==

In order to get your card working you will have to determine its chipset.
There is one, generic, way for [http://en.wikipedia.org/wiki/Conventional_PCI PCI] and [http://en.wikipedia.org/wiki/PC_Card PCMCIA] cards, and one for [[USB]] cards:

*'''The generic way'''
**Run "[[hwinfo]] --wlan"
:If this command does not succeed, this can mean that you have an old [[kernel]] that does not recognize your card as a WLAN card. In this case, you cannot use it. Anyway, to find out its type use <code>hwinfo --[http://en.wikipedia.org/wiki/Conventional_PCI pci]</code> or <code>hwinfo --pcmcia</code>.

*'''Methods for [[USB]] cards'''
**Run <code>hwinfo --usb</code>.
:This will give you information about the chipset and tell you a ''Driver activation command'' (like "modprobe rt73usb").

Hopefully you now have a chipset name but...

== Which driver to load and how? ==

To find out which driver you have to load, use
hwinfo --wlan|grep -i driver
See below for additional relevant information on given chipsets or drivers.

'''Open Source'''
* [[WiFi Link 5100]]
* [[Intel PRO/Wireless 3945ABG]]
* [[Intel_Pro_Wireless]] 2100/2200/2915 -- Note that this requires http://sourceforge.net/projects/ieee80211
** ipw2200 on Suse 10.0, see [[Suse100ipw2200]]
* Prism 2/2.5/3: [[Prism_2_Drivers]]
* Ralink RT2400/2500, RT61, RT73: [[Ralink_Wireless_Drivers]]
* Atheros AR5210/5211/5212: [[MADWIFI]]
* Prism GT/Duette/Indigo: [[Prism54]]
* [[Broadcom 4318 Airforce one 54g card]]
* Texas Instruments ACX100/111: [http://acx100.sourceforge.net/ acx100]
* Atmel: [[AT76C5XXx]]
* [[Belkin_F5D6020_ver.2]]
* [[Net_Gear_WG121_on_Mandrake_10.0_Linux]]
* Linksys [[WMP54G Wireless how-to for Ubuntu 8.10]] Intrepid Ibex
* Almost every other chipset: [[NDIS_Wrapper]]
'''Proprietary'''
* [[Linuxant Driverloader]]

Note that [[building]] a [[kernel module]] requires the kernel sources.
Download your driver sources in .tar.gz format and [[compile from source]].

= Connect to an Accesspoint =

This chapter covers how to connect to an unencrypted or WEP encrypted accesspoint. [[wpa|For WPA encryption, have a look here]]. The example interface will be called wlan0.

To set up the interface, start by:

$ ifconfig wlan0 up

If you want, you could scan for an accesspoint first:

$ iwlist wlan0 scanning

You will then see the available accesspoints, their ESSID's, the frequency, etc.
To associate with an accesspoint (for example "test"), run:
$ iwconfig wlan0 essid test
Most drivers will automatically find the right channel in a minute.
You should now be able to see something like this when you run iwconfig:
$ iwconfig
lo no wireless extensions

wlan0 IEEE 802.11b ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key: off
Power Management:off
Link Quality=0/0 Signal level=0/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This means that everything has been installed properly.

== Using WEP encryption ==

If the accesspoint uses WEP, you set the encryption like so:
$ iwconfig wlan0 key s:"the_ascii_key"
Or you can use a hexadecimal key:
$ iwconfig wlan0 key 00000000000
The bits of encryption is determined by the key length. Note that this command, along with the key, can be seen in "ps aux".

# ifconfig ath0 down
# iwconfig ath0 essid disaster-master enc 1234abcdef mode Managed channel auto
# ifconfig ath0 up
# dhclient ath0

If you don't like typing a large command sequence to reconnect your login each time then here is a helpful script which can speed up the process.
#!/bin/sh
#this is a comment
#all commands must be run as root (script must be run as root or as startup script)

#Router WEP settings
iface=ath0
ssid=disaster-master
wephexkey=1234abcdef
chan=auto

#setting up and applying wireless config, no need to edit beyond this point
ifconfig $iface down
iwconfig $iface essid $ssid enc $wephexkey mode Managed channel $chan
ifconfig $iface up
dhclient $iface

== Use WPA/WPA2 Personal ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-PSK or WPA2-PSK.

My network SSID is called disaster-master and it's currently running WPA2-PSK encryption on it. My WPA2 passphrase is "hindrance".

First create two text files and save them as wireless-wpa.sh and wireless-wpa.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa.sh'''
#!/bin/sh
iface=ath0

#shut down interface
ifconfig $iface down

#set ad-hoc/management of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#stop any persistent wireless wpa2 sessions
killall wpa_supplicant

#apply WPA/WPA2 personal settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa.conf'''
# disaster-master network using WPA2-PSK

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="disaster-master"
scan_ssid=1
key_mgmt=WPA-PSK
psk="hindrance"
}
Don't forget to edit wireless-wpa.sh and set iface equal to your wireless device and edit wireless-wpa.conf with your WPA settings. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''). Run the following command sequence:
# chmod 755 wireless-wpa.sh
# chmod 644 wireless-wpa.conf
# ./wireless-wpa.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa.sh every time you restart your computer.

== Use WPA/WPA2 Enterprise ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-Enterprise or WPA2-Enterprise.

My enterprise network SSID is called dragonfly3 and it has a radius login server at radius.irt.drexel.edu (which is automatically detected and not needed to be set up). The Enterprise network is currently running WPA2-Enterprise encryption with IEEE 802.1X login using EAP-TTLS/MSCHAPv2. My login (not real) at radius.irt.drexel.edu is "abc123" and my password is "hindrance".

First create two text files and save them as wireless-wpa-enterprise.sh and wireless-wpa-enterprise.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa-enterprise.sh'''
#!/bin/sh
iface=ath0

#stop any persistent wireless wpa2 authentication sessions
killall wpa_supplicant

#shut down wireless interface
ifconfig $iface down

#set working mode of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#apply dragonfly3 settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa-enterprise.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa-enterprise.conf'''
# Drexel dragonfly3 IEEE 802.1X login using EAP-TTLS/MSCHAPv2

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dragonfly3"
scan_ssid=0
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS
phase2="auth=MSCHAPV2"
identity="abc123"
password="hindrance"
}
Don't forget to edit wireless-wpa-enterprise.sh and set iface equal to your wireless device and edit wireless-wpa-enterprise.conf with your network SSID and enterprise login information. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''. Run the following command sequence:
# chmod 755 wireless-wpa-enterprise.sh
# chmod 644 wireless-wpa-enterprise.conf
# ./wireless-wpa-enterprise.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa-enterprise.sh every time you restart your computer.

== Getting an IP address ==

If you have associated properly, you should see the accesspoint's mac address in from iwconfig instead of 00:00:00:00:00:00. If the network you have connected to uses dhcp, it is time to obtain an ip address:
$ dhclient wlan0
Or:
$ dhcpcd wlan0
You should see "DHCPOFFER" or similar in a minute if all went well. If it sits there for a while with no DHCPOFFER, then something is wrong. Perhaps the encryption key was incorrect.

However, if you would connect to a AP that doesn't have a dhcp server, you can do the following:

First scan for the AP so you can see the ESSID and the mac address. Do the following
$ iwconfig wlan0 essid "MyAP" (if that's the ESSID)
$ iwconfig wlan0 ap 00:40:CA:45:10:9C (if that's the mac)
$ ifconfig wlan0 192.168.0.20 up
$ route add -net default gw 192.168.0.1
Provided that the AP has the IP 192.168.0.1.

== Autostarting network configuration ==
I found a really good post which tells you how to do this [http://www.howtoforge.com/forums/showthread.php?p=22384#post22384 located here] and create the necessary system startup links. Depending on your distribution you can do it with chkconfig (RedHat, Fedora, CentOS, Mandriva, SuSE) or update-rc.d (Debian, Ubuntu). I'm going to proceed explaining how to manually set up a startup script rather than using the automated method like update-rc.d. This is per the documentation from the [http://www.debian.org/doc/debian-policy/ch-opersys.html Debian Policy Manual Section 9.3].

The directory for startup scripts is located in ''/etc/rcS.d''. Do a quick listing and see what is in your bootup script directory using ''ls /etc/rcS.d'':
: '''ls /etc/rcS.d'''
README S35mountall.sh
S01mountkernfs.sh S36mountall-bootclean.sh
S01readahead S37apparmor
S02hostname.sh S37mountoverflowtmp
S06keyboard-setup S37udev-finish
S07linux-restricted-modules-common S39readahead-desktop
S08hwclockfirst.sh S39ufw
S08loopback S40networking
S10udev S45mountnfs.sh
S11hwclock.sh S46mountnfs-bootclean.sh
S11mountdevsubfs.sh S49console-setup
S13pcmciautils S55bootmisc.sh
S15module-init-tools S55dns-clean
S17procps S55pppd-dns
S20checkroot.sh S55urandom
S22mtab.sh S70screen-cleanup
S25brltty S70x11-common
S30checkfs.sh S90console-screen.kbd.sh
Here is what my readme readme says:
: '''cat /etc/rcS.d/README'''
The scripts in this directory whose names begin with an 'S' are executed
once when booting the system, even when booting directly into single user
mode.

The scripts are all symbolic links whose targets are located in
/etc/init.d/ .

To disable a script in this directory, rename it so that it begins with
a 'K'.

For more information see /etc/init.d/README.

The following sequence points are defined at this time:

* After the S40 scripts have executed, all local file systems are mounted
and networking is available. All device drivers have been initialized.

* After the S60 scripts have executed, the system clock has been set, NFS
filesystems have been mounted (unless the system depends on the automounter,
which is started later) and the filesystems have been cleaned.
As a quick side note, if you are using WPA then you need to edit your ''wireless-wpa.sh'' script and change ''./wireless-wpa.conf'' to ''/etc/init.d/wireless-wpa.conf''. Here's the newly formatted command:
wpa_supplicant -B -Dwext -i $iface -c /etc/init.d/wireless-wpa.conf -dd
And also please note from the README that ''"After the S40 scripts have executed, all local file systems are mounted and networking is available. All device drivers have been initialized."'' As you can see from my listing that I have no S41 script so I'm going to make that my wireless networking startup script and call it ''S41wlan_net_connect'' (you can call it ''S41'' whatever you want if you don't like it). Browse to the directory where you have your wireless-wpa.sh, then switch to root user and run the following command sequence:
cp ./wireless-wpa.sh /etc/init.d/wireless-wpa.sh
cp ./wireless-wpa.conf /etc/init.d/wireless-wpa.conf
chmod 755 /etc/init.d/wireless-wpa.sh
chmod 644 /etc/init.d/wireless-wpa.conf
ln -s /etc/init.d/wireless-wpa.sh /etc/rcS.d/S41wlan_net_connect
We just finished creating the symbolic link (ln -s) so now test it by restarting. It should be set up as a startup script now.

= Create an access point =

It is fairly simple to setup an AP in linux. This is how I did.

I purchased a D-Link DWL-G520 pci card. You need a card that supports Master mode. Check [http://linux-wless.passys.nl this] (''linux-wless.passys.nl'') site for compatibility with Linux, I think ndiswrapper doesn't have support for Master mode, not sure though.

'''Creating the AP'''

Then if your interface is ath0:

$ iwconfig ath0 mode Master
$ iwconfig ath0 essid "LinuxAP"
$ ifconfig ath0 192.168.1.1 up

I chose an IP that wasn't in my wired LANs subnet.
Now you should be able to see the AP if you scan for APs.

'''Configure statically your client's card'''

Then on the client side (if your interface is ath0) you do:

$ iwconfig ath0 mode Managed
$ iwconfig essid "LinuxAP"
$ iwconfig ap 00:11:22:AA:22:11
$ ifconfig ath0 192.168.1.10 netmask 255.255.255.0 up
$ route add -net default gw 192.168.1.1

It's not always necessary to specify the mac address for the ap, but sometimes it's a good thing. As you can see I chose an ip that was in the same subnet as the ap, it's important.

== DHCP server, firewall and stuff ==

Now, that was the static ip way and you probably want a dhcp-server and some firewall-rules for the ap. Guess what... here they come!

'''iptables'''

I have some rules with iptables in a script:

#!/bin/sh
IPTABLES='/sbin/iptables'
EXTIF='eth0'
INTIF='eth1'
WLAN='ath0'
WAN='85.235.31.133'

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

$IPTABLES -F
$IPTABLES -X

$IPTABLES -X -t nat
$IPTABLES -F -t nat

$IPTABLES -X -t filter
$IPTABLES -F -t filter

# enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

# forward LAN traffic from $INTIF1 to Internet interface $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

# allow ping
$IPTABLES -A INPUT -p icmp -i $EXTIF -j ACCEPT

# Allowing access to the FTP server"
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 21 -j ACCEPT

# Allowing access to the ssh server on port 2200 (I've changed it)
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 2200 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP

'''dnsmasq'''

And my dnsmasq.config looks like this:

resolv-file=/etc/resolv.conf
no-poll
domain-needed
bogus-priv
strict-order

interface=ath0
dhcp-range=192.168.1.10,192.168.1.50,12h

interface=eth1
dhcp-range=192.168.0.10,192.168.0.50,12h

# alice and bob are declared in /etc/hosts
dhcp-host=00:0A:E4:52:6B:12,alice
dhcp-host=00:40:CA:45:10:9C,bob

dhcp-authoritative

And that's it! Just run the script, start dnsmasq and connect to the ap described in the top of this wiki.

'''stuff'''

By the way, if you want to ping some host in the 192.168.0.0 subnet make sure that you don't have another interface that's not alive with an ip in that subnet. So if you have an ordinary wired card eth0 with an ip in the 192.168.0.0 subnet (but no cable in maybe) make sure that you bring that interface down.
$ ifconfig eth0 down
Now you can ping hosts in that subnet with your wifi card.

= External links =
== Howtos,Guides ==
*[http://www-106.ibm.com/developerworks/library/wi-enable.html?ca=dgr-lnxw82Linux4Wireless A nice overview] (''www-106.ibm.com'')
*[http://www.rustyspigot.com/groovyweb/?page_name=Linux%20Wireless&category=linux Wireless Tutorial] (''www.rustyspigot.com'')
*[http://www.ubuntuforums.org/showthread.php?t=202834 Wireless Security - WPA1 WPA2 LEAP AES, etc.] (''www.ubuntuforums.org'')

== Chipset list ==
*[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz list of all possible wlan chipsets] (''wiki.uni-konstanz.de'')
*[http://linux-wless.passys.nl Supported cards by manufacturer, chipset and interface (PCI, USB, PCMCIA)] (''linux-wless.passys.nl'')

== Specific cards ==
*[http://www.wmconnolley.org.uk/linux-wireless.html D-LINK DWL-650 (and/or DRC-650) under RH 8.0, kernel 2.4.18] (''www.wmconnolley.org.uk'')
*[http://www.netdigix.com/downloads/debian-linksys-wireless-howto.html Linksys WMP54G - 802.11G - kernel 2.4 - debian 3.0] (''www.netdigix.com'')
*[http://kennethjor.blogspot.com/2006/10/linksys-wusb54gc-ralink-rt73-and.html Linksys WUSB54GC - kernel 2.6.15 - Ubuntu 6.06] (''kennethjor.blogspot.com'')
*[http://wwwu.uni-klu.ac.at/agebhard/WUSB54GC/ Kernel module package for Ralink RT73 based USB WLAN adapters, such as Linksys WUSB54GC - Kernel 2.6.15 - Ubuntu 6.06] (''www.uni-klu.ac.at'')

[[Category:Networking]]
[[Category:Example]]
[[Category:Guides]]

Connect to a wireless local area network

2010-08-24T15:00:10Z

Sag47:

This covers how to get '''wireless''', or '''Wi-Fi''' [[networks]] to work under Linux, and the various applications that go along with them.

= Start =
You should start by means of your [[distribution]] - most probably, it works out of the box. Make sure you enabled WLAN on your laptop (there is mostly a button for it). Put it next to your WLAN router. Install your WLAN card as a network card, it will be called eth1,wlan0 or so. Use <code>[[iwconfig]]</code> to find out how it is called. You should be able to scan for wireless networks then, e.g. by
$ iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 00:0F:C9:01:F5:F4
ESSID:"foo"
Mode:Managed
Channel:10
Encryption key:off
Bit Rates:0 kb/s

$

If you get a <code>Command not found</code> error, install the [[Wireless tools]] and try again. 
If you do not get a list like the above, see the next section [[#Wireless_Configuration|Wireless configuration]]. 
If it works, you can continue with the section [[#Connect_to_an_Accesspoint|Connect to an Accesspoint]].

= Wireless Configuration =
The following provides the general steps required to get wireless networking enabled on your Linux machine.

== Gaining root access ==

Type su in your Terminal to log into root (you must type your root password. If you're on an Ubuntu-like where the root user is disabled then don't bother typing su but instead add sudo at the beginning of each command. If you're on Ubuntu and, like me, hate the sudo command then run sudo bash which logs you into root just like su.

In the command examples do not type '$' or '#' because $ signifies that the command is run as a normal user and # means the command is being run as the root user.

== Find out your wifi card's chipset ==

In order to get your card working you will have to determine its chipset.
There is one, generic, way for [http://en.wikipedia.org/wiki/Conventional_PCI PCI] and [http://en.wikipedia.org/wiki/PC_Card PCMCIA] cards, and one for [[USB]] cards:

*'''The generic way'''
**Run "[[hwinfo]] --wlan"
:If this command does not succeed, this can mean that you have an old [[kernel]] that does not recognize your card as a WLAN card. In this case, you cannot use it. Anyway, to find out its type use <code>hwinfo --[http://en.wikipedia.org/wiki/Conventional_PCI pci]</code> or <code>hwinfo --pcmcia</code>.

*'''Methods for [[USB]] cards'''
**Run <code>hwinfo --usb</code>.
:This will give you information about the chipset and tell you a ''Driver activation command'' (like "modprobe rt73usb").

Hopefully you now have a chipset name but...

== Which driver to load and how? ==

To find out which driver you have to load, use
hwinfo --wlan|grep -i driver
See below for additional relevant information on given chipsets or drivers.

'''Open Source'''
* [[WiFi Link 5100]]
* [[Intel PRO/Wireless 3945ABG]]
* [[Intel_Pro_Wireless]] 2100/2200/2915 -- Note that this requires http://sourceforge.net/projects/ieee80211
** ipw2200 on Suse 10.0, see [[Suse100ipw2200]]
* Prism 2/2.5/3: [[Prism_2_Drivers]]
* Ralink RT2400/2500, RT61, RT73: [[Ralink_Wireless_Drivers]]
* Atheros AR5210/5211/5212: [[MADWIFI]]
* Prism GT/Duette/Indigo: [[Prism54]]
* [[Broadcom 4318 Airforce one 54g card]]
* Texas Instruments ACX100/111: [http://acx100.sourceforge.net/ acx100]
* Atmel: [[AT76C5XXx]]
* [[Belkin_F5D6020_ver.2]]
* [[Net_Gear_WG121_on_Mandrake_10.0_Linux]]
* Linksys [[WMP54G Wireless how-to for Ubuntu 8.10]] Intrepid Ibex
* Almost every other chipset: [[NDIS_Wrapper]]
'''Proprietary'''
* [[Linuxant Driverloader]]

Note that [[building]] a [[kernel module]] requires the kernel sources.
Download your driver sources in .tar.gz format and [[compile from source]].

= Connect to an Accesspoint =

This chapter covers how to connect to an unencrypted or WEP encrypted accesspoint. [[wpa|For WPA encryption, have a look here]]. The example interface will be called wlan0.

To set up the interface, start by:

$ ifconfig wlan0 up

If you want, you could scan for an accesspoint first:

$ iwlist wlan0 scanning

You will then see the available accesspoints, their ESSID's, the frequency, etc.
To associate with an accesspoint (for example "test"), run:
$ iwconfig wlan0 essid test
Most drivers will automatically find the right channel in a minute.
You should now be able to see something like this when you run iwconfig:
$ iwconfig
lo no wireless extensions

wlan0 IEEE 802.11b ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key: off
Power Management:off
Link Quality=0/0 Signal level=0/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This means that everything has been installed properly.

== Using WEP encryption ==

If the accesspoint uses WEP, you set the encryption like so:
$ iwconfig wlan0 key s:"the_ascii_key"
Or you can use a hexadecimal key:
$ iwconfig wlan0 key 00000000000
The bits of encryption is determined by the key length. Note that this command, along with the key, can be seen in "ps aux".

# ifconfig ath0 down
# iwconfig ath0 essid disaster-master enc 1234abcdef mode Managed channel auto
# ifconfig ath0 up
# dhclient ath0

If you don't like typing a large command sequence to reconnect your login each time then here is a helpful script which can speed up the process.
#!/bin/sh
#this is a comment
#all commands must be run as root (script must be run as root or as startup script)

#Router WEP settings
iface=ath0
ssid=disaster-master
wephexkey=1234abcdef
chan=auto

#setting up and applying wireless config, no need to edit beyond this point
ifconfig $iface down
iwconfig $iface essid $ssid enc $wephexkey mode Managed channel $chan
ifconfig $iface up
dhclient $iface

== Use WPA/WPA2 Personal ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-PSK or WPA2-PSK.

My network SSID is called disaster-master and it's currently running WPA2-PSK encryption on it. My WPA2 passphrase is "hindrance".

First create two text files and save them as wireless-wpa.sh and wireless-wpa.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa.sh'''
#!/bin/sh
iface=ath0

#shut down interface
ifconfig $iface down

#set ad-hoc/management of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#stop any persistent wireless wpa2 sessions
killall wpa_supplicant

#apply WPA/WPA2 personal settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa.conf'''
# disaster-master network using WPA2-PSK

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="disaster-master"
scan_ssid=1
key_mgmt=WPA-PSK
psk="hindrance"
}
Don't forget to edit wireless-wpa.sh and set iface equal to your wireless device and edit wireless-wpa.conf with your WPA settings. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''). Run the following command sequence:
# chmod 755 wireless-wpa.sh
# chmod 644 wireless-wpa.conf
# ./wireless-wpa.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa.sh every time you restart your computer.

== Use WPA/WPA2 Enterprise ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-Enterprise or WPA2-Enterprise.

My enterprise network SSID is called dragonfly3 and it has a radius login server at radius.irt.drexel.edu (which is automatically detected and not needed to be set up). The Enterprise network is currently running WPA2-Enterprise encryption with IEEE 802.1X login using EAP-TTLS/MSCHAPv2. My login (not real) at radius.irt.drexel.edu is "abc123" and my password is "hindrance".

First create two text files and save them as wireless-wpa-enterprise.sh and wireless-wpa-enterprise.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa-enterprise.sh'''
#!/bin/sh
iface=ath0

#stop any persistent wireless wpa2 authentication sessions
killall wpa_supplicant

#shut down wireless interface
ifconfig $iface down

#set working mode of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#apply dragonfly3 settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa-enterprise.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa-enterprise.conf'''
# Drexel dragonfly3 IEEE 802.1X login using EAP-TTLS/MSCHAPv2

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dragonfly3"
scan_ssid=0
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS
phase2="auth=MSCHAPV2"
identity="abc123"
password="hindrance"
}
Don't forget to edit wireless-wpa-enterprise.sh and set iface equal to your wireless device and edit wireless-wpa-enterprise.conf with your network SSID and enterprise login information. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''. Run the following command sequence:
# chmod 755 wireless-wpa-enterprise.sh
# chmod 644 wireless-wpa-enterprise.conf
# ./wireless-wpa-enterprise.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa-enterprise.sh every time you restart your computer.

== Getting an IP address ==

If you have associated properly, you should see the accesspoint's mac address in from iwconfig instead of 00:00:00:00:00:00. If the network you have connected to uses dhcp, it is time to obtain an ip address:
$ dhclient wlan0
Or:
$ dhcpcd wlan0
You should see "DHCPOFFER" or similar in a minute if all went well. If it sits there for a while with no DHCPOFFER, then something is wrong. Perhaps the encryption key was incorrect.

However, if you would connect to a AP that doesn't have a dhcp server, you can do the following:

First scan for the AP so you can see the ESSID and the mac address. Do the following
$ iwconfig wlan0 essid "MyAP" (if that's the ESSID)
$ iwconfig wlan0 ap 00:40:CA:45:10:9C (if that's the mac)
$ ifconfig wlan0 192.168.0.20 up
$ route add -net default gw 192.168.0.1
Provided that the AP has the IP 192.168.0.1.

== Autostarting network configuration ==
I found a really good post which tells you how to do this [http://www.howtoforge.com/forums/showthread.php?p=22384#post22384 located here] and create the necessary system startup links. Depending on your distribution you can do it with chkconfig (RedHat, Fedora, CentOS, Mandriva, SuSE) or update-rc.d (Debian, Ubuntu). I'm going to proceed explaining how to manually set up a startup script rather than using the automated method like update-rc.d. This is per the documentation from the [http://www.debian.org/doc/debian-policy/ch-opersys.html Debian Policy Manual Section 9.3].

The directory for startup scripts is located in ''/etc/rcS.d''. Do a quick listing and see what is in your bootup script directory using ''ls /etc/rcS.d'':
: '''ls /etc/rcS.d'''
README S35mountall.sh
S01mountkernfs.sh S36mountall-bootclean.sh
S01readahead S37apparmor
S02hostname.sh S37mountoverflowtmp
S06keyboard-setup S37udev-finish
S07linux-restricted-modules-common S39readahead-desktop
S08hwclockfirst.sh S39ufw
S08loopback S40networking
S10udev S45mountnfs.sh
S11hwclock.sh S46mountnfs-bootclean.sh
S11mountdevsubfs.sh S49console-setup
S13pcmciautils S55bootmisc.sh
S15module-init-tools S55dns-clean
S17procps S55pppd-dns
S20checkroot.sh S55urandom
S22mtab.sh S70screen-cleanup
S25brltty S70x11-common
S30checkfs.sh S90console-screen.kbd.sh
Here is what my readme readme says:
: '''cat /etc/rcS.d/README'''
The scripts in this directory whose names begin with an 'S' are executed
once when booting the system, even when booting directly into single user
mode.

The scripts are all symbolic links whose targets are located in
/etc/init.d/ .

To disable a script in this directory, rename it so that it begins with
a 'K'.

For more information see /etc/init.d/README.

The following sequence points are defined at this time:

* After the S40 scripts have executed, all local file systems are mounted
and networking is available. All device drivers have been initialized.

* After the S60 scripts have executed, the system clock has been set, NFS
filesystems have been mounted (unless the system depends on the automounter,
which is started later) and the filesystems have been cleaned.
As a quick side note, if you are using WPA then you need to edit your ''wireless-wpa.sh'' script and change ''./wireless-wpa.conf'' to ''/etc/init.d/wireless-wpa.conf''. Here's the newly formatted command:
wpa_supplicant -B -Dwext -i $iface -c /etc/init.d/wireless-wpa.conf -dd
And also please note from the README that ''"After the S40 scripts have executed, all local file systems are mounted and networking is available. All device drivers have been initialized."'' As you can see from my listing that I have no S41 script so I'm going to make that my wireless networking startup script and call it ''S41wlan_net_connect'' (you can call it ''S41'' whatever you want if you don't like it). Browse to the directory where you have your wireless-wpa.sh, then switch to root user and run the following command sequence:
cp ./wireless-wpa.sh /etc/init.d/wireless-wpa.sh
cp ./wireless-wpa.conf /etc/init.d/wireless-wpa.conf
chmod 755 /etc/init.d/wireless-wpa.sh
chmod 644 /etc/init.d/wireless-wpa.conf
ln -s /etc/init.d/wireless-wpa.sh /etc/rcS.d/S41wlan_net_connect
We just finished creating the symbolic link (ln -s) so now test it by restarting. It should be set up as a startup script now.

= Create an access point =

It is fairly simple to setup an AP in linux. This is how I did.

I purchased a D-Link DWL-G520 pci card. You need a card that supports Master mode. Check [http://linux-wless.passys.nl this] (''linux-wless.passys.nl'') site for compatibility with Linux, I think ndiswrapper doesn't have support for Master mode, not sure though.

'''Creating the AP'''

Then if your interface is ath0:

$ iwconfig ath0 mode Master
$ iwconfig ath0 essid "LinuxAP"
$ ifconfig ath0 192.168.1.1 up

I chose an IP that wasn't in my wired LANs subnet.
Now you should be able to see the AP if you scan for APs.

'''Configure statically your client's card'''

Then on the client side (if your interface is ath0) you do:

$ iwconfig ath0 mode Managed
$ iwconfig essid "LinuxAP"
$ iwconfig ap 00:11:22:AA:22:11
$ ifconfig ath0 192.168.1.10 netmask 255.255.255.0 up
$ route add -net default gw 192.168.1.1

It's not always necessary to specify the mac address for the ap, but sometimes it's a good thing. As you can see I chose an ip that was in the same subnet as the ap, it's important.

== DHCP server, firewall and stuff ==

Now, that was the static ip way and you probably want a dhcp-server and some firewall-rules for the ap. Guess what... here they come!

'''iptables'''

I have some rules with iptables in a script:

#!/bin/sh
IPTABLES='/sbin/iptables'
EXTIF='eth0'
INTIF='eth1'
WLAN='ath0'
WAN='85.235.31.133'

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

$IPTABLES -F
$IPTABLES -X

$IPTABLES -X -t nat
$IPTABLES -F -t nat

$IPTABLES -X -t filter
$IPTABLES -F -t filter

# enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

# forward LAN traffic from $INTIF1 to Internet interface $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

# allow ping
$IPTABLES -A INPUT -p icmp -i $EXTIF -j ACCEPT

# Allowing access to the FTP server"
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 21 -j ACCEPT

# Allowing access to the ssh server on port 2200 (I've changed it)
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 2200 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP

'''dnsmasq'''

And my dnsmasq.config looks like this:

resolv-file=/etc/resolv.conf
no-poll
domain-needed
bogus-priv
strict-order

interface=ath0
dhcp-range=192.168.1.10,192.168.1.50,12h

interface=eth1
dhcp-range=192.168.0.10,192.168.0.50,12h

# alice and bob are declared in /etc/hosts
dhcp-host=00:0A:E4:52:6B:12,alice
dhcp-host=00:40:CA:45:10:9C,bob

dhcp-authoritative

And that's it! Just run the script, start dnsmasq and connect to the ap described in the top of this wiki.

'''stuff'''

By the way, if you want to ping some host in the 192.168.0.0 subnet make sure that you don't have another interface that's not alive with an ip in that subnet. So if you have an ordinary wired card eth0 with an ip in the 192.168.0.0 subnet (but no cable in maybe) make sure that you bring that interface down.
$ ifconfig eth0 down
Now you can ping hosts in that subnet with your wifi card.

= External links =
== Howtos,Guides ==
*[http://www-106.ibm.com/developerworks/library/wi-enable.html?ca=dgr-lnxw82Linux4Wireless A nice overview] (''www-106.ibm.com'')
*[http://www.rustyspigot.com/groovyweb/?page_name=Linux%20Wireless&category=linux Wireless Tutorial] (''www.rustyspigot.com'')
*[http://www.ubuntuforums.org/showthread.php?t=202834 Wireless Security - WPA1 WPA2 LEAP AES, etc.] (''www.ubuntuforums.org'')

== Chipset list ==
*[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz list of all possible wlan chipsets] (''wiki.uni-konstanz.de'')
*[http://linux-wless.passys.nl Supported cards by manufacturer, chipset and interface (PCI, USB, PCMCIA)] (''linux-wless.passys.nl'')

== Specific cards ==
*[http://www.wmconnolley.org.uk/linux-wireless.html D-LINK DWL-650 (and/or DRC-650) under RH 8.0, kernel 2.4.18] (''www.wmconnolley.org.uk'')
*[http://www.netdigix.com/downloads/debian-linksys-wireless-howto.html Linksys WMP54G - 802.11G - kernel 2.4 - debian 3.0] (''www.netdigix.com'')
*[http://kennethjor.blogspot.com/2006/10/linksys-wusb54gc-ralink-rt73-and.html Linksys WUSB54GC - kernel 2.6.15 - Ubuntu 6.06] (''kennethjor.blogspot.com'')
*[http://wwwu.uni-klu.ac.at/agebhard/WUSB54GC/ Kernel module package for Ralink RT73 based USB WLAN adapters, such as Linksys WUSB54GC - Kernel 2.6.15 - Ubuntu 6.06] (''www.uni-klu.ac.at'')

[[Category:Networking]]
[[Category:Example]]
[[Category:Guides]]

Connect to a wireless local area network

2010-08-24T14:52:01Z

Sag47:

This covers how to get '''wireless''', or '''Wi-Fi''' [[networks]] to work under Linux, and the various applications that go along with them.

= Start =
You should start by means of your [[distribution]] - most probably, it works out of the box. Make sure you enabled WLAN on your laptop (there is mostly a button for it). Put it next to your WLAN router. Install your WLAN card as a network card, it will be called eth1,wlan0 or so. Use <code>[[iwconfig]]</code> to find out how it is called. You should be able to scan for wireless networks then, e.g. by
$ iwlist wlan0 scanning
wlan0 Scan completed :
Cell 01 - Address: 00:0F:C9:01:F5:F4
ESSID:"foo"
Mode:Managed
Channel:10
Encryption key:off
Bit Rates:0 kb/s

$

If you get a <code>Command not found</code> error, install the [[Wireless tools]] and try again. 
If you do not get a list like the above, see the next section [[#Wireless_Configuration|Wireless configuration]]. 
If it works, you can continue with the section [[#Connect_to_an_Accesspoint|Connect to an Accesspoint]].

= Wireless Configuration =
The following provides the general steps required to get wireless networking enabled on your Linux machine.

== Gaining root access ==

Type su in your Terminal to log into root (you must type your root password. If you're on an Ubuntu-like where the root user is disabled then don't bother typing su but instead add sudo at the beginning of each command. If you're on Ubuntu and, like me, hate the sudo command then run sudo bash which logs you into root just like su.

In the command examples do not type '$' or '#' because $ signifies that the command is run as a normal user and # means the command is being run as the root user.

== Find out your wifi card's chipset ==

In order to get your card working you will have to determine its chipset.
There is one, generic, way for [http://en.wikipedia.org/wiki/Conventional_PCI PCI] and [http://en.wikipedia.org/wiki/PC_Card PCMCIA] cards, and one for [[USB]] cards:

*'''The generic way'''
**Run "[[hwinfo]] --wlan"
:If this command does not succeed, this can mean that you have an old [[kernel]] that does not recognize your card as a WLAN card. In this case, you cannot use it. Anyway, to find out its type use <code>hwinfo --[http://en.wikipedia.org/wiki/Conventional_PCI pci]</code> or <code>hwinfo --pcmcia</code>.

*'''Methods for [[USB]] cards'''
**Run <code>hwinfo --usb</code>.
:This will give you information about the chipset and tell you a ''Driver activation command'' (like "modprobe rt73usb").

Hopefully you now have a chipset name but...

== Which driver to load and how? ==

To find out which driver you have to load, use
hwinfo --wlan|grep -i driver
See below for additional relevant information on given chipsets or drivers.

'''Open Source'''
* [[WiFi Link 5100]]
* [[Intel PRO/Wireless 3945ABG]]
* [[Intel_Pro_Wireless]] 2100/2200/2915 -- Note that this requires http://sourceforge.net/projects/ieee80211
** ipw2200 on Suse 10.0, see [[Suse100ipw2200]]
* Prism 2/2.5/3: [[Prism_2_Drivers]]
* Ralink RT2400/2500, RT61, RT73: [[Ralink_Wireless_Drivers]]
* Atheros AR5210/5211/5212: [[MADWIFI]]
* Prism GT/Duette/Indigo: [[Prism54]]
* [[Broadcom 4318 Airforce one 54g card]]
* Texas Instruments ACX100/111: [http://acx100.sourceforge.net/ acx100]
* Atmel: [[AT76C5XXx]]
* [[Belkin_F5D6020_ver.2]]
* [[Net_Gear_WG121_on_Mandrake_10.0_Linux]]
* Linksys [[WMP54G Wireless how-to for Ubuntu 8.10]] Intrepid Ibex
* Almost every other chipset: [[NDIS_Wrapper]]
'''Proprietary'''
* [[Linuxant Driverloader]]

Note that [[building]] a [[kernel module]] requires the kernel sources.
Download your driver sources in .tar.gz format and [[compile from source]].

= Connect to an Accesspoint =

This chapter covers how to connect to an unencrypted or WEP encrypted accesspoint. [[wpa|For WPA encryption, have a look here]]. The example interface will be called wlan0.

To set up the interface, start by:

$ ifconfig wlan0 up

If you want, you could scan for an accesspoint first:

$ iwlist wlan0 scanning

You will then see the available accesspoints, their ESSID's, the frequency, etc.
To associate with an accesspoint (for example "test"), run:
$ iwconfig wlan0 essid test
Most drivers will automatically find the right channel in a minute.
You should now be able to see something like this when you run iwconfig:
$ iwconfig
lo no wireless extensions

wlan0 IEEE 802.11b ESSID:"test"
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:11 Mb/s Tx-Power=15 dBm
Retry limit:8 RTS thr=1536 B Fragment thr=1536 B
Encryption key: off
Power Management:off
Link Quality=0/0 Signal level=0/255 Noise level=0/0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This means that everything has been installed properly.

== Using WEP encryption ==

If the accesspoint uses WEP, you set the encryption like so:
$ iwconfig wlan0 key s:"the_ascii_key"
Or you can use a hexadecimal key:
$ iwconfig wlan0 key 00000000000
The bits of encryption is determined by the key length. Note that this command, along with the key, can be seen in "ps aux".

# ifconfig ath0 down
# iwconfig ath0 essid disaster-master enc 1234abcdef mode Managed channel auto
# ifconfig ath0 up
# dhclient ath0

If you don't like typing a large command sequence to reconnect your login each time then here is a helpful script which can speed up the process.
#!/bin/sh
#this is a comment
#all commands must be run as root (script must be run as root or as startup script)

#Router WEP settings
iface=ath0
ssid=disaster-master
wephexkey=1234abcdef
chan=auto

#setting up and applying wireless config, no need to edit beyond this point
ifconfig $iface down
iwconfig $iface essid $ssid enc $wephexkey mode Managed channel $chan
ifconfig $iface up
dhclient $iface

== Use WPA/WPA2 Personal ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-PSK or WPA2-PSK.

My network SSID is called disaster-master and it's currently running WPA2-PSK encryption on it. My WPA2 passphrase is "hindrance".

First create two text files and save them as wireless-wpa.sh and wireless-wpa.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa.sh'''
#!/bin/sh
iface=ath0

#shut down interface
ifconfig $iface down

#set ad-hoc/management of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#stop any persistent wireless wpa2 sessions
killall wpa_supplicant

#apply WPA/WPA2 personal settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa.conf'''
# disaster-master network using WPA2-PSK

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="disaster-master"
scan_ssid=1
key_mgmt=WPA-PSK
psk="hindrance"
}
Don't forget to edit wireless-wpa.sh and set iface equal to your wireless device and edit wireless-wpa.conf with your WPA settings. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''). Run the following command sequence:
# chmod 755 wireless-wpa.sh
# chmod 644 wireless-wpa.conf
# ./wireless-wpa.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa.sh every time you restart your computer.

== Use WPA/WPA2 Enterprise ==
For this you must have the wpasupplicant package installed on your distro in order to use the wpa_supplicant and related commands. This tutorial is the same whether you are using WPA-Enterprise or WPA2-Enterprise.

My enterprise network SSID is called dragonfly3 and it has a radius login server at radius.irt.drexel.edu (which is automatically detected and not needed to be set up). The Enterprise network is currently running WPA2-Enterprise encryption with IEEE 802.1X login using EAP-TTLS/MSCHAPv2. My login (not real) at radius.irt.drexel.edu is "abc123" and my password is "hindrance".

First create two text files and save them as wireless-wpa-enterprise.sh and wireless-wpa-enterprise.conf and make sure that they are saved into the same directory. Copy the following contents into each file.
: '''wireless-wpa-enterprise.sh'''
#!/bin/sh
iface=ath0

#stop any persistent wireless wpa2 authentication sessions
killall wpa_supplicant

#shut down wireless interface
ifconfig $iface down

#set working mode of wireless device
iwconfig $iface mode Managed

#enable interface
ifconfig $iface up

#apply dragonfly3 settings to device
wpa_supplicant -B -Dwext -i $iface -c ./wireless-wpa-enterprise.conf -dd

#obtain an IP address
dhclient $iface
: '''wireless-wpa-enterprise.conf'''
# Drexel dragonfly3 IEEE 802.1X login using EAP-TTLS/MSCHAPv2

ctrl_interface=/var/run/wpa_supplicant

network={
ssid="dragonfly3"
scan_ssid=0
key_mgmt=WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
eap=TTLS
phase2="auth=MSCHAPV2"
identity="abc123"
password="hindrance"
}
Don't forget to edit wireless-wpa-enterprise.sh and set iface equal to your wireless device and edit wireless-wpa-enterprise.conf with your network SSID and enterprise login information. Navigate to the current directory of your shell scripts in your terminal (mine are located in ''~/Documents/wireless/''. Run the following command sequence:
# chmod 755 wireless-wpa-enterprise.sh
# chmod 644 wireless-wpa-enterprise.conf
# ./wireless-wpa-enterprise.sh
You should be successfully connected to your WPA/WPA2 wireless network. Please note that you only need to run the chmod commands the first time. After that you don't need to run them. You must run wireless-wpa-enterprise.sh every time you restart your computer.

== Getting an IP address ==

If you have associated properly, you should see the accesspoint's mac address in from iwconfig instead of 00:00:00:00:00:00. If the network you have connected to uses dhcp, it is time to obtain an ip address:
$ dhclient wlan0
Or:
$ dhcpcd wlan0
You should see "DHCPOFFER" or similar in a minute if all went well. If it sits there for a while with no DHCPOFFER, then something is wrong. Perhaps the encryption key was incorrect.

However, if you would connect to a AP that doesn't have a dhcp server, you can do the following:

First scan for the AP so you can see the ESSID and the mac address. Do the following
$ iwconfig wlan0 essid "MyAP" (if that's the ESSID)
$ iwconfig wlan0 ap 00:40:CA:45:10:9C (if that's the mac)
$ ifconfig wlan0 192.168.0.20 up
$ route add -net default gw 192.168.0.1
Provided that the AP has the IP 192.168.0.1.

= Create an access point =

It is fairly simple to setup an AP in linux. This is how I did.

I purchased a D-Link DWL-G520 pci card. You need a card that supports Master mode. Check [http://linux-wless.passys.nl this] (''linux-wless.passys.nl'') site for compatibility with Linux, I think ndiswrapper doesn't have support for Master mode, not sure though.

'''Creating the AP'''

Then if your interface is ath0:

$ iwconfig ath0 mode Master
$ iwconfig ath0 essid "LinuxAP"
$ ifconfig ath0 192.168.1.1 up

I chose an IP that wasn't in my wired LANs subnet.
Now you should be able to see the AP if you scan for APs.

'''Configure statically your client's card'''

Then on the client side (if your interface is ath0) you do:

$ iwconfig ath0 mode Managed
$ iwconfig essid "LinuxAP"
$ iwconfig ap 00:11:22:AA:22:11
$ ifconfig ath0 192.168.1.10 netmask 255.255.255.0 up
$ route add -net default gw 192.168.1.1

It's not always necessary to specify the mac address for the ap, but sometimes it's a good thing. As you can see I chose an ip that was in the same subnet as the ap, it's important.

== DHCP server, firewall and stuff ==

Now, that was the static ip way and you probably want a dhcp-server and some firewall-rules for the ap. Guess what... here they come!

'''iptables'''

I have some rules with iptables in a script:

#!/bin/sh
IPTABLES='/sbin/iptables'
EXTIF='eth0'
INTIF='eth1'
WLAN='ath0'
WAN='85.235.31.133'

/bin/echo 1 > /proc/sys/net/ipv4/ip_forward

$IPTABLES -F
$IPTABLES -X

$IPTABLES -X -t nat
$IPTABLES -F -t nat

$IPTABLES -X -t filter
$IPTABLES -F -t filter

# enable masquerading to allow LAN internet access
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

# forward LAN traffic from $INTIF1 to Internet interface $EXTIF
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -m state --state NEW,ESTABLISHED -j ACCEPT

# allow ping
$IPTABLES -A INPUT -p icmp -i $EXTIF -j ACCEPT

# Allowing access to the FTP server"
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 21 -j ACCEPT

# Allowing access to the ssh server on port 2200 (I've changed it)
$IPTABLES -A INPUT -i $EXTIF -p tcp --dport 2200 -j ACCEPT

# block out all other Internet access on $EXTIF
$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,INVALID -j DROP
$IPTABLES -A FORWARD -i $EXTIF -m state --state NEW,INVALID -j DROP

'''dnsmasq'''

And my dnsmasq.config looks like this:

resolv-file=/etc/resolv.conf
no-poll
domain-needed
bogus-priv
strict-order

interface=ath0
dhcp-range=192.168.1.10,192.168.1.50,12h

interface=eth1
dhcp-range=192.168.0.10,192.168.0.50,12h

# alice and bob are declared in /etc/hosts
dhcp-host=00:0A:E4:52:6B:12,alice
dhcp-host=00:40:CA:45:10:9C,bob

dhcp-authoritative

And that's it! Just run the script, start dnsmasq and connect to the ap described in the top of this wiki.

'''stuff'''

By the way, if you want to ping some host in the 192.168.0.0 subnet make sure that you don't have another interface that's not alive with an ip in that subnet. So if you have an ordinary wired card eth0 with an ip in the 192.168.0.0 subnet (but no cable in maybe) make sure that you bring that interface down.
$ ifconfig eth0 down
Now you can ping hosts in that subnet with your wifi card.

= External links =
== Howtos,Guides ==
*[http://www-106.ibm.com/developerworks/library/wi-enable.html?ca=dgr-lnxw82Linux4Wireless A nice overview] (''www-106.ibm.com'')
*[http://www.rustyspigot.com/groovyweb/?page_name=Linux%20Wireless&category=linux Wireless Tutorial] (''www.rustyspigot.com'')
*[http://www.ubuntuforums.org/showthread.php?t=202834 Wireless Security - WPA1 WPA2 LEAP AES, etc.] (''www.ubuntuforums.org'')

== Chipset list ==
*[http://wiki.uni-konstanz.de/wiki/bin/view/Wireless/ListeChipsatz list of all possible wlan chipsets] (''wiki.uni-konstanz.de'')
*[http://linux-wless.passys.nl Supported cards by manufacturer, chipset and interface (PCI, USB, PCMCIA)] (''linux-wless.passys.nl'')

== Specific cards ==
*[http://www.wmconnolley.org.uk/linux-wireless.html D-LINK DWL-650 (and/or DRC-650) under RH 8.0, kernel 2.4.18] (''www.wmconnolley.org.uk'')
*[http://www.netdigix.com/downloads/debian-linksys-wireless-howto.html Linksys WMP54G - 802.11G - kernel 2.4 - debian 3.0] (''www.netdigix.com'')
*[http://kennethjor.blogspot.com/2006/10/linksys-wusb54gc-ralink-rt73-and.html Linksys WUSB54GC - kernel 2.6.15 - Ubuntu 6.06] (''kennethjor.blogspot.com'')
*[http://wwwu.uni-klu.ac.at/agebhard/WUSB54GC/ Kernel module package for Ralink RT73 based USB WLAN adapters, such as Linksys WUSB54GC - Kernel 2.6.15 - Ubuntu 6.06] (''www.uni-klu.ac.at'')

[[Category:Networking]]
[[Category:Example]]
[[Category:Guides]]

User talk:ThorstenStaerk

2010-08-24T14:19:22Z

Sag47:

User talk:ThorstenStaerk

2010-08-24T14:15:46Z

Sag47: /* Re: templates Rh */ new section

User talk:ThorstenStaerk

2010-08-24T00:43:10Z

Sag47: /* interesting website and stuff */ new section

Vim

2010-08-24T00:21:11Z

Sag47: /* A tutorial */

'''vim''' ('''vi''' i'''m'''proved) is a contemporary version of the classic [[vi]] editor, with additional capabilites.

== Introduction ==
All [[UNIX]] machines typically come with the [[vi]] [[text editor]]. However, vi lacks some more contemporary features (for example, syntax highlighting). This is where '''vim''' comes in. If you know how to use vi, you'll find vim to be the same except it has a number of useful features added to make editing easier. If you don't yet know how to use vi or vim, and you didn't come from using [[ed]], you'll find the learning curve quite steep (which means, it might take you a while to learn to achieve maximum proficiency).

Vim was originally written by (and is still primarily maintained by) Bram Moolenaar. It started as a personal desire to have a useful vi-clone for the Amiga, but eventually grew as more features were added. It now runs on a variety of platforms (including Unix work-a-likes, e.g. GNU/Linux, Mac OS X, and *BSD; Amiga; Windows; Mac "Classic"; and OS/2) and supports a variety of graphical toolkits (including GTK, QT, and Carbon) in addition to the command-line interface. VIM is also the latin word for "power" or "force".

Vim has a compatibility mode which produces an almost vi-compatible experience (the version of vi used seems to be one released with Sun OS 4.x, from Version 3.7 dated on 6/7/85). This is enabled by using the ":set compatible" ex-command or by running Vim with the -C option.

== Tips ==

=== Learning ===
To learn [[vim]], [[open a console]] and call
[http://linuxcommand.org/man_pages/vimtutor1.html vimtutor]

==== A tutorial ====
While vim is not as easy to learn initially as it is to learn nano, there are plenty advantages to using it. Some great features of vim are copy, cut, and paste. Also there is code styling for programmers and there's also an undo/redo feature which is awesome.

There are three modes for vim (That I know of right now). There is the visual mode, insert mode, and the command mode. Before I start breaking down the different modes let me say this: every time you delete or copy text in the command or visual mode, the deleted text is loaded into a special buffer. This buffer continues to hold the text until you delete more text/characters/lines in which case the buffer will be replaced with the newly deleted text.

When you first open a file with command vim myfile you start out in the command mode. If the file myfile exists then it will load myfile into the editor. If the file myfile does not exist then it will create a blank file with myfile as its save path which can be modified but myfile will not be created on your hard drive until you save the document.

Pressing the i key will put the editor into insert mode. Go ahead and put the editor into insert mode and type some random text you can play with. In fact you should type a couple of lines.

Pressing the Esc while in insert mode will take the editor out of insert mode and back into command mode. Now each letter on your keyboard has turned into a command which manipulates the document instead of keys which insert text into the document.

Pressing the v key puts the editor into visual mode. Visual mode is used to highlight text in the document so you can apply different commands just to that text. If you accidentally go into visual mode or you've highlighted text and don't want to do anything to it then press the v key to go back into command mode.

While in command mode, pressing the colon key (: ) opens the editors command line where you can type a command for the editor to manipulate the whole document and not just some text or a few lines. For example in the editors command line you can save the document, quit the document, quit without saving, undo change, and redo change to name a few. You can even combine commands to do them at the same time such as save and quit at the same time.

That's most of the explanation behind it. Now remember the three modes: command, insert, and visual. Everything is centralized around the command mode. Also remember the editor command line which is accessed when in the command mode. Now that I've explained all that here is what happens when pressing different keys in the different modes.

When in command mode press the colon (: ) to enter the editor command line. Here are different editor commands.
command - explanation
{| border="1"
| :w
| write/save the document
|-
| :q
| quit vim
|-
| :q!
| quit vim without saving
|-
| :u
| undo
|-
| :r
| redo
|-
| :wq
| write/save the document and then quit vim
|}
If you accidentally enter the editor command line pressing Esc twice will put you back into command mode.

When you're in the command mode different keys have different functions. The commands are case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left
|-
| j
| move cursor down
|-
| k
| move cursor up
|-
| l
| move cursor right
|-
| w
| move the cursor right and down the document accross each word instead of each character.
|-
| ZZ
| same as :wq. write/save the document and then quit vim. Double tap the z key while holding the shift key (double click).
|-
| dd
| cuts/deletes an entire line of text. Double tab the d key (double click).
|-
| dw
| cuts/deletes a words of text
|-
| yy
| copies an entire line of text. Double tap the y key (double click).
|-
| p
| paste text after: if copied entire line then it will paste text after the current line. if copied a few characters then paste them after the current character.
|-
| P
| same as p but pastes text before the current character/line.
|-
| i
| enters editor into insert mode
|-
| o
| inserts a new line after the current line and then places the editor into insert mode.
|-
| u
| Undo the last edit. Same as :u.
|-
| v
| enters the editor into visual mode.
|-
| r
| replace. When you push a key after pressing r the letter the cursor is currently located on is replaced with the key pressed. You are still in command mode.
|-
| R
| replace. puts the editor into insert mode however it overwrites replacing each character if one already exists.
|-
| x
| delete a character
|}

When you're in insert mode every key on the keyboard types text into the document like a normal text editor. When you wish to leave insert mode press the Esc key.

When you're in the visual mode you can highlight text and apply different commands to it. The commands are similar to command mode and are also case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left (highlighting text)
|-
| j
| move cursor down (highlighting text)
|-
| k
| move cursor up (highlighting text)
|-
| l
| move cursor right (highlighting text)
|-
| y
| copy the highlighted text and enter back into command mode
|-
| d
| cut/delete the hightlighted text and enter back into command mode
|-
| p
| paste the text from the buffer replacing the highlighted text.
|}

The following command opens myfile and automatically goes to line 23.
vim +23 myfile

It's a bit of a task remembering all those commands. The best way to learn them is to try to use vim regularly referring to those commands for the different modes. There's a lot more commands and tricks you can do in vim. Those are just the basic ones.

=== ~/.vimrc ===
To make a config file for vim, create a file in your home directory called .vimrc, and fill it with stuff that you'd normally type into vim's "ex" mode. For example, if you regularly do ":syntax on" from inside vim, put "syntax on" (no colon or quotes) on a line by itself in your ~/.vimrc file.

Here's the contents of a useful .vimrc file:
<pre>
syntax on
set number
set expandtab
set tabstop=4
set shiftwidth=4
set autoindent
</pre>

Where:
* "syntax on" turns on syntax highlighting
* "set number" turns on line numbers
* "set expandtab" makes vim insert spaces (instead of tabs) whenever you hit the tab key
* "set tabstop=4" sets tabs to equal 4 spaces
* "set shiftwidth=4" makes it so when you use the text shifting command, it shifts over using 4-space indents.
* "set autoindent" has vim use "smart indenting", ie. when you are tabbed out to, say, the 8th column, and you type something then hit enter, the cursor is helpfully placed at the 8th column again for you.

Additionally you can turn any single argument command off by adding an exclamation point (!). So "set number" can be turned off by "set number!"

(You can shut off line numbering from command mode by typing <tt>:set nonumber</tt>.)

=== Syntax highlighting ===

You can turn syntax highlighting on/off with:
:syntax off
:syntax on

If you have syntax highlighting on, but are using a dark background and the colors don't show up well, you can use this command:
:set background=dark

==External links==
*[http://www.vim.org Vim Homepage] (''www.vim.org'')
*[http://vi-improved.org/wiki/index.php #vim wiki] (''vi-improved.org'')

[[Category:Editors]]

Vim

2010-08-24T00:18:33Z

Sag47:

'''vim''' ('''vi''' i'''m'''proved) is a contemporary version of the classic [[vi]] editor, with additional capabilites.

== Introduction ==
All [[UNIX]] machines typically come with the [[vi]] [[text editor]]. However, vi lacks some more contemporary features (for example, syntax highlighting). This is where '''vim''' comes in. If you know how to use vi, you'll find vim to be the same except it has a number of useful features added to make editing easier. If you don't yet know how to use vi or vim, and you didn't come from using [[ed]], you'll find the learning curve quite steep (which means, it might take you a while to learn to achieve maximum proficiency).

Vim was originally written by (and is still primarily maintained by) Bram Moolenaar. It started as a personal desire to have a useful vi-clone for the Amiga, but eventually grew as more features were added. It now runs on a variety of platforms (including Unix work-a-likes, e.g. GNU/Linux, Mac OS X, and *BSD; Amiga; Windows; Mac "Classic"; and OS/2) and supports a variety of graphical toolkits (including GTK, QT, and Carbon) in addition to the command-line interface. VIM is also the latin word for "power" or "force".

Vim has a compatibility mode which produces an almost vi-compatible experience (the version of vi used seems to be one released with Sun OS 4.x, from Version 3.7 dated on 6/7/85). This is enabled by using the ":set compatible" ex-command or by running Vim with the -C option.

== Tips ==

=== Learning ===
To learn [[vim]], [[open a console]] and call
[http://linuxcommand.org/man_pages/vimtutor1.html vimtutor]

==== A tutorial ====
While vim is not as easy to learn initially as it is to learn nano, there are plenty advantages to using it. Some great features of vim are copy, cut, and paste. Also there is code styling for programmers and there's also an undo/redo feature which is awesome.

There are three modes for vim (That I know of right now). There is the visual mode, insert mode, and the command mode. Before I start breaking down the different modes let me say this: every time you delete or copy text in the command or visual mode, the deleted text is loaded into a special buffer. This buffer continues to hold the text until you delete more text/characters/lines in which case the buffer will be replaced with the newly deleted text.

When you first open a file with command vim myfile you start out in the command mode. If the file myfile exists then it will load myfile into the editor. If the file myfile does not exist then it will create a blank file with myfile as its save path which can be modified but myfile will not be created on your hard drive until you save the document.

Pressing the i key will put the editor into insert mode. Go ahead and put the editor into insert mode and type some random text you can play with. In fact you should type a couple of lines.

Pressing the Esc while in insert mode will take the editor out of insert mode and back into command mode. Now each letter on your keyboard has turned into a command which manipulates the document instead of keys which insert text into the document.

Pressing the v key puts the editor into visual mode. Visual mode is used to highlight text in the document so you can apply different commands just to that text. If you accidentally go into visual mode or you've highlighted text and don't want to do anything to it then press the v key to go back into command mode.

While in command mode, pressing the colon key (: ) opens the editors command line where you can type a command for the editor to manipulate the whole document and not just some text or a few lines. For example in the editors command line you can save the document, quit the document, quit without saving, undo change, and redo change to name a few. You can even combine commands to do them at the same time such as save and quit at the same time.

That's most of the explanation behind it. Now remember the three modes: command, insert, and visual. Everything is centralized around the command mode. Also remember the editor command line which is accessed when in the command mode. Now that I've explained all that here is what happens when pressing different keys in the different modes.

When in command mode press the colon (: ) to enter the editor command line. Here are different editor commands.
command - explanation
{| border="1"
| :w
| write/save the document
|-
| :q
| quit vim
|-
| :q!
| quit vim without saving
|-
| :u
| undo
|-
| :r
| redo
|-
| :wq
| write/save the document and then quit vim
|}
If you accidentally enter the editor command line pressing Esc twice will put you back into command mode.

When you're in the command mode different keys have different functions. The commands are case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left
|-
| j
| move cursor down
|-
| k
| move cursor up
|-
| l
| move cursor right
|-
| w
| move the cursor right and down the document accross each word instead of each character.
|-
| ZZ
| same as :wq. write/save the document and then quit vim. Double tap the z key while holding the shift key (double click).
|-
| dd
| cuts/deletes an entire line of text. Double tab the d key (double click).
|-
| dw
| cuts/deletes a words of text
|-
| yy
| copies an entire line of text. Double tap the y key (double click).
|-
| p
| paste text after: if copied entire line then it will paste text after the current line. if copied a few characters then paste them after the current character.
|-
| P
| same as p but pastes text before the current character/line.
|-
| i
| enters editor into insert mode
|-
| o
| inserts a new line after the current line and then places the editor into insert mode.
|-
| v
| enters the editor into visual mode.
|-
| r
| replace. When you push a key after pressing r the letter the cursor is currently located on is replaced with the key pressed. You are still in command mode.
|-
| R
| replace. puts the editor into insert mode however it overwrites replacing each character if one already exists.
|-
| x
| delete a character
|}

When you're in insert mode every key on the keyboard types text into the document like a normal text editor. When you wish to leave insert mode press the Esc key.

When you're in the visual mode you can highlight text and apply different commands to it. The commands are similar to command mode and are also case sensitive.
{| border="1"
| command
| explanation
|-
| h
| move cursor left (highlighting text)
|-
| j
| move cursor down (highlighting text)
|-
| k
| move cursor up (highlighting text)
|-
| l
| move cursor right (highlighting text)
|-
| y
| copy the highlighted text and enter back into command mode
|-
| d
| cut/delete the hightlighted text and enter back into command mode
|-
| p
| paste the text from the buffer replacing the highlighted text.
|}

The following command opens myfile and automatically goes to line 23.
vim +23 myfile

It's a bit of a task remembering all those commands. The best way to learn them is to try to use vim regularly referring to those commands for the different modes. There's a lot more commands and tricks you can do in vim. Those are just the basic ones.

=== ~/.vimrc ===
To make a config file for vim, create a file in your home directory called .vimrc, and fill it with stuff that you'd normally type into vim's "ex" mode. For example, if you regularly do ":syntax on" from inside vim, put "syntax on" (no colon or quotes) on a line by itself in your ~/.vimrc file.

Here's the contents of a useful .vimrc file:
<pre>
syntax on
set number
set expandtab
set tabstop=4
set shiftwidth=4
set autoindent
</pre>

Where:
* "syntax on" turns on syntax highlighting
* "set number" turns on line numbers
* "set expandtab" makes vim insert spaces (instead of tabs) whenever you hit the tab key
* "set tabstop=4" sets tabs to equal 4 spaces
* "set shiftwidth=4" makes it so when you use the text shifting command, it shifts over using 4-space indents.
* "set autoindent" has vim use "smart indenting", ie. when you are tabbed out to, say, the 8th column, and you type something then hit enter, the cursor is helpfully placed at the 8th column again for you.

Additionally you can turn any single argument command off by adding an exclamation point (!). So "set number" can be turned off by "set number!"

(You can shut off line numbering from command mode by typing <tt>:set nonumber</tt>.)

=== Syntax highlighting ===

You can turn syntax highlighting on/off with:
:syntax off
:syntax on

If you have syntax highlighting on, but are using a dark background and the colors don't show up well, you can use this command:
:set background=dark

==External links==
*[http://www.vim.org Vim Homepage] (''www.vim.org'')
*[http://vi-improved.org/wiki/index.php #vim wiki] (''vi-improved.org'')

[[Category:Editors]]

Embed a zip file into a photo

2010-08-23T14:46:40Z

Sag47: Redirected page to Embed a zip file into an image

#REDIRECT [[Embed a zip file into an image]]

[[Category:Guides]]

Game List

2010-08-23T03:07:09Z

Sag47: /* FPS */

This page is to list games that run natively on [[GNU]]/[[Linux]], that means they don't require a emulator to run. See [[Gaming]] section for more info on gaming in Linux.

Click on the links for a better description of the game, and a link to its homepage. Some games are ports to GNU/Linux. There may also be games derived directly from other games, such games may or may not be listed on this page, but in their parent's page, ''[http://en.wikipedia.org/wiki/Doom_(series) Doom]'' for example has tons of ports, and derived games, many are not listed on this page, but the parent ''Doom'' is.

'''N.B:''' a virtual machine is not considered as an emulator. This implies that this game list includes games that ''may'' require a virtual machine to run under [[Linux]].

== Action/Arcade ==
Pretty much any game that wont fit anywhere else.
* [http://artax.karlin.mff.cuni.cz/~brain/0verkill/ 0verkill] - OSS
* [[Adventure]] - OSS
* [http://armagetron.sourceforge.net/ Armagetron] - OSS
: Everyone drives around and leaves a wall behind him. The others are not allowed to touch this wall.
* [http://atanks.sourceforge.net/ Atanks] - OSS
: Buy weapons for your tank, then use it to play against the computer or other players.
* [http://en.wikipedia.org/wiki/Bzflag BZFlag] - OSS
: A 3D multiplayer tank shooting game
* [http://ourawesomegames.com/pub/candydefense.jnlp Candy Defense] - $Binary
* [http://www.gagaplay.com/cosmictrip/cosmictrip.jnlp Cosmic Trip] - $Binary
* [http://www.reptilelabour.com/software/chromium/ Chromium] - OSS
* [http://criticalmass.sourceforge.net/critter.php Critter] - OSS
* [http://sourceforge.net/projects/gnukem/ Dave Gnukem] - OSS
* [http://www.newbreedsoftware.com/defendguin/ Defendguin] - OSS
: Shoot the monsters and protect the penguins.
* [http://www.nongnu.org/feuerkraft/ Feuerkraft] - OSS
* [http://freedroid.sourceforge.net/ Freedroid] - OSS
: Shoot the droids to rid their spaceship.
* [http://xhosxe.free.fr/glaxium/ Galaxium] - OSS
* [http://armagetron.sourceforge.net/ GLTron] - OSS
* [http://www.newbreedsoftware.com/icbm3d/ ICBM3D] - OSS
: Defend your nation against missiles.
* [http://www.ufoot.org/liquidwar/ LiquidWar] - OSS
: A multiplayer war game.
* [http://www.newbreedsoftware.com/madbomber/ Mad Bomber] - OSS
: Catch the bombs before they hit the ground.
* [http://www.devolution.com/~slouken/Maelstrom/index.html Maelstrom] - OSS
* [http://www.linux-games.com/penguin-command/ Penguin Command] - OSS
* [http://supertux.lethargik.org/ SuperTux] - OSS
: A classic 2D jump&run game. Your quest is to rescue Penny, a female penguin.
* [http://aluminumangel.org/attack/ Tux Kart] - OSS, a racing game geared towards kids
* [http://www.javagameplay.com/wz3.html Warzone 3] - $Binary
* [http://xmoto.tuxfamily.org/ XMoto] - OSS, a 2D motocross game where you traverse obstacles an solve puzzles.

== FPS ==
This is for ''First Person Shoot'' 'em ups (see [[FPS]]).
* [[America's Army]] - Binary
* [http://www.javagameplay.com/ancientarenas/medium.html Ancient Arenas] - $Binary
* [[Cube]] - OSS
* [http://en.wikipedia.org/wiki/Cold_War_%28video_game%29 Cold War] - $Binary, google "cold war linux" for sources to purchase
* [http://en.wikipedia.org/wiki/Doom_(series) Doom] - OSS
* [[Doom 3]] - $Binary
* [http://www.javagameplay.com/futuristicarenas/medium.html Futuristic Arenas] - $Binary
* [http://www.bytonic.de/downloads/jake2_jogl11.jnlp Jake 2] - OSS
* [http://www.nexuiz.com/ Nexuiz] - OSS
* [http://openparsec.sourceforge.net/ Parsec] - OSS
: [[Network]]-enabled space-based first-person-shooter.
* [http://www.gopostal.com/postal2/index.php Postal 2] - $Binary
* [http://icculus.org/prey/ Prey] - $Binary
* [[Quake]] - OSS/$
* [[Quake 3 Arena]] - $Binary
* [http://zerowing.idsoftware.com/linux/quake4/ Quake 4] - $Binary
* [[Return to Castle Wolfenstein]] - $Binary
* [http://icculus.org/rott/ Rise of the Traid] - OSS
: An oldish, but fun and hard FPS.
* [http://www.lokigames.com/products/rune/ Rune] - $Binary
: A third-person-perspective intense action game featuring nordic fantasy
* [http://www.pulpgames.net/scared/ Scared] - $Binary
* [http://www.croteam.com/ Serious Sam] - Binary
* [http://www.lokigames.com/products/sof/ Soldier of Fortune] - $Binary
: FPS for Linux
* [http://javagl.sourceforge.net/tesseract/index.html Tesseract] - Binary
* [http://en.wikipedia.org/wiki/Tribes_2 Tribes 2] - $Binary
* [http://www.truecombatelite.net/ True Combat: True Combat Elite] - Binary
* [http://tuer.sourceforge.net TUER] - OSS
* [[Unreal Tournament]] - $Binary
* [http://wolfgl.sourceforge.net/ Wolfenstein for Linux] - OSS.
* [http://www.enemy-territory.com/ Wolfenstein: Enemy Territory] - Binary

== Strategy ==
Strategy based games
* [http://www.firaxis.com/games/game_detail.php?gameid=7# Alpha Centauri] - $Binary
: Colonists settle on Alpha Centauri. The Linux version of this game is from Loki Games that is no more.
* [http://www.asc-hq.org/ ASC] - OSS
* [http://www.boswars.org/index.shtml BoS] - OSS
: A real-time strategy game
* [http://crimson.seul.org/ Crimson Fields] - OSS
: A turn-based war game played in 2D.
* [http://www.freeciv.org FreeCiv] - OSS
: Network-enabled turn-based game to build up your civilization, you will have to do research and lead wars.
* [http://www.freecol.org/ FreeCol] - OSS
: Colonization clone.
* [http://freelords.sourceforge.net FreeLords] - OSS
* [http://www.glest.org/en/index.html Glest] - OSS
: Fantasy/medieval theme
* [[Globulation 2]] - OSS
* [[Pingus]] - OSS
* [[Thousand Parsec]] - OSS
* [http://users.on.net/~bobjob/TD.jnlp Tower Defence Game] - $Binary
* [http://en.wikipedia.org/wiki/Tribal_Trouble Tribal Trouble] - $Binary
* [http://en.wikipedia.org/wiki/Warzone_2100 Warzone2100] - OSS
* [http://www.wesnoth.org/ Wesnoth] - OSS
: Turn-based single&multiplayer game set in a fantasy environment.
* [http://www.widelands.org Widelands] - OSS

== RPG ==
This section is for any type of ''Role Playing Game''
* [http://en.wikipedia.org/wiki/Angband_(video_game) Angband] - OSS
* [http://crossfire.real-time.com/ Crossfire] - OSS
* [http://web2.168180.vserver.de/ Daimonin] - OSS
: Play a fantasy hero who completes quests.
* [[Eternal Lands]] - OSS
* [[FreedroidRPG]] - OSS
* [http://www.illarion.org/ Illarion] - A free MMORPG that focusses on true roleplaying.
* [[Lincity]] - OSS
* [[Nethack]] - OSS
* [http://nwn.bioware.com/downloads/linuxclient.html Neverwinter Nights for Linux] - $Binary
* [http://www.openttd.com/ OpenTTD] - OSS/$
: Manage transports as in TransPort Tycoon.
* [http://www.planeshift.it/ PlaneShift] - OSS
: There are a lot of skills and no matter what role you choose, you can level up in them.
* [http://www.runescape.com Runescape] - $Binary
* [[Savage]] - $Binary
* [http://en.wikipedia.org/wiki/Simcity Simcity] - $Binary
: City building simulation
* [http://www.simutrans.de/ Simutrans] - Binary
* [http://vegastrike.sourceforge.net/ Vega Stike] - OSS
: Earn enough money to upgrade your ship, ... No network support.
* [http://www.wurmonline.com Wurm Online] - $Binary

== Puzzle/Educational/Board ==
This section encompasses games to make people think, or solve problems.
* [http://ccdw.org/~cjj/prog/ccgo/ ccGo] - OSS: Implementation of the board game Go
* [http://games.flowix.com/ Einstein] - OSS
* [[FooBillard]] - OSS - [[OpenGL]] billards
* [http://www.frozen-bubble.org/ Frozen bubble] - OSS
* [http://www.newbreedsoftware.com/gemdropx/ Gem Drop X] - OSS
* [http://glchess.sourceforge.net/ glChess] - OSS
* [http://lgames.sourceforge.net/index.php?project=LBreakout2 Lbreakout 2] - OSS
: Move a paddle at the bottom of your screen to bounce a ball to the top and destroy bricks.
* [http://kiki.sourceforge.net/ Kiki] - OSS
: 3D problem solving game
* [http://sam.zoy.org/monsterz/ Monsterz] - OSS
: Make rows and lines of similar looking monsters. Good for a quick game.
* [http://www.newbreedsoftware.com/pdamaze/ PDA Maze] - OSS
: Get past a 3D maze in a first person perspective.
* [[PyChess]] - OSS
* [http://www.tropiceuro.com Tropic Euro] - Binary
: An online adaptation of the board game Puerto Rico for 2-5 players.
* [http://tux4kids.alioth.debian.org/tuxmath/ TuxMath] - OSS
: Fight against bombs in the space - but the bombs are math problems and you fight them by solving.
* [http://2dboy.com/games.php World of Goo] - $Binary
* [http://www.tim-mann.org/xboard.html Xboard] - OSS

=== Tetris like ===

* [http://lgames.sourceforge.net/index.php?project=LTris Ltris] - OSS
* [http://aluminumangel.org/attack/ Crack Attack] - OSS
* [http://chaos2.org/xpuyopuyo/index.shtml XPuyopuyo] - OSS
* [http://www.dandeliongames.com/startup.jnlp 3D Breakout] - $Binary
* [http://www.freewebs.com/jeromeblouin/mygames.htm Incredibuilder!] - $Binary

== Simulation ==
Simulations are meant for teaching people about certain things, for example on how to operate machines, or demonstrate what-ifs.
* [[Core Wars]] - OSS
* [http://www.flightgear.org/ FlightGear] - OSS
* [http://downloads.sourceforge.net/project/freemind/freemind-unstable/0.9.0_RC6/freemind-bin-max-0.9.0_RC_6.zip?use_mirror=sunet YS Flight Simulation] - OSS
: Multiplayer flight simulator

== Other ==
* [[BSD games]] - OSS
* [http://hem.passagen.se/awl/ksokoban/ Anders Widell's Sokoban] - contained on [[knoppix]]

== See also ==
* [[gaMe]]
* [http://en.wikipedia.org/wiki/List_of_Linux_games List of Linux Games (wikipedia)] (''en.wikipedia.org'')
* [http://www.linuxsoft.cz/en/sw_list.php?id_kategory=23 Linux Game software] (''www.linuxsoft.cz'')
* [http://www.happypenguin.org The Linux Game Tome] (''www.happypenguin.org'')
* [http://www.javagametome.com The Java Game Tome] (''www.javagametome.com'')

[[Category:Game]]

Game List

2010-08-23T03:01:04Z

Sag47: /* Action/Arcade */

This page is to list games that run natively on [[GNU]]/[[Linux]], that means they don't require a emulator to run. See [[Gaming]] section for more info on gaming in Linux.

Click on the links for a better description of the game, and a link to its homepage. Some games are ports to GNU/Linux. There may also be games derived directly from other games, such games may or may not be listed on this page, but in their parent's page, ''[http://en.wikipedia.org/wiki/Doom_(series) Doom]'' for example has tons of ports, and derived games, many are not listed on this page, but the parent ''Doom'' is.

'''N.B:''' a virtual machine is not considered as an emulator. This implies that this game list includes games that ''may'' require a virtual machine to run under [[Linux]].

== Action/Arcade ==
Pretty much any game that wont fit anywhere else.
* [http://artax.karlin.mff.cuni.cz/~brain/0verkill/ 0verkill] - OSS
* [[Adventure]] - OSS
* [http://armagetron.sourceforge.net/ Armagetron] - OSS
: Everyone drives around and leaves a wall behind him. The others are not allowed to touch this wall.
* [http://atanks.sourceforge.net/ Atanks] - OSS
: Buy weapons for your tank, then use it to play against the computer or other players.
* [http://en.wikipedia.org/wiki/Bzflag BZFlag] - OSS
: A 3D multiplayer tank shooting game
* [http://ourawesomegames.com/pub/candydefense.jnlp Candy Defense] - $Binary
* [http://www.gagaplay.com/cosmictrip/cosmictrip.jnlp Cosmic Trip] - $Binary
* [http://www.reptilelabour.com/software/chromium/ Chromium] - OSS
* [http://criticalmass.sourceforge.net/critter.php Critter] - OSS
* [http://sourceforge.net/projects/gnukem/ Dave Gnukem] - OSS
* [http://www.newbreedsoftware.com/defendguin/ Defendguin] - OSS
: Shoot the monsters and protect the penguins.
* [http://www.nongnu.org/feuerkraft/ Feuerkraft] - OSS
* [http://freedroid.sourceforge.net/ Freedroid] - OSS
: Shoot the droids to rid their spaceship.
* [http://xhosxe.free.fr/glaxium/ Galaxium] - OSS
* [http://armagetron.sourceforge.net/ GLTron] - OSS
* [http://www.newbreedsoftware.com/icbm3d/ ICBM3D] - OSS
: Defend your nation against missiles.
* [http://www.ufoot.org/liquidwar/ LiquidWar] - OSS
: A multiplayer war game.
* [http://www.newbreedsoftware.com/madbomber/ Mad Bomber] - OSS
: Catch the bombs before they hit the ground.
* [http://www.devolution.com/~slouken/Maelstrom/index.html Maelstrom] - OSS
* [http://www.linux-games.com/penguin-command/ Penguin Command] - OSS
* [http://supertux.lethargik.org/ SuperTux] - OSS
: A classic 2D jump&run game. Your quest is to rescue Penny, a female penguin.
* [http://aluminumangel.org/attack/ Tux Kart] - OSS, a racing game geared towards kids
* [http://www.javagameplay.com/wz3.html Warzone 3] - $Binary
* [http://xmoto.tuxfamily.org/ XMoto] - OSS, a 2D motocross game where you traverse obstacles an solve puzzles.

== FPS ==
This is for ''First Person Shoot'' 'em ups (see [[FPS]]).
* [[America's Army]] - Binary
* [http://www.javagameplay.com/ancientarenas/medium.html Ancient Arenas] - $Binary
* [[Cube]] - OSS
* [http://en.wikipedia.org/wiki/Doom_(series) Doom] - OSS
* [[Doom 3]] - $Binary
* [http://www.javagameplay.com/futuristicarenas/medium.html Futuristic Arenas] - $Binary
* [http://www.bytonic.de/downloads/jake2_jogl11.jnlp Jake 2] - OSS
* [http://www.nexuiz.com/ Nexuiz] - OSS
* [http://openparsec.sourceforge.net/ Parsec] - OSS
: [[Network]]-enabled space-based first-person-shooter.
* [http://www.gopostal.com/postal2/index.php Postal 2] - $Binary
* [[Quake]] - OSS/$
* [[Quake 3 Arena]] - $Binary
* [[Return to Castle Wolfenstein]] - $Binary
* [http://icculus.org/rott/ Rise of the Traid] - OSS
: An oldish, but fun and hard FPS.
* [http://www.lokigames.com/products/rune/ Rune] - $Binary
: A third-person-perspective intense action game featuring nordic fantasy
* [http://www.pulpgames.net/scared/ Scared] - $Binary
* [http://www.croteam.com/ Serious Sam] - Binary
* [http://www.lokigames.com/products/sof/ Soldier of Fortune] - $Binary
: FPS for Linux
* [http://javagl.sourceforge.net/tesseract/index.html Tesseract] - Binary
* [http://en.wikipedia.org/wiki/Tribes_2 Tribes 2] - $Binary
* [http://www.truecombatelite.net/ True Combat: True Combat Elite] - Binary
* [http://tuer.sourceforge.net TUER] - OSS
* [[Unreal Tournament]] - $Binary
* [http://wolfgl.sourceforge.net/ Wolfenstein for Linux] - OSS.
* [http://www.enemy-territory.com/ Wolfenstein: Enemy Territory] - Binary

== Strategy ==
Strategy based games
* [http://www.firaxis.com/games/game_detail.php?gameid=7# Alpha Centauri] - $Binary
: Colonists settle on Alpha Centauri. The Linux version of this game is from Loki Games that is no more.
* [http://www.asc-hq.org/ ASC] - OSS
* [http://www.boswars.org/index.shtml BoS] - OSS
: A real-time strategy game
* [http://crimson.seul.org/ Crimson Fields] - OSS
: A turn-based war game played in 2D.
* [http://www.freeciv.org FreeCiv] - OSS
: Network-enabled turn-based game to build up your civilization, you will have to do research and lead wars.
* [http://www.freecol.org/ FreeCol] - OSS
: Colonization clone.
* [http://freelords.sourceforge.net FreeLords] - OSS
* [http://www.glest.org/en/index.html Glest] - OSS
: Fantasy/medieval theme
* [[Globulation 2]] - OSS
* [[Pingus]] - OSS
* [[Thousand Parsec]] - OSS
* [http://users.on.net/~bobjob/TD.jnlp Tower Defence Game] - $Binary
* [http://en.wikipedia.org/wiki/Tribal_Trouble Tribal Trouble] - $Binary
* [http://en.wikipedia.org/wiki/Warzone_2100 Warzone2100] - OSS
* [http://www.wesnoth.org/ Wesnoth] - OSS
: Turn-based single&multiplayer game set in a fantasy environment.
* [http://www.widelands.org Widelands] - OSS

== RPG ==
This section is for any type of ''Role Playing Game''
* [http://en.wikipedia.org/wiki/Angband_(video_game) Angband] - OSS
* [http://crossfire.real-time.com/ Crossfire] - OSS
* [http://web2.168180.vserver.de/ Daimonin] - OSS
: Play a fantasy hero who completes quests.
* [[Eternal Lands]] - OSS
* [[FreedroidRPG]] - OSS
* [http://www.illarion.org/ Illarion] - A free MMORPG that focusses on true roleplaying.
* [[Lincity]] - OSS
* [[Nethack]] - OSS
* [http://nwn.bioware.com/downloads/linuxclient.html Neverwinter Nights for Linux] - $Binary
* [http://www.openttd.com/ OpenTTD] - OSS/$
: Manage transports as in TransPort Tycoon.
* [http://www.planeshift.it/ PlaneShift] - OSS
: There are a lot of skills and no matter what role you choose, you can level up in them.
* [http://www.runescape.com Runescape] - $Binary
* [[Savage]] - $Binary
* [http://en.wikipedia.org/wiki/Simcity Simcity] - $Binary
: City building simulation
* [http://www.simutrans.de/ Simutrans] - Binary
* [http://vegastrike.sourceforge.net/ Vega Stike] - OSS
: Earn enough money to upgrade your ship, ... No network support.
* [http://www.wurmonline.com Wurm Online] - $Binary

== Puzzle/Educational/Board ==
This section encompasses games to make people think, or solve problems.
* [http://ccdw.org/~cjj/prog/ccgo/ ccGo] - OSS: Implementation of the board game Go
* [http://games.flowix.com/ Einstein] - OSS
* [[FooBillard]] - OSS - [[OpenGL]] billards
* [http://www.frozen-bubble.org/ Frozen bubble] - OSS
* [http://www.newbreedsoftware.com/gemdropx/ Gem Drop X] - OSS
* [http://glchess.sourceforge.net/ glChess] - OSS
* [http://lgames.sourceforge.net/index.php?project=LBreakout2 Lbreakout 2] - OSS
: Move a paddle at the bottom of your screen to bounce a ball to the top and destroy bricks.
* [http://kiki.sourceforge.net/ Kiki] - OSS
: 3D problem solving game
* [http://sam.zoy.org/monsterz/ Monsterz] - OSS
: Make rows and lines of similar looking monsters. Good for a quick game.
* [http://www.newbreedsoftware.com/pdamaze/ PDA Maze] - OSS
: Get past a 3D maze in a first person perspective.
* [[PyChess]] - OSS
* [http://www.tropiceuro.com Tropic Euro] - Binary
: An online adaptation of the board game Puerto Rico for 2-5 players.
* [http://tux4kids.alioth.debian.org/tuxmath/ TuxMath] - OSS
: Fight against bombs in the space - but the bombs are math problems and you fight them by solving.
* [http://2dboy.com/games.php World of Goo] - $Binary
* [http://www.tim-mann.org/xboard.html Xboard] - OSS

=== Tetris like ===

* [http://lgames.sourceforge.net/index.php?project=LTris Ltris] - OSS
* [http://aluminumangel.org/attack/ Crack Attack] - OSS
* [http://chaos2.org/xpuyopuyo/index.shtml XPuyopuyo] - OSS
* [http://www.dandeliongames.com/startup.jnlp 3D Breakout] - $Binary
* [http://www.freewebs.com/jeromeblouin/mygames.htm Incredibuilder!] - $Binary

== Simulation ==
Simulations are meant for teaching people about certain things, for example on how to operate machines, or demonstrate what-ifs.
* [[Core Wars]] - OSS
* [http://www.flightgear.org/ FlightGear] - OSS
* [http://downloads.sourceforge.net/project/freemind/freemind-unstable/0.9.0_RC6/freemind-bin-max-0.9.0_RC_6.zip?use_mirror=sunet YS Flight Simulation] - OSS
: Multiplayer flight simulator

== Other ==
* [[BSD games]] - OSS
* [http://hem.passagen.se/awl/ksokoban/ Anders Widell's Sokoban] - contained on [[knoppix]]

== See also ==
* [[gaMe]]
* [http://en.wikipedia.org/wiki/List_of_Linux_games List of Linux Games (wikipedia)] (''en.wikipedia.org'')
* [http://www.linuxsoft.cz/en/sw_list.php?id_kategory=23 Linux Game software] (''www.linuxsoft.cz'')
* [http://www.happypenguin.org The Linux Game Tome] (''www.happypenguin.org'')
* [http://www.javagametome.com The Java Game Tome] (''www.javagametome.com'')

[[Category:Game]]

Blender

2010-08-22T11:47:20Z

Sag47:

'''Blender''' is a [[3D modeling]] application available for Linux, Windows, and Macintosh. It is a powerful, professional 3D environment, but it has a steep learning curve, and many sometimes obscure shortcut keys. It currently supports animation rendering, radiosity, particle systems, and [[OpenGL]] Realtime animation for some (but not all) platforms/OSs. Blender is an interesting program because it was originally a commercial, closed source program. The company that made it went bust, and the code was released as open source for a fee to the creditors. That fee was paid and so the once closed source program became open source.

Learning how to use Blender can be tough, but it's worth it. A good place to start is the Using Blender section of [http://www.blender3d.org Blender3d.org]. From the homepage, go to InfoCenter -> Using Blender.

Blender has a built-in python [[interpreter]] and [http://en.wikipedia.org/wiki/API API] for 3D object manipulation. Along with the built-in script library, there are many community-created scripts and tutorials for creating your own scripts.

In 2006, an 'open' video made entirely by blender was released called [http://orange.blender.org/ Elephants Dream]. This was made under the Creative Commons license which allows anyone to use it to make their own movies as long as they say they used Elephants Dream.

== List of 3D movies created by Blender ==
* [http://www.bigbuckbunny.org/ Big Buck Bunny], watch the [http://www.bigbuckbunny.org/index.php/trailer-page/ trailer] and/or the [http://www.bigbuckbunny.org/index.php/download/ whole thing].
* [http://orange.blender.org/ Elephants Dream], watch the [http://orange.blender.org/download whole thing].
* [http://durian.blender.org/ Sintel], watch the [http://durian.blender.org/download/ trailer]. This movie is currently in production and about to be released.
== External links ==
* [http://www.blender3d.org Blender3d.org] (''www.blender3d.org'')
* [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro Noob to Pro, wikibooks] (''en.wikibooks.org'')
* [http://www.elysiun.com/ elYsiun.com] (''www.elysiun.com'')
*: ''the'' Blender forum and community site.

''This article is a [[LQWiki:stub_articles|stub]] and needs to be finished. [[LQWiki:plunging_forward|Plunge forward]] and [[LQWiki:How_to_edit_a_page|help it grow]]!''

3D modeling

2010-08-22T11:32:51Z

Sag47:

'''3D modeling''' software is used to create 3D images, animations, simualtions, crash tests etc.

{|
| [[Blender]] ||
Powerful modeling environment
|-
| [[K-3D]] ||
Integrated 3D modeler/animation/rendering system
|-
| [[PovRay]] ||
Renders scenes from C++ style text files (ray tracing, offline rendering)
|-
| SharpConstruct ||
Interactive sculpting program
|-
| [[Wings 3d]] ||
Polygon modeler
|-
| Cinema 4D ||
A very good 3D modeler, easy to use.
|-
| 3Ds MAX ||
3D studio MAX is a very poverfull 3D program. It uses lots of defferet renderers
|-
| MAYA ||
The best 3D program on the market, and probably the toughest to learn.
|-
| [http://www.newtek.com/lightwave/ Lightwave 3D] ||
|-
|}

{{stub}}

User:Sag47

2010-08-22T05:19:33Z

Sag47: /* My Professional Certifications */

= My =

[http://www.gleske.net/ My website]

[[Special:Contributions/Sag47|My Contributions]]

[http://sourceforge.net/users/sag47 My Sourceforge]

[http://www.ece.drexel.edu/ My Passion]

[http://notepad-plus-plus.org/ My favorite IDE]

= My Operating Systems =
* Windows (all editions from Dos and 3.1 all the way up to Windows 7)
* Linux (many distros, once you know your way around the terminal any distro becomes more easy) [http://www.linuxfromscratch.org/ Linux From Scratch] was my most challenging.
* FreeBSD
* Mac OS (the NeXT version. I don't have any experience with OS 9)

Ordered by frequency of use.

= My Languages =
* AutoCAD
* AJAX
* Assembly (MIPs and Pentium)
* C++
* C#
* C
* CSS
* CVS
* Cypress PSoC 3/PSoC Designer
* DHTML
* HTML
* Java
* JavaScript
* Labview
* Linux Shell
* Maple
* Matlab
* MySQL
* Neuron C
* NSIS
* PHP
* Python
* Subversion
* UPMACS
* VHDL
* Windows Batch/INI/CSV
* XHTML
* XML
= My Life in meatspace =
Gun shooting (pistol, skeet, rifle, you name it and I love it), scuba diving, sailing (15 yrs), motocross racing and fourwheeling (trucks and quads) (8 yrs), microprocessor design, wake boarding, snow boarding (18 yrs), skiing (19 yrs), repelling, caving, jetski riding (this one is recent and a blast), roller hockey, cycling, riding motorcycles, driving manual cars, going out dancing, studying and reading on subjects of interest (which include everything), and tons more which I can't think of off the top of my head. That's all stuff I try to do as often as possible. My list would be bigger if I was rich and had unlimited time. All of it is in no particular order. I have a passion for most of what I do and try to learn it to a professional level.

= My Professional Certifications =
* BS Electrical and Computer Engineering Dual Major, anticipated and in progress
* CompTIA A+ Certification, 2004
* CompTIA Network+ Certification, 2005
* PADI Open Water SCUBA, 2010
* PADI Advanced Open Water SCUBA, 2010
* PADI Enriched Air Nitrox (EANx), 2010

= My Plans =
Most people say I would do well as a computer science major. But that is just a hobby and Linux is something I enjoy participating in my free time.

As a professional I want to design microprocessors and so Engineering is the path I chose. I may master in something like Biomedical Engineering in the future but that is far off and only because I feel processors of the future will contain biological components since we are reaching the limits to the size of atoms with processors in modern day for electrical paths. Now instead of decreasing size and increasing speed (Hz) they are adding cores and improving CPI (cycles per instruction) time with lowered cycle rates. It won't be long before our electronics depend on chemical signals for processing much like our brain depends on.

This is the future I see and want to be a part of. I have many other plans but those are secret ;)

User:Sag47

2010-08-22T05:17:59Z

Sag47: /* My Operating Systems */

= My =

[http://www.gleske.net/ My website]

[[Special:Contributions/Sag47|My Contributions]]

[http://sourceforge.net/users/sag47 My Sourceforge]

[http://www.ece.drexel.edu/ My Passion]

[http://notepad-plus-plus.org/ My favorite IDE]

= My Operating Systems =
* Windows (all editions from Dos and 3.1 all the way up to Windows 7)
* Linux (many distros, once you know your way around the terminal any distro becomes more easy) [http://www.linuxfromscratch.org/ Linux From Scratch] was my most challenging.
* FreeBSD
* Mac OS (the NeXT version. I don't have any experience with OS 9)

Ordered by frequency of use.

= My Languages =
* AutoCAD
* AJAX
* Assembly (MIPs and Pentium)
* C++
* C#
* C
* CSS
* CVS
* Cypress PSoC 3/PSoC Designer
* DHTML
* HTML
* Java
* JavaScript
* Labview
* Linux Shell
* Maple
* Matlab
* MySQL
* Neuron C
* NSIS
* PHP
* Python
* Subversion
* UPMACS
* VHDL
* Windows Batch/INI/CSV
* XHTML
* XML
= My Life in meatspace =
Gun shooting (pistol, skeet, rifle, you name it and I love it), scuba diving, sailing (15 yrs), motocross racing and fourwheeling (trucks and quads) (8 yrs), microprocessor design, wake boarding, snow boarding (18 yrs), skiing (19 yrs), repelling, caving, jetski riding (this one is recent and a blast), roller hockey, cycling, riding motorcycles, driving manual cars, going out dancing, studying and reading on subjects of interest (which include everything), and tons more which I can't think of off the top of my head. That's all stuff I try to do as often as possible. My list would be bigger if I was rich and had unlimited time. All of it is in no particular order. I have a passion for most of what I do and try to learn it to a professional level.

= My Professional Certifications =
* BS Electrical and Computer Engineering Dual Major, anticipated and in progress
* CompTIA A+ Certification, 2004
* CompTIA Network+ Certification, 2005
* PADI Open Water SCUBA, 2010
* PADI Advanced Open Water SCUBA, 2010
* PADI Entriched Air Nitrox (EANx), 2010

= My Plans =
Most people say I would do well as a computer science major. But that is just a hobby and Linux is something I enjoy participating in my free time.

As a professional I want to design microprocessors and so Engineering is the path I chose. I may master in something like Biomedical Engineering in the future but that is far off and only because I feel processors of the future will contain biological components since we are reaching the limits to the size of atoms with processors in modern day for electrical paths. Now instead of decreasing size and increasing speed (Hz) they are adding cores and improving CPI (cycles per instruction) time with lowered cycle rates. It won't be long before our electronics depend on chemical signals for processing much like our brain depends on.

This is the future I see and want to be a part of. I have many other plans but those are secret ;)

Set up FTP server

2010-08-22T05:06:04Z

Sag47:

{{PageAuthor|Sag47}}
This covers how to get an [[FTP server]] for [[networks]] to work under Linux, and various information about other servers and applications which go along with them.

= FTP Server: proftpd instructions =
== Assumptions ==
I'm going to make a few assumptions:
* You have [[apache]]2 already installed (and maybe php5/mysql-server-5.1/mysql-client-5.1 but not required)
* You have a new to intermediate level of terminal knowledge (basics such as cd dirs and whatnot)
* Your apache web user is www-data like mine is (cat /etc/passwd | grep www)
* You are running all commands as root. Emulate a root login by typing "sudo bash" so you don't have to type the stupid sudo command a bunch.

== Install proftpd ==
'''Okay lets get started with FTP!'''
Install proftpd. If asked about running from inetd or standalone then choose standalone.

Debian/Ubuntu based install command.
sudo apt-get install proftpd

You can stop, start, get the status, and more from the following command.
/etc/init.d/proftpd
# start server
/etc/init.d/proftpd start
# stop server
/etc/init.d/proftpd stop

Since proftpd is located in /etc/init.d/ it will autostart when the system starts up.

== Setup proftp to use system users ==
For the server and port settings you need to modify proftpd.conf which is located in /etc/ or /etc/proftpd/. Lets pretend we don't know where it is at all and search for it.
cd /
#Here's two ways to find it
find . -type f -name "proftpd.conf"
find . | grep proftpd.conf

Modify your proftpd.conf and change any port settings or anonymous logins you wish and restart the server....
vim /etc/proftpd/proftpd.conf

You should uncomment the following lines in proftpd.conf
#if your machine is IPv4 only
UseIPv6 off
#jail all users in their homes
DefaultRoot ~
#user does not require a valid shell to login
RequireValidShell off

#at the end of the file add the following...

# Allow users from a group to login
MaxLoginAttempts 5
<Limit LOGIN>
AllowGroup ftpusers
DenyALL
</Limit>

Create an ftpusers group so that any user in the ftpusers group can login to their home via ftp.
groupadd ftpusers

== Give existing users FTP access ==
Add any existing users you wish to have ftp access to the ftpusers group.
#my username is sam and I'm going to add myself
usermod -a -G ftpusers sam

#check to ensure the user was added to group
groups sam

== Set up your user webadmin to upload files to /var/www ==
Create your webadmin user (without a shell login) so that they may only login using ftp. Set their home to /var/www.
#setup user webadmin
useradd webadmin -d /var/www -s /bin/false

#set password for webadmin
passwd webadmin

Add the user webadmin to the ftpusers group and give webadmin ownership to /var/www.
usermod -a -G ftpusers webadmin
chown -R webadmin\: /var/www
chmod -R 755 /var/www
groups webadmin

#check the ownership and permissions of /var/www
ls -lah /var | grep www

Alternatively if you're using the PHP copy function you'll want to give ownership of /var/www to www-data (the apache user) and allow webadmin to modify the files and folders within.
usermod -a -G www-data webadmin
chown -R www-data\: /var/www
chmod -R 775 /var/www
groups webadmin
ls -lah /var | grep www

== Troubleshooting proftpd==
#check to see if proftpd is running
/etc/init.d/proftpd status
#if it is not running then check for processes using port 21
netstat -anp | grep 21
#use the kill command to kill a process based on it's PID and retry

== Documentation Sources ==
http://www.proftpd.org/ - website

http://www.proftpd.org/docs/ - documentation

http://www.proftpd.org/docs/howto/Limit.html - Limits section in proftpd.conf

= FTP Clients =
Here is a comprehensive list of FTP Clients available to distros which users may have on your network.
{| border="1" class="wikitable sortable" style="font-size: 90%; text-align: center; width: auto;"
! {{Rh}} | Name
! {{Rh}} | Linux
! {{Rh}} | Mac OS X
! {{Rh}} | Windows
! {{Rh}} | Other
|-
! {{Rh}} |[http://www.crossftp.com/ CrossFTP]
|Y
|Y
|Y
|Y
|-
! {{Rh}} |[http://filezilla-project.org/download.php?type=client FileZilla FTP Client]
|Y
|Y
|Y
|Y
|-
! {{Rh}} |[http://portableapps.com/apps/internet/filezilla_portable FileZilla Portable]
|N
|N
|Y
|N
|-
! {{Rh}} |[[FireFTP]]
|Y
|Y
|Y
|Y
|-
! {{Rh}} |[[Kasablanca]]
|Y
|N
|N
|N
|-
! {{Rh}} |[[KBear]]
|Y
|N
|N
|N
|-
! {{Rh}} |[[Nautilus]]
|Y
|N
|N
|N
|-
! {{Rh}} |[http://winscp.net/eng/index.php WinSCP]
|N
|N
|Y
|N
|-
! {{Rh}} |[http://portableapps.com/apps/internet/winscp_portable WinSCP Portable]
|N
|N
|Y
|N
|}

= See also =
* [[Linux software equivalent to Windows software]]
* [[apAche]]
* [[fTp]]
* [[ftp Server]]

[[Category:Networking]]

User:Sag47

2010-08-22T04:37:47Z

Sag47: /* My */

= My =

[http://www.gleske.net/ My website]

[[Special:Contributions/Sag47|My Contributions]]

[http://sourceforge.net/users/sag47 My Sourceforge]

[http://www.ece.drexel.edu/ My Passion]

[http://notepad-plus-plus.org/ My favorite IDE]

= My Operating Systems =
* Windows (all editions from Dos and 3.1 all the way up to Windows 7)
* Linux (many distros, once you know your way around the terminal any distro becomes more easy) [http://www.linuxfromscratch.org/ Linux From Scratch] was my most challenging.
* FreeBSD
* Mac OS (the NeXT version. I don't have any experience with OS 9)

= My Languages =
* AutoCAD
* AJAX
* Assembly (MIPs and Pentium)
* C++
* C#
* C
* CSS
* CVS
* Cypress PSoC 3/PSoC Designer
* DHTML
* HTML
* Java
* JavaScript
* Labview
* Linux Shell
* Maple
* Matlab
* MySQL
* Neuron C
* NSIS
* PHP
* Python
* Subversion
* UPMACS
* VHDL
* Windows Batch/INI/CSV
* XHTML
* XML
= My Life in meatspace =
Gun shooting (pistol, skeet, rifle, you name it and I love it), scuba diving, sailing (15 yrs), motocross racing and fourwheeling (trucks and quads) (8 yrs), microprocessor design, wake boarding, snow boarding (18 yrs), skiing (19 yrs), repelling, caving, jetski riding (this one is recent and a blast), roller hockey, cycling, riding motorcycles, driving manual cars, going out dancing, studying and reading on subjects of interest (which include everything), and tons more which I can't think of off the top of my head. That's all stuff I try to do as often as possible. My list would be bigger if I was rich and had unlimited time. All of it is in no particular order. I have a passion for most of what I do and try to learn it to a professional level.

= My Professional Certifications =
* BS Electrical and Computer Engineering Dual Major, anticipated and in progress
* CompTIA A+ Certification, 2004
* CompTIA Network+ Certification, 2005
* PADI Open Water SCUBA, 2010
* PADI Advanced Open Water SCUBA, 2010
* PADI Entriched Air Nitrox (EANx), 2010

= My Plans =
Most people say I would do well as a computer science major. But that is just a hobby and Linux is something I enjoy participating in my free time.

As a professional I want to design microprocessors and so Engineering is the path I chose. I may master in something like Biomedical Engineering in the future but that is far off and only because I feel processors of the future will contain biological components since we are reaching the limits to the size of atoms with processors in modern day for electrical paths. Now instead of decreasing size and increasing speed (Hz) they are adding cores and improving CPI (cycles per instruction) time with lowered cycle rates. It won't be long before our electronics depend on chemical signals for processing much like our brain depends on.

This is the future I see and want to be a part of. I have many other plans but those are secret ;)

Embed a zip file into an image

2010-08-22T04:31:52Z

Sag47: /* About */

{{PageAuthor|Sag47}}
This is for intermediate users of computers but I'll slim it down so basic users can benefit from this tutorial as well.

= About =
First lets go over some basic terminology.

''[[Encryption]]'' is a way to secure your files and scramble your data so that no one can read it but you. If you are interested in using encryption then I suggest [http://www.truecrypt.org/ TrueCrypt] which is free/open source and for Windows, Linux, and MAC.

''[http://en.wikipedia.org/wiki/Steganography Steganography]'' is the art and science of writing hidden messages in such a way that no one apart from the sender and intended recipient even realizes there is a hidden message.

So basically steganography is, in a way, more clever and effective at hiding data than encryption because it looks like something else.

An example would be a folder full of family images. One of those images is embedded with a zip file but to a would-be villain it still looks like a folder of images. Only you know which image has the zip file so nothing looks suspicious.

Probably the most effective way of securing/hiding your information is combining Encryption with Stenography. So if my data was truly sensitive that I would require encryption and it needed to be transported then I would put my encrypted file within a zip file and combine it with an image to lower suspicion.

Are you interested yet? Well I'll stop beating around the bush and tell you how to do it! This requires that you have previous knowledge of what an image is and how to zip your files.

= How to do it =
== in Linux ==
cat MyImage.png MyZipFile.zip >> output.png
For more information about the cat command type "man cat" in the terminal. You may zip your files using the zip utility.
zip MyZipFile.zip myfile.txt
zip -r MyZipFile.zip myfolder/

== in Mac ==
Open the terminal from utilities and run the same command as you would in Linux. Google for "man cat" for more information on the cat command.

== in Windows ==
When I say type Ctrl+C it means to hold your Ctrl key down on the keyboard and, with Ctrl still held down, type the C key and then release both keys.

Open your command prompt: Type [Window Key]+R
In the run dialog type "cmd" without quotes. And press enter.

Now you must know where your image and zip file are located on your computer. Mine just so happens to be on the desktop and so that is what this command sequence is for. I already have an image called MyImage.png and a zip file called MyZipFile.zip located on my desktop.
C:\Users\User> cd Desktop

C:\Users\User\Desktop> '''''copy /b MyImage.png + MyZipFile.zip output.png'''''
input.png
comp.zip
1 file(s) copied.

C:\Users\User\Desktop>

If you notice that in "MyImage.png + MyZipFile.zip" the image goes before the zip file and there is a plus (+) symbol in between the two files.

= How to open it =
Ok, so what use is a zip file if you can't open it because it is an image? Well that problem is solved easily enough.
== in Linux and Mac ==
You just have to rename the image with a .zip extension to be able to unzip it.
mv output.png output.zip
unzip output.zip

== in Windows ==
Open a folder, any folder and click on ''Tools > Folder Options...'' (if you are using Windows Vista/7 then you must press the Alt key and then the menu will show up so you can click Tools). Click on the View tab and scroll down and uncheck "Hide extensions for known file types". You can now close that folder and look at your desktop. You will notice that everything has an extension now.

Simply right click on output.png (which is the image/zip file you created in this tutorial) and select rename. Change .png to .zip and now it can be opened as a zip file.

= Warnings and Notices =
* ''NOTE: If you are using Windows XP/2000 then your command line will look a little different but the commands are the same.''
* Once you create this image/zip file then the zip file can't be changed (even if you really want to add more files it won't) so every time you want to add/remove files from your image/zip file then you will have to recreate it from a new image and zip file.
* '''DO NOT EDIT''' your image/zip file with an image editor such as GIMP, Photoshop, or MS Paint. Those programs don't know what a zip file looks like so when you save any changes to the image it will destroy the zip file and only the image will be left behind.
* Remember that images aren't very big so if you combine a 500MB zip file with an image then the image will be 500MB. To me this would be a suspicious file if I was an attacker so I would look into it. There are better ways of hiding larger files from attackers and steganography is only one of many.

= See also =
* [[Cryptography commands]]
* [[Encryption]]
* [[Encrypt a disk]]
* [[Security]]
* [http://www.truecrypt.org/ TrueCrypt homepage]
* [http://en.wikipedia.org/wiki/Encryption Wikipedia on Encryption]
* [http://en.wikipedia.org/wiki/Steganography Wikipedia on Steganography]

[[Category:Guides]]

Embed a zip file into an image

2010-08-22T04:29:49Z

Sag47: /* See also */

{{PageAuthor|Sag47}}
This is for intermediate users of computers but I'll slim it down so basic users can benefit from this tutorial as well.

= About =
First lets go over some basic terminology.

''[[Encryption]]'' is a way to secure your files and scramble your data so that no one can read it but you. If you are interested in using encryption then I suggest [http://www.truecrypt.org/ TrueCrypt] which is free/open source and for Windows, Linux, and MAC.

''[http://en.wikipedia.org/wiki/Steganography Steganography]'' is the art and science of writing hidden messages in such a way that no one apart from the sender and intended recipient even realizes there is a hidden message.

So basically steganography is, in a way, more clever and effective at hiding data than encryption because it looks like something else. An example would be a folder full of family images, and one of those images is embedded with a zip file but to a would-be villain still looks like a folder of images. Only you know which image has the zip file so nothing looks suspicious.

Probably the most effective way of securing/hiding your information is combining Encryption with Stenography. So if my data was truly sensitive that I would require encryption and it needed to be transported then I would put my encrypted file within a zip file and combine it with an image to lower suspicion.

Are you interested yet? Well I'll stop beating around the bush and tell you how to do it! This requires that you have previous knowledge of what an image is and how to zip your files.

= How to do it =
== in Linux ==
cat MyImage.png MyZipFile.zip >> output.png
For more information about the cat command type "man cat" in the terminal. You may zip your files using the zip utility.
zip MyZipFile.zip myfile.txt
zip -r MyZipFile.zip myfolder/

== in Mac ==
Open the terminal from utilities and run the same command as you would in Linux. Google for "man cat" for more information on the cat command.

== in Windows ==
When I say type Ctrl+C it means to hold your Ctrl key down on the keyboard and, with Ctrl still held down, type the C key and then release both keys.

Open your command prompt: Type [Window Key]+R
In the run dialog type "cmd" without quotes. And press enter.

Now you must know where your image and zip file are located on your computer. Mine just so happens to be on the desktop and so that is what this command sequence is for. I already have an image called MyImage.png and a zip file called MyZipFile.zip located on my desktop.
C:\Users\User> cd Desktop

C:\Users\User\Desktop> '''''copy /b MyImage.png + MyZipFile.zip output.png'''''
input.png
comp.zip
1 file(s) copied.

C:\Users\User\Desktop>

If you notice that in "MyImage.png + MyZipFile.zip" the image goes before the zip file and there is a plus (+) symbol in between the two files.

= How to open it =
Ok, so what use is a zip file if you can't open it because it is an image? Well that problem is solved easily enough.
== in Linux and Mac ==
You just have to rename the image with a .zip extension to be able to unzip it.
mv output.png output.zip
unzip output.zip

== in Windows ==
Open a folder, any folder and click on ''Tools > Folder Options...'' (if you are using Windows Vista/7 then you must press the Alt key and then the menu will show up so you can click Tools). Click on the View tab and scroll down and uncheck "Hide extensions for known file types". You can now close that folder and look at your desktop. You will notice that everything has an extension now.

Simply right click on output.png (which is the image/zip file you created in this tutorial) and select rename. Change .png to .zip and now it can be opened as a zip file.

= Warnings and Notices =
* ''NOTE: If you are using Windows XP/2000 then your command line will look a little different but the commands are the same.''
* Once you create this image/zip file then the zip file can't be changed (even if you really want to add more files it won't) so every time you want to add/remove files from your image/zip file then you will have to recreate it from a new image and zip file.
* '''DO NOT EDIT''' your image/zip file with an image editor such as GIMP, Photoshop, or MS Paint. Those programs don't know what a zip file looks like so when you save any changes to the image it will destroy the zip file and only the image will be left behind.
* Remember that images aren't very big so if you combine a 500MB zip file with an image then the image will be 500MB. To me this would be a suspicious file if I was an attacker so I would look into it. There are better ways of hiding larger files from attackers and steganography is only one of many.

= See also =
* [[Cryptography commands]]
* [[Encryption]]
* [[Encrypt a disk]]
* [[Security]]
* [http://www.truecrypt.org/ TrueCrypt homepage]
* [http://en.wikipedia.org/wiki/Encryption Wikipedia on Encryption]
* [http://en.wikipedia.org/wiki/Steganography Wikipedia on Steganography]

[[Category:Guides]]

Howto

2010-08-22T04:26:48Z

Sag47: /* Disk and archive manipulation */

A '''Howto''', '''Tutorial''' or '''Guide''' is a ''documentation for accomplishing tasks''. If you wish to find a listing of all howtos on this wiki, look at the [[:Category:Guides|Category Guides]].

Here is a selection:

= Introducing Linux =
* [[Choose a Linux distribution]]
* [[Interoperability]]
** [[Run Windows software]]
** [[Share files with Windows]]
** [[Install Windows fonts]]
** [[Beginner's Command Line]] - migrating from windows to the linux command line
= Disk and archive manipulation =
* [[Clone a disk using dd]]
* [[Configure storage devices]]
* [[Create software RAID and volume groups]]
* [[Embed a zip file into an image]]
* [[Make a USB disk bootable]]
* [[Make backups]]
* [[Encrypt a disk]]
* [[Pack and unpack files]]

= Setup and Office =
* [[Creating startup scripts]]
* Do [[Office tasks]] - word processing, spreadsheet, presentation, image manipulation and other
* [[Install Software]]
* [[Print]]
* [[Scan]]
* [[Schedule Tasks]]
* [[Set up lm sensors]] - for monitoring CPU/Motherboard temperature, fan speeds, voltage information, etc.
* [[Browsing tasks|Surf the web]] / [[Connect to the net]]
= Fun Stuff =
* [[Burn a CDROM]]
* Play [[Games]]
* Do [[Multimedia tasks]] - listen to music, extract CDs, watch videos and DVDs
** [[Configure Sound]]
** [[Use Digital Cameras and Linux]]
** [[Use Camcorders and Linux]]
** [[Use Webcams and Linux]]
** [[Watch tv]]
* [[Talk to friends online]] - how to access common instant messaging networks, see also [[IM]].

= See also =
* [[TroubleShooting]] - you have a problem and need a solution
* [[Tips & Tricks]] - you want new ideas
* [[LinuxIntro]] - you need some overview

Embed a zip file into an image

2010-08-22T04:26:09Z

Sag47: /* See also */

{{PageAuthor|Sag47}}
This is for intermediate users of computers but I'll slim it down so basic users can benefit from this tutorial as well.

= About =
First lets go over some basic terminology.

''[[Encryption]]'' is a way to secure your files and scramble your data so that no one can read it but you. If you are interested in using encryption then I suggest [http://www.truecrypt.org/ TrueCrypt] which is free/open source and for Windows, Linux, and MAC.

''[http://en.wikipedia.org/wiki/Steganography Steganography]'' is the art and science of writing hidden messages in such a way that no one apart from the sender and intended recipient even realizes there is a hidden message.

So basically steganography is, in a way, more clever and effective at hiding data than encryption because it looks like something else. An example would be a folder full of family images, and one of those images is embedded with a zip file but to a would-be villain still looks like a folder of images. Only you know which image has the zip file so nothing looks suspicious.

Probably the most effective way of securing/hiding your information is combining Encryption with Stenography. So if my data was truly sensitive that I would require encryption and it needed to be transported then I would put my encrypted file within a zip file and combine it with an image to lower suspicion.

Are you interested yet? Well I'll stop beating around the bush and tell you how to do it! This requires that you have previous knowledge of what an image is and how to zip your files.

= How to do it =
== in Linux ==
cat MyImage.png MyZipFile.zip >> output.png
For more information about the cat command type "man cat" in the terminal. You may zip your files using the zip utility.
zip MyZipFile.zip myfile.txt
zip -r MyZipFile.zip myfolder/

== in Mac ==
Open the terminal from utilities and run the same command as you would in Linux. Google for "man cat" for more information on the cat command.

== in Windows ==
When I say type Ctrl+C it means to hold your Ctrl key down on the keyboard and, with Ctrl still held down, type the C key and then release both keys.

Open your command prompt: Type [Window Key]+R
In the run dialog type "cmd" without quotes. And press enter.

Now you must know where your image and zip file are located on your computer. Mine just so happens to be on the desktop and so that is what this command sequence is for. I already have an image called MyImage.png and a zip file called MyZipFile.zip located on my desktop.
C:\Users\User> cd Desktop

C:\Users\User\Desktop> '''''copy /b MyImage.png + MyZipFile.zip output.png'''''
input.png
comp.zip
1 file(s) copied.

C:\Users\User\Desktop>

If you notice that in "MyImage.png + MyZipFile.zip" the image goes before the zip file and there is a plus (+) symbol in between the two files.

= How to open it =
Ok, so what use is a zip file if you can't open it because it is an image? Well that problem is solved easily enough.
== in Linux and Mac ==
You just have to rename the image with a .zip extension to be able to unzip it.
mv output.png output.zip
unzip output.zip

== in Windows ==
Open a folder, any folder and click on ''Tools > Folder Options...'' (if you are using Windows Vista/7 then you must press the Alt key and then the menu will show up so you can click Tools). Click on the View tab and scroll down and uncheck "Hide extensions for known file types". You can now close that folder and look at your desktop. You will notice that everything has an extension now.

Simply right click on output.png (which is the image/zip file you created in this tutorial) and select rename. Change .png to .zip and now it can be opened as a zip file.

= Warnings and Notices =
* ''NOTE: If you are using Windows XP/2000 then your command line will look a little different but the commands are the same.''
* Once you create this image/zip file then the zip file can't be changed (even if you really want to add more files it won't) so every time you want to add/remove files from your image/zip file then you will have to recreate it from a new image and zip file.
* '''DO NOT EDIT''' your image/zip file with an image editor such as GIMP, Photoshop, or MS Paint. Those programs don't know what a zip file looks like so when you save any changes to the image it will destroy the zip file and only the image will be left behind.
* Remember that images aren't very big so if you combine a 500MB zip file with an image then the image will be 500MB. To me this would be a suspicious file if I was an attacker so I would look into it. There are better ways of hiding larger files from attackers and steganography is only one of many.

= See also =
* [[Encryption]]
* http://en.wikipedia.org/wiki/Encryption
* http://en.wikipedia.org/wiki/Steganography
* http://www.truecrypt.org/

[[Category:Guides]]