<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Slackware 12 Wireless WPA using ipw2200</title>
	<atom:link href="http://www.dkpw.co.uk/wp/?feed=rss2&#038;p=465" rel="self" type="application/rss+xml" />
	<link>http://www.dkpw.co.uk/wp/?p=465</link>
	<description>Bluff &#38; Bluster</description>
	<lastBuildDate>Tue, 07 Sep 2010 12:08:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: davidw</title>
		<link>http://www.dkpw.co.uk/wp/?p=465&#038;cpage=1#comment-415</link>
		<dc:creator>davidw</dc:creator>
		<pubDate>Sat, 30 Aug 2008 14:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.dkpw.co.uk/wp/?p=465#comment-415</guid>
		<description>Thanks for letting me know Katie, glad you got it working.</description>
		<content:encoded><![CDATA[<p>Thanks for letting me know Katie, glad you got it working.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katie</title>
		<link>http://www.dkpw.co.uk/wp/?p=465&#038;cpage=1#comment-414</link>
		<dc:creator>Katie</dc:creator>
		<pubDate>Mon, 25 Aug 2008 23:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.dkpw.co.uk/wp/?p=465#comment-414</guid>
		<description>Thanks!

Worked for me on slackware 12.1!</description>
		<content:encoded><![CDATA[<p>Thanks!</p>
<p>Worked for me on slackware 12.1!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidw</title>
		<link>http://www.dkpw.co.uk/wp/?p=465&#038;cpage=1#comment-389</link>
		<dc:creator>davidw</dc:creator>
		<pubDate>Wed, 30 Jul 2008 20:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dkpw.co.uk/wp/?p=465#comment-389</guid>
		<description>Thanks Hamish, good to know that this helped and that it is also relevant for Slackware 12.1

You have hit on the difference between Slack and many other distributions. Most offer some front end GUI to manage wireless connections and in effect store the SSID and any accompanying passwords in a DB. Slack relies on good old fashioned script editing.

You would need to amend /etc/rc.d/rc.wireless.conf with the new network&#039;s details as well as /etc/wpa_supplicant.conf. This can be accomplished quickly and easily in a console window and will be finished before a GUI has sniffed the WAP, checked the password and failed to connect you. :-)

After amending the files you would need to run the commands at the end of the post to connect.

What I have done in the past is include all my regularly used networks in the above files and commented out the ones I don&#039;t need at that moment. That saves some typing.  

You might like to see this thread at LinuxQuestions which discusses using a WPA GUI but the consensus is that amending the files by hand is the way to go. It is certainly the Slack way.

http://www.linuxquestions.org/questions/slackware-14/wpa-not-working-slackware-12.1-656755/

Good luck!</description>
		<content:encoded><![CDATA[<p>Thanks Hamish, good to know that this helped and that it is also relevant for Slackware 12.1</p>
<p>You have hit on the difference between Slack and many other distributions. Most offer some front end GUI to manage wireless connections and in effect store the SSID and any accompanying passwords in a DB. Slack relies on good old fashioned script editing.</p>
<p>You would need to amend /etc/rc.d/rc.wireless.conf with the new network&#8217;s details as well as /etc/wpa_supplicant.conf. This can be accomplished quickly and easily in a console window and will be finished before a GUI has sniffed the WAP, checked the password and failed to connect you. <img src='http://www.dkpw.co.uk/wp/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>After amending the files you would need to run the commands at the end of the post to connect.</p>
<p>What I have done in the past is include all my regularly used networks in the above files and commented out the ones I don&#8217;t need at that moment. That saves some typing.  </p>
<p>You might like to see this thread at LinuxQuestions which discusses using a WPA GUI but the consensus is that amending the files by hand is the way to go. It is certainly the Slack way.</p>
<p><a href="http://www.linuxquestions.org/questions/slackware-14/wpa-not-working-slackware-12.1-656755/" rel="nofollow">http://www.linuxquestions.org/questions/slackware-14/wpa-not-working-slackware-12.1-656755/</a></p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamish</title>
		<link>http://www.dkpw.co.uk/wp/?p=465&#038;cpage=1#comment-388</link>
		<dc:creator>Hamish</dc:creator>
		<pubDate>Wed, 30 Jul 2008 14:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.dkpw.co.uk/wp/?p=465#comment-388</guid>
		<description>This was a great help to me in getting my wireless connected on my laptop. I have a full router, and wireless is a big help when setting up my computer!

All the networking stuff is fine for Slackware 12.1.

What happens when you want to join another network? Wouldn&#039;t hard-coding your ESSID into rc.wireless stop you from connecting to another network? I am new to wireless and Slackware, so forgive my ignorance!</description>
		<content:encoded><![CDATA[<p>This was a great help to me in getting my wireless connected on my laptop. I have a full router, and wireless is a big help when setting up my computer!</p>
<p>All the networking stuff is fine for Slackware 12.1.</p>
<p>What happens when you want to join another network? Wouldn&#8217;t hard-coding your ESSID into rc.wireless stop you from connecting to another network? I am new to wireless and Slackware, so forgive my ignorance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: davidw</title>
		<link>http://www.dkpw.co.uk/wp/?p=465&#038;cpage=1#comment-218</link>
		<dc:creator>davidw</dc:creator>
		<pubDate>Fri, 21 Mar 2008 03:49:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.dkpw.co.uk/wp/?p=465#comment-218</guid>
		<description>Darkstar - you are pissed! Stop it right now. You naughty person! eth0 and eth1 are viable entities and deserve your respect. Remember the BBC Acorn! They are its children.

Need I say more?</description>
		<content:encoded><![CDATA[<p>Darkstar &#8211; you are pissed! Stop it right now. You naughty person! eth0 and eth1 are viable entities and deserve your respect. Remember the BBC Acorn! They are its children.</p>
<p>Need I say more?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darkstar</title>
		<link>http://www.dkpw.co.uk/wp/?p=465&#038;cpage=1#comment-217</link>
		<dc:creator>Darkstar</dc:creator>
		<pubDate>Thu, 20 Mar 2008 22:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.dkpw.co.uk/wp/?p=465#comment-217</guid>
		<description>And lo!From the hills they came, the hairy nerds of config, streaming down the drab slopes of despair as their Pairwise Ciphers failed to recognise the supplicant, slack kernel of ineptitude that pursued them, its hideous swollen purple modprobe rearing up against the darkening sky - final battle between eth0 and eth1 about to commence.

I could go on................</description>
		<content:encoded><![CDATA[<p>And lo!From the hills they came, the hairy nerds of config, streaming down the drab slopes of despair as their Pairwise Ciphers failed to recognise the supplicant, slack kernel of ineptitude that pursued them, its hideous swollen purple modprobe rearing up against the darkening sky &#8211; final battle between eth0 and eth1 about to commence.</p>
<p>I could go on&#8230;&#8230;&#8230;&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
