[Cialug] Wireless Kubuntu

[Todd Walton]

It works!  I got home from work this evening, and tried it out.  I had
fiddled with iwconfig a little and set the parameters of the interface
(key, essid, mode, so on).  Truthfully, I wasn't sure what I was
doing, but I knew enough to do that.  Not being sure what the next
step was, I opened up wlassistant and voila!  It connected right away,
no fuss.  And here I am typing in Kubuntu.

I think the issue may have been not configuration, but signal quality
or something, which means it'll probably come back.

So anyway, if I had a fully supported wireless card and a everything
was working right, how would I start up wireless from the command
line?  iwconfig to set the parameters...  Then does the card just do
its connecting?  Or is there some command to send to the card to tell
it connect?  I'd rather not rely on the GUI.  So... what's the
theoretical chain of events?

-todd


On 3/19/07, Dan Hockey <icepuck2k at mchsi.com> wrote:
> Have you tried making the connection without using encryption? On my former
> linksys router I had to disable encryption before Mandriva would connect,
> then I set up wep then everything worked from then on, go figure;)
> -dh
>
> -----Original Message-----
> From: cialug-bounces at cialug.org [mailto:cialug-bounces at cialug.org] On Behalf
> Of David Champion
> Sent: Monday, March 19, 2007 11:44 AM
> To: Central Iowa Linux Users Group
> Subject: Re: [Cialug] Wireless Kubuntu
>
> The Atheros driver is one of the better supported under linux - you
> should be able to use the native driver.
>
> -dc
>
> Todd Walton wrote:
> > On 3/18/07, Lars Althof <lars at larch.dk> wrote:
> >> Do you know what the wireless card in the laptop is?
> >
> > It's actually a desktop.  It's a Belkin F5D7000, using an Atheros chipset.
> >
> >> source drivers don't support the -g hardware very well, so you might be
> >> connecting at 12mbps, which  (I think) forces other computers to use the
> >> same speed.
> >
> > That would be worth looking into.  I think I read something in the
> > router's manual that indirectly implied that it could handle g at full
> > g even with a b connected.
> >
> >> switching to NDIS wrapper and the windows driver fixed it
> >> for me. If you don't know which chipset is in your laptop run lspci and
> >> look for wireless.
> >
> > Oh please no, don't make me deal with ndiswrapper!
> >
> >> You might also think about switch to Knetworkmanager, to me it seems
> >> much simpler to use and more stable, plus it will handle WPA.
> >
> > ACK.
> >
> > -todd
> > _______________________________________________
> > Cialug mailing list
> > Cialug at cialug.org
> > http://cialug.org/mailman/listinfo/cialug
> >
>
>
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>