John H. Robinson, IV wrote:
> [EMAIL PROTECTED] wrote:
>> On Sun, Nov 18, 2007 at 05:57:20PM -0800, John H. Robinson, IV wrote:
>>> Every time I have made a modification via iwconfig, it took place
>>> *immediately*. What, exactly, are you doing?
>> For example...
>>
>> Switching SSIDs,
> 
> # iwconfig $INTERFACE essid any
> # iwconfig $INTERFACE essid NETGEAR
> 
> Changes take place *instantly*. Run a dhclient right after that.
> 
>> switching from WEP to non-WEP,
> 
> # iwconfig $INTERFACE key off
> 
>> switching from non-WEP to WEP....
> 
> # iwconfig $INTERFACE key $KEY
> 
>> all of these require tweaking /etc/network/interfaces and then doing
>> /etc/init.d/networking restart and/or rebooting.
> 
> None of them do. You can use iwconfig directly. Once you get your
> settings down, then put them into your interfaces file.

Hey, jhriv, this discussion is very close to what I've been _pining_ for.

For wired interfaces, I feel I sorta-mastered the commandline sequence
some time ago, so that I can use ifconfig, route (and edit
/etc/resolv.conf) to solve a lot of problems without using scripts. I
admit to not having dhclient commands down, yet -- though I can look at
them in ps, copy the command args, and kill old dhclients when they seem
to get in the way.

Now, for wireless, I have _some_ acquaintance with iwconfig, but not
enough to do everything via commandline, so I often find myself puzzled
in the same way as CS, in this thread.

I am convinced the start/stop scripts sometimes are the cause of
problems in the sense that they cannot recover from stupid-user-tricks.

So, boy-o-boy, I would be your friend forever if you could actually show
(some) recipes for the complete commandline sequence for wireless
setup/shutdown -- including dhclient and wep_supplicant (as req'd),
..pleeeease.


Aside: I have seen problems caused by (fixed by killing) previously
started dhclient  (and wep_supplicant?) and maybe(??) dhcpdb. Could be
that's biting CS and  that's what gets fixed eventually (timeout) or on
reboot .. hmm?

> 
>> When this is done, DHCP server search/connection attempts fail and
>> fail over and over for a long time.
>>
>> then....after like the 10th reboot and/or /etc/init.d/networking restart
>> it starts working with the new hotspot!?!??!
> 
> Sounds more like hotspot issues vice host issues. What type of Access
> Point are you trying to connect to? What does iwspy(8) tell you?

Regards,
..jim


-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to