On Wed, 2004-11-03 at 10:02 -0500, Dan Williams wrote: > On Wed, 2004-11-03 at 00:42 -0500, Jason 'vanRijn' Kasper wrote: > > - NetworkManager has to have the mode set to "Managed" > > in /etc/sysconfig/network-scripts/ifcfg-eth1, from what I saw. This > > conflicts with FC's insistence on making the mode "Auto" so that I can > > change the channel to 6 and the rate to Auto > > (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133500). > > NM always sets the mode to Managed/Infrastructure. You should not be > able to change the channel on the card, since when you put the card into > Infrastructure mode, it will _automatically_ switch to the channel of > the ESSID you set on the card. There is no need to manually set the > channel and rate unless: > > 1) your AP is broken > 2) your card/firmware is broken > 3) you're using Ad-Hoc mode, in which case you aren't using NM > > What do you need to explicitly set the channel for? hmmmmm. Well, as it turns out, it's not the channel that I have to set to get things to work nicely in fedora's Network Configuration GUI. It's the rate. If I don't change the rate from the default "11M" to "Auto", then my card (a Symbol LA4111 Spectrum24 Wireless LAN PC Card) can't associate/get an IP address. As for the above... 1) I'm using a Linksys WRT54GS AP 2) I wouldn't argue this. =:) It's a pretty obscure card that uses orinoco_cs. 3) I don't think I'm doing this. Like I said, using fedora's network configurator works so long as I change the rate from "11M" to "auto" and use either Managed or Auto mode. > > > - unless I log into gnome as root, NetworkManagerInfo hard-locks-up my > > laptop. No, I cannot give a stack trace or anything useful to debug > > this. Specifically, what happens is I start NetworkManagerInfo, click > > on its menu, choose the SID of my network, and then sometimes > > immediately and sometimes after the error dialog box comes up to say > > "can't connect to this network" (it does NOT ask me for a WEP key if I'm > > not root), my laptop freezes hard. Mouse doesn't respond, kernel > > doesn't respond, etc., etc. > > Previously there were issues wtih the IPv6 stack and wireless drivers in > the _kernel_ (#rh135432# in bugzilla), these may be fixed. They caused > a hard-lock of machine where a panic would print to the console, but of > course you couldn't see it because you were in X. hrmmmmmm. That's interesting. I have ipv6 turned off on both of my network connections and yet lsmod still shows this... ipv6 232577 27 I'll add the below to /etc/modprobe.conf and reboot and retry this.... alias net-pf-10 off alias ipv6 off Also, in other news, I created a bugzilla for the issues I listed in this e-mail, not realizing you had replied already to them. =:/ Sorry about that. I guess if the above fixes my issue, then the only one I have left is NM not remembering the WEP key. Don't suppose that one is fixed already? =:D Thanks for your work on NM, Dan, and for the answers to my questions. =:) -- ,-----------------------------------------------------------------// | Jason 'vanRijn' Kasper :: Numbers 6:22-26 ` | All brontosauruses are thin at one end, much MUCH thicker | in the middle, and then thin again at the far end. That is | the theory that I have and which is mine, and what it is too. , | bash$ :(){ :|:&};: `----------------------//