[TriLUG] Wifi card weirdness

[Frye, Matthew]

Before I reloaded FC1, I had this card working 100% of the time.  I never
had to fumble with scripts or assign static addresses.  Since the eth0
initialization fails because it can't see the card, I wonder if setting
ONBOOT to no and running ifup in rc.local would work.  I am going to try
this and report my findings 

MPF

> -----Original Message-----
> From: David A. Cafaro [mailto:dac at trilug.org]
> Sent: Thursday, June 24, 2004 8:53 AM
> To: Triangle Linux Users Group discussion list
> Subject: Re: [TriLUG] Wifi card weirdness
> 
> 
> The only way I have ever gotten a wireless card to work 99.9% of the
> time via DHCP (assuming there weren't other non-DHCP related problems,
> ie. missing wep...) Was to use a personal script like this:
> 
> /sbin/ifconfig eth1 up
> sleep 3
> /sbin/iwconfig eth1 essid myessid mode Managed channel 6 key MYLONGKEY
> /sbin/dhclient eth1
> /sbin/dhclient-script
> 
> With a dummy ifcfg-eth1 file that looked like the setup for a normal
> ethernet wired interface set to DHCP vs static.  That always seems to
> pulls dhcp when I need it.  The first ifconfig and sleep commands are
> just specific to my card since it has to load up firmware first before
> it can be used (Prism54 based card, on fedora core 2).
> 
> -David
> 
> On Thu, 2004-06-24 at 08:05, Jon Carnes wrote:
> > I've had a lot of trouble with getting DHCP via WiFi on some of my
> > setups. Using a Linksys WRV54G Wireless Router I can get 
> DHCP in seconds
> > to anything directly connected, but it can take 5 minutes (or never
> > happen) to get DHCP out to a device connected wirelessly.
> > 
> > Connect the same device directly, and BOOM its up and 
> running. Give it a
> > static IP and run it wirelessly, and all works fine.  It's 
> just the DHCP
> > broadcast that doesn't work well (if at all).
> > 
> > Let me know if you find a nice solution.
> > 
> > Jon Carnes
> -- 
> David A. Cafaro
> dac(at)cafaro.net
> Admin to User: "You did what!?!?!"
> 
> -- 
> TriLUG mailing list        : 
> http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
> 

----- Confidentiality Notice -----
This e-mail and any attached documents contain confidential information belonging
to the sending entity, Rex Healthcare, and is intended only for the use of the 
individual(s) or entity(s) associated with the recipient addresses listed in the message 
header.  The authorized recipient of this information is prohibited from disclosing this 
information to any other party.  If you are not the intended recipient, you are hereby 
notified that any disclosure, copying, distribution or action taken in reliance on the 
contents of the email and/or attachments is strictly prohibited.  If you received this 
e-mail transmission in error, please notify the sender immediately to arrange for return 
or destruction of this information.

To report abuse or inappropriate use, please email abuse at rexhealth.com.