I am a linux newbie, but have managed to setup a backend and frontend sucessfully. My last task is the get my frontend networked wireless. I have intstalled a DWL-G520 card in the frontend, but I have no idea where to go from here(how to connect to my network). I have searched the forums for a wifi guide but have not found anything usefull. Is there a tutorial somewhere out there? Network utility? ???

Hi,

I think that card uses a Ralink chipset, specifically a Rt61. Drivers are here.

http://www.ralinktech.com/ralink/Home/Support/Linux.html

I hope this gets you started.

Bigb

Thanks for the reminder.

Thanks bigB. Unfortunately I think I will require a little more direction than that.

First off, you probably want to look here:
http://madwifi.org/wiki/Compatibility/D-Link
Check which hardware revision you have - as long as it's not A3, the madwifi driver should work.
If it is A3, you'll need to use ndiswrapper instead (AFAIK both madwifi and ndiswrapper should already be installed for R5F1, so it's just a matter of configuring things correctly).

If the madwifi driver works, you should just need to edit your /etc/network/interfaces file and change eth0 to ath0. You can find more info here:
http://madwifi.org/wiki/UserDocs/FirstTimeHowTo

If you end up needing to use ndiswrapper, this may help:
http://ndiswrapper.sourceforge.net/joom ... tallation/

thanks psicard that worked perfectly, I am now connected via wifi using madwifi. Now to connect to the AP I need to issue 4 commands



How can I have these commands sent automatically during startup?

I have answered my own question. Here is what I did:

I created a startup script at /etc/init.d/wifi-boot where wifi-boot is a file name that I have made up




then make it executable



and ensure it runs at startup by




But... small PROBLEM
This works as it should but my boot process is now very long. I assume that the system is getting stuck beacuse it cannot connect to the backend until my new script is run whenever that is. I cannot see any errors that might be present because I have enabled that splash screen at boot and have not yet figure out how to disable it.
Does anyone know how to get my script to run before the frontend attempts to connect to the backend? Or have any ideas on what else may be causing this LONG boot time?

The frontend doesn't attempt to connect to the backend until X and fluxbox start.

ok, any idea why the boot process is taking so long after chaging network settings?

Hi,

If you press the ESC key it should open a window so you can see what is occurring.

Time is relative, 1 minute, 2, 3, 10?
Mike

You might be better off adding your wireless config info to your /etc/network/interfaces file instead of the script you wrote. The ath0 stanza should look something like


I'm not sure if it'll speed things up or not, but your wireless connection may start up sooner in the boot process....

I have found that having a wireless link, even 54mbps, inbetween your backend and frontend will result in dissapointing lag.

I have run 100mbit cabling to my frontends for this reason. Its more work, but the increase in speed when you hit play and when seeking is well worth it

I agree with you 100% soundoff, if I could stayed wired I would but its just not an option in this case.

I discovered the cause of the slow boot by watching the boot sequence, it was printing DHCPDISCOVER over and over, entually fail and move on. I did what psicard suggested and it fixed this problem and I am still connected. Everything seems stable now.

Have you considered two 108Mbit routers?

Then you'd just connect the myth box via ethernet. This is how I'd do it, since it means zero configuration and no extra drivers on the linux box.

Cheers

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************

I run a wireless dlink in my backend. Here is my /etc/network/interfacesBut as you can see I use wpa

My old one for WEP was

_________________
KnoppMyth Folding@home
How to setup F@H
F@H Stats Page