[Tfug] Trouble with wifi ap. Out of ideas

[Nathanial Hendler]

iwlist eth1 scannig worked for me.  Here's what I got...

          Cell 01 - Address: 00:1A:E3:5E:E7:50
                    ESSID:"stayonline"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:1
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=39/100  Signal level=-77 dBm
                    Extra: Last beacon: 220ms ago
          Cell 02 - Address: 00:1B:2B:35:1B:20
                    ESSID:"stayonline"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:1
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=51/100  Signal level=-70 dBm
                    Extra: Last beacon: 216ms ago
          Cell 03 - Address: 00:1B:2B:35:1F:70
                    ESSID:"stayonline"
                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Channel:6
                    Encryption key:off
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
                              11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Quality=71/100  Signal level=-57 dBm
                    Extra: Last beacon: 20ms ago


... so it was automatically connecting to Cell 03 (channel 6) because it has
a higher signal quality.  When I forced eth1 to channel 1, it started
working.  I don't understand it, but it's working.

Nathan

On 7/4/07, Jude Nelson <judecn at gmail.com> wrote:
>
> Try deactivating your landline interface (i.e. sudo ifconfig eth0
> down).  In
> my experience at least, sometimes when using both a landline and wireless
> interface, the routing table for various reasons will assume that the
> landline leads to the default gateway.  You can change this using the
> route
> command, or you can deactivate it (and thus reassigning the default
> gateway
> to a different interface); both are different means to the same end.
>
> To get a list of wireless APs, run "sudo iwlist eth1 scanning"
>
> Also, what chipset and driver?
>
> Regards,
> Jude Nelson
>
> On 7/4/07, Glen Pfeiffer <glen at thepfeiffers.net> wrote:
> >
> > On 07/04/2007 10:25 AM, Nathanial Hendler wrote:
> > > If I run windows, the wireless works just fine, so I know the
> > > access point is ok.
> > >
> > I would not be too quick to say that. I was running a DLink (yes
> > it is junk) and my laptop running Windows could access it fine,
> > but running Debian Etch, it exhibited behavior similar to what
> > you described. I swapped out the wireless router to a Linksys,
> > and it works flawlessly now.
> >
> >
> > > Only windows can give me a list.  I can't get a list (or don't
> > > know how) from the linux side of things.
> > >
> > I think 'iwlist wlan0 scan' will do the trick. Replace wlan0 with
> > your wireless interface name. Also, the interface must be up
> > before scanning will work, but it does not need to be connected.
> >
> > Sorry I can't offer any real help.
> >
> > --
> > Glen
> >
> >
> > _______________________________________________
> > Tucson Free Unix Group - tfug at tfug.org
> > Subscription Options:
> > http://www.tfug.org/mailman/listinfo/tfug_tfug.org
> >
> _______________________________________________
> Tucson Free Unix Group - tfug at tfug.org
> Subscription Options:
> http://www.tfug.org/mailman/listinfo/tfug_tfug.org
>