<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>New Linux User &#187; wireless</title>
	<atom:link href="http://www.everyjoe.com/newlinuxuser/tag/wireless/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.everyjoe.com/newlinuxuser</link>
	<description>Linux Tips - Information for Using Linux</description>
	<lastBuildDate>Sun, 06 Dec 2009 23:55:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Looks like the Broadcom driver works better now</title>
		<link>http://www.everyjoe.com/newlinuxuser/looks-like-the-broadcom-driver-works-better-now/</link>
		<comments>http://www.everyjoe.com/newlinuxuser/looks-like-the-broadcom-driver-works-better-now/#comments</comments>
		<pubDate>Wed, 18 Jun 2008 16:12:48 +0000</pubDate>
		<dc:creator>Clair Ching</dc:creator>
				<category><![CDATA[Geeky Fun]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[wifi]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://www.newlinuxuser.com/looks-like-the-broadcom-driver-works-better-now/</guid>
		<description><![CDATA[So far, I haven&#8217;t had much troubles with the wireless network in the office when I am using Ubuntu Hardy Heron.  I don&#8217;t get disconnected after 15-20 minutes of being online.  It used to happen that way a lot and it was really so much trouble having to connect to the wireless network that often.  Now that it seems to be much better, I also feel better about using the bcm43xx driver instead of using ndiswrapper to make the wireless networking happen.
That or I was experiencing a bad combination of things. Bad Broadcom driver, slow internet speeds, [...]<p>Post from: <a href="http://www.everyjoe.com/newlinuxuser">New Linux User</a></p>
]]></description>
			<content:encoded><![CDATA[<p>So far, I haven&#8217;t had much troubles with the wireless network in the office when I am using Ubuntu Hardy Heron.  I don&#8217;t get disconnected after 15-20 minutes of being online.  It used to happen that way a lot and it was really so much trouble having to connect to the wireless network that often.  Now that it seems to be much better, I also feel better about using the bcm43xx driver instead of using ndiswrapper to make the wireless networking happen.</p>
<p>That or I was experiencing a bad combination of things. Bad Broadcom driver, slow internet speeds, etc.</p>
<p>But seriously, I am relieved.  I don&#8217;t have to rant as much as I used to about the Broadcom wireless networking issues on my laptop.  I suppose there are still many of you who struggle with it.  Don&#8217;t lose hope! It can still improve as I have seen things with my own eyes. <img src='http://www.everyjoe.com/newlinuxuser/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I have to admit though that it was my biggest mistake to just buy a random laptop two years ago and that&#8217;s why you should be smarter and not follow my example at all.</p>
<p>To my fellow Broadcom victims who are on Ubuntu Hardy, there are answers on the forums.  Some of them don&#8217;t always work but it&#8217;s good to read and learn from them by trying them out.  You&#8217;d never know, right?  And through our feedback developers have a better idea of what works and what doesn&#8217;t.</p>
<p>Post from: <a href="http://www.everyjoe.com/newlinuxuser">New Linux User</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.everyjoe.com/newlinuxuser/looks-like-the-broadcom-driver-works-better-now/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HOWTO: Bringing Up Wireless Cards (continued)</title>
		<link>http://www.everyjoe.com/newlinuxuser/howto-bringing-up-wireless-cards-continued/</link>
		<comments>http://www.everyjoe.com/newlinuxuser/howto-bringing-up-wireless-cards-continued/#comments</comments>
		<pubDate>Mon, 27 Mar 2006 12:51:48 +0000</pubDate>
		<dc:creator>Jon</dc:creator>
				<category><![CDATA[How To]]></category>
		<category><![CDATA[wifi]]></category>
		<category><![CDATA[wireless]]></category>

		<guid isPermaLink="false">http://www.newlinuxuser.com/howto-bringing-up-wireless-cards-continued/</guid>
		<description><![CDATA[I recently recorded a video over at The Linux Learning Station on using iwconfig, ifconfig, and dhclient to bring up a wireless network card. The process in the video is the process that I&#8217;ve always followed because, thankfully, both my PCMCIA cards are usually recognized by most distros.
My process basically involves setting the essid and WEP password on the card and then bringing it up. In order to ensure that it comes up every time I boot, I make a little script and use update-rc.d to put it in the proper init directories.
What I didn&#8217;t know was that I could [...]<p>Post from: <a href="http://www.everyjoe.com/newlinuxuser">New Linux User</a></p>
]]></description>
			<content:encoded><![CDATA[<p>I recently recorded a video over at <a href="http://learning.jonwatson.ca/">The Linux Learning Station</a> on using <a href="http://learning.jonwatson.ca/configure-a-wireless-network-card-with-iwconfig-ifconfig-and-dhclient/">iwconfig, ifconfig, and dhclient to bring up a wireless network card</a>. The process in the video is the process that I&#8217;ve always followed because, thankfully, both my PCMCIA cards are usually recognized by most distros.</p>
<p>My process basically involves setting the essid and WEP password on the card and then bringing it up. In order to ensure that it comes up every time I boot, I make a little script and use <a href="http://learning.jonwatson.ca/starting-scripts-automatically-a-startup-debian/">update-rc.d to put it in the proper init directories</a>.</p>
<p>What I didn&#8217;t know was that I could put the essid and WEP values into the /etc/network/interfaces file rather than writing a script. Reader Kurtis put me on to that little gem and when I took a look at my interfaces file, it explained a lot to me about the difference between distros that pick up my card and distros that don&#8217;t.</p>
<blockquote><p>
# This file describes the network interfaces available on your system<br />
# and how to activate them. For more information, see interfaces(5).</p>
<p># The loopback network interface<br />
auto lo<br />
iface lo inet loopback</p>
<p># The primary network interface<br />
auto eth1<br />
iface eth1 inet dhcp<br />
        # wireless-* options are implemented by the wireless-tools package<br />
        wireless-mode managed<br />
        wireless-essid driveon<br />
        wireless-key1 8FB06577D76E84EE6D4233651D
</p></blockquote>
<p>I&#8217;m currently running flight 5 of Kubuntu Dapper Drake and it picked up my network card during install. It asked me for my essid and WEP key and lo&#8217; and behold &#8211; this is where it stored it.</p>
<p>So, instead of writing a script to bring your card up, you may also want to try putting the correct values into your interfaces file (if your distro doesn&#8217;t do it for you during install) and see what happens.</p>
<p>Thanks, Kurtis!</p>
<p>Post from: <a href="http://www.everyjoe.com/newlinuxuser">New Linux User</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.everyjoe.com/newlinuxuser/howto-bringing-up-wireless-cards-continued/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>