[clue-tech] wireless on Ubuntu

[Tony McDowell]

At least you got it working in the end.  Networking (particularly Wireless
Networking) is my biggest pet peeve with Ubuntu.  Ubuntu is a bit Playskool
(but, hey, so was Win XP when it debuteD), but I like how most things "just
work" like on a Mac.  I am one of those that believe that Ubuntu is as close
as we're going to get to MacOS on generic PC hardware (short of an official
release from Cupertino).  However, networking still routinely breaks the
"suspension of disblief" and forces users into geek mode too much for my
liking.

Sadly, right now my home Linux boxen are down to just my file server (a
heavily modded MaxTerm 8300 running Trustix 2.1) and my on-again/off-again
Fedora tirade to run MythTV on my media center.  With wireless networking so
hit-or-miss under Ubuntu, I cannot justify it for my laptop and with my
590SLI mainboard suffering from the weird "Windows tampering with the NIC"
issue, I cannot easily dual-boot Windows and Linux on my desktop.

The above paragraph is, I suppose, my brief introduction of myself to the
group.  I'm "new" to the Denver area.  I'm technically still in Las Vegas,
but we move on the 18th og June.

-tony

On 6/6/07, dennisjperkins at comcast.net <dennisjperkins at comcast.net> wrote:
>
> Ubuntu 7.04.
>
> If you don't use shared/restricted WEP, it's easy.  Just use
> NetworkManager.  If you use shared WEP, you need to edit
> /etc/network/interfaces by hand.  That's not so hard, just one more line in
> interfaces, but finding the information took some time.  I did a fair amount
> of googling to find out how to do it.
>
> To be fair, it handles Atheros much better than the newest Fedora.  No
> support for madwifi from Fedora.  The two sites that were mentioned for the
> madwifi RPMs have bad RPMs because they have circular dependencies.  I
> didn't feel like figuring out how to make madwifi work on Fedora after
> compiling, so I just wiped Fedora and put Ubuntu on.
>
>  -------------- Original message ----------------------
> From: "Tony McDowell" <svet.am at gmail.com>
> > Which Ubuntu are you using?  My experiences with wireless on Ubuntu have
> > varied greatly.  In 6.10 and previous, good luck with WPA (it's
> _possible_,
> > but only by hacking .confs).  I was, however, able to use WEP
> successfully
> > without too much muss on both 6.10 and 6.06.  I played with 7.04 on my
> > ThinkPad T21 very briefly and I was able to connect to my WPA-PSK access
> > point without issue.
> >
> > -tony
> >
> > On 6/6/07, dennisjperkins at comcast.net <dennisjperkins at comcast.net>
> wrote:
> > >
> > > I spent last evening figuring out how to get WEP working on an Ubuntu
> > > desktop.  WPA would be better but the access point uses shared
> (restricted)
> > > WEP.  Considering how well Ubuntu set everything else up, I'm
> surprised at
> > > what was required to get WEP working.  It detected the Atheros chip
> and
> > > installed madwifi correctly.
> > >
> > > Ubuntu wants you to use NetworkManager to configure the network.  That
> is
> > > where my problems began.  It seems too primitive if you want more than
> basic
> > > WEP.  (I haven't tried it with WPA, so maybe that is better.)  I could
> set a
> > > key, but I could not set restricted mode.  Multiple keys can't be set,
> but I
> > > don't know how useful that feature is anyway.
> > >
> > > Maybe I asked the wrong question, but Ubuntu's documentation seems to
> > > gloss over WEP as much as possible.  I finally found the necessary
> > > information on the Madwifi site.
> > >
> > > Luckily I didn't need to set up roaming profiles.
> > > _______________________________________________
> > > clue-tech mailing list
> > > clue-tech at cluedenver.org
> > > http://www.cluedenver.org/mailman/listinfo/clue-tech
> > >
>
>
>
>
> ---------- Forwarded message ----------
> From: "Tony McDowell" <svet.am at gmail.com>
> To: "CLUE tech" <clue-tech at cluedenver.org>
> Date: Wed, 6 Jun 2007 20:03:02 +0000
> Subject: Re: [clue-tech] wireless on Ubuntu
> Which Ubuntu are you using?  My experiences with wireless on Ubuntu have
> varied greatly.  In 6.10 and previous, good luck with WPA (it's
> _possible_, but only by hacking .confs).  I was, however, able to use WEP
> successfully without too much muss on both 6.10 and 6.06.  I played with
> 7.04 on my ThinkPad T21 very briefly and I was able to connect to my
> WPA-PSK access point without issue.
>
> -tony
>
> On 6/6/07, dennisjperkins at comcast.net <dennisjperkins at comcast.net> wrote:
> >
> > I spent last evening figuring out how to get WEP working on an Ubuntu
> > desktop.  WPA would be better but the access point uses shared (restricted)
> > WEP.  Considering how well Ubuntu set everything else up, I'm surprised at
> > what was required to get WEP working.  It detected the Atheros chip and
> > installed madwifi correctly.
> >
> > Ubuntu wants you to use NetworkManager to configure the network.  That
> > is where my problems began.  It seems too primitive if you want more than
> > basic WEP.  (I haven't tried it with WPA, so maybe that is better.)  I could
> > set a key, but I could not set restricted mode.  Multiple keys can't be set,
> > but I don't know how useful that feature is anyway.
> >
> > Maybe I asked the wrong question, but Ubuntu's documentation seems to
> > gloss over WEP as much as possible.  I finally found the necessary
> > information on the Madwifi site.
> >
> > Luckily I didn't need to set up roaming profiles.
> > _______________________________________________
> > clue-tech mailing list
> > clue-tech at cluedenver.org
> > http://www.cluedenver.org/mailman/listinfo/clue-tech
> >
>
>
> _______________________________________________
> clue-tech mailing list
> clue-tech at cluedenver.org
> http://www.cluedenver.org/mailman/listinfo/clue-tech
> _______________________________________________
> clue-tech mailing list
> clue-tech at cluedenver.org
> http://www.cluedenver.org/mailman/listinfo/clue-tech
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cluedenver.org/pipermail/clue-tech/attachments/20070606/6f46b0cc/attachment-0002.html