On Tue, 2006-11-14 at 09:32 -0800, Christoph Maier wrote:
> On Tue, 2006-11-14 at 08:43 -0800, Carl Lowenstein wrote:
> > On 11/14/06, Andrew Lentvorski <[EMAIL PROTECTED]> wrote:
[...]
> > > iwconfig lists eth1 as unassociated. ESSID of nds Nickname: "ipw2100"
> > > Mode: managed Channel=0 Access Point: Not-Associated
> > >
> > > Anybody have some advice?
IWCONFIG(8) Linux Programmer’s Manual
IWCONFIG(8)
NAME
iwconfig - configure a wireless network interface
SYNOPSIS
iwconfig [interface]
iwconfig interface [essid X] [nwid N] [mode M] [freq F]
[channel C][sens S ][ap A ][nick NN ]
[rate R] [rts RT] [frag FT] [txpower T]
[enc E] [key K] [power P] [retry R]
[commit]
iwconfig --help
iwconfig --version
[...]
PARAMETERS
[...]
mode Set the operating mode of the device, which depends on
the net‐
work topology. The mode can be Ad-Hoc (network composed of
only
one cell and without Access Point), Managed (node
connects to a
network composed of many Access Points, with roaming),
Master
(the node is the synchronisation master or acts as an
Access
Point), Repeater (the node forwards packets between other
wire‐
less nodes), Secondary (the node acts as a backup
mas‐
ter/repeater), Monitor (the node is not associated with
any cell
and passively monitor all packets on the frequency) or
Auto.
Example :
iwconfig eth0 mode Managed
iwconfig eth0 mode Ad-Hoc
[...]
> I hope this makes more sense to you than it makes to me (I can't
> reproduce the result in Fedora) ... probably "Managed" is a Bad Thing
> for what you are trying to do.
>
> If you're trying to do what Carl thinks, it's way over my head.
>
> Christoph
>
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
