On Wed, Feb 03, 2010 at 12:44:45AM -0600, Kent West wrote:
> Celejar wrote:
> > This is the networking subsystem attempting to configure the wireless
> > interface.
> >
> >
> >> Sending on LPF/wlan0/00:18:f8:29:b5:96
> >> Sending on Socket/fallback
> >> DHCPDISCOVER on wlan0 to 255.255.255.2
On Tue, Feb 02, 2010 at 04:04:54PM -0600, Kent West wrote:
[...]
>
> After a couple of reboots, and after running wicd-client from the actual
> machine instead of over ssh, the machine did not lock up; it did see the
> various ACUWireless networks, but when I tried clicking on the first
> one, i
Matthew Moore wrote:
> On Tuesday February 2 2010 3:21:33 pm Kent West wrote:
>
>> Listening on LPF/wlan0/00:18:f8:29:b5:96
>> Sending on LPF/wlan0/00:18:f8:29:b5:96
>> Sending on Socket/fallback
>> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
>> DHCPDISCOVER on wlan0 to 255.2
Kent West:
>
> we...@evoljasen:~$ dmesg | grep wlan
-- snip
> [ 267.697118] wlan0: AP denied association (code=10)
Well, there you have it. The access point does not want to talk to you.
You said it works using the same card in a different machine? -Otherwise
I would suspect the access points ha
Celejar wrote:
> This is the networking subsystem attempting to configure the wireless
> interface.
>
>
>> Sending on LPF/wlan0/00:18:f8:29:b5:96
>> Sending on Socket/fallback
>> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
>> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 i
On Tue, 02 Feb 2010 14:03:56 -0600
Kent West wrote:
...
> Now I get no dhcp offers received. I don't understand how ifup/down and
> /etc/modules and udev and /etc/network/interfaces and "wpa-conf
> /etc/wpa_supplicant/wpa_supplicant.conf" and iwlist/spy/scan/whatever
> and eth0 vs wlan0 vs sit0
On Tuesday February 2 2010 3:21:33 pm Kent West wrote:
> Listening on LPF/wlan0/00:18:f8:29:b5:96
> Sending on LPF/wlan0/00:18:f8:29:b5:96
> Sending on Socket/fallback
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
>
Jochen Schulz wrote:
> Kent West:
>
>> we...@evoljasen:~$ sudo iwconfig wlan0
>> wlan0 IEEE 802.11bg ESSID:"ACUWireless"
>> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
>>
>
> Did you wait a few seconds before running this command? Association does
> not
Kent West:
>
> we...@evoljasen:~$ sudo iwconfig wlan0 essid any && sudo iwconfig wlan0
> essid ACUWireless
Thanks for fixing my errors.
> we...@evoljasen:~$ sudo iwconfig wlan0
> wlan0 IEEE 802.11bg ESSID:"ACUWireless"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associ
Jochen Schulz wrote:
> Kent West:
>
>> Jochen Schulz wrote:
>>
>>> /etc/network/interfaces contains the configuration of all your network
>>> devices.
>>>
>> Well, that's what I thought, except a couple of people on this thread
>> told me to remove my wireless from this file and use
Matt Zagrabelny wrote:
> On Tue, 2010-02-02 at 16:00 -0600, Kent West wrote:
>
>
>> So, how do I associate an Access Point?
>>
>
> Associate to a wireless network:
>
> sudo iwconfig wlan0 essid UMD-Wireless
>
> Associate to a AP, I wouldn't do this step:
>
> sudo iwconfig wlan0 ap mac-addre
Kent West:
> Jochen Schulz wrote:
>>
>> /etc/network/interfaces contains the configuration of all your network
>> devices.
>
> Well, that's what I thought, except a couple of people on this thread
> told me to remove my wireless from this file and use wicd or
> NetworkManager, so it's not always
Kent West wrote:
> After a couple of reboots, and after running wicd-client from the actual
> machine instead of over ssh, the machine did not lock up; it did see the
> various ACUWireless networks, but when I tried clicking on the first
> one, it thought for a minute or two, then reported "Connect
On Tue, 2010-02-02 at 16:00 -0600, Kent West wrote:
> So, how do I associate an Access Point?
Associate to a wireless network:
sudo iwconfig wlan0 essid UMD-Wireless
Associate to a AP, I wouldn't do this step:
sudo iwconfig wlan0 ap mac-address-of-ap-radio
sudo ifup wlan0
--
Matt Zagrabelny
On Tue, 2010-02-02 at 16:00 -0600, Kent West wrote:
>
> we...@evoljasen:~$ sudo iwconfig wlan0
> wlan0 IEEE 802.11bg ESSID:"ACUWireless"
> Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
> Tx-Power=27 dBm
> Retry min limit:7 RTS thr:off
Kent West wrote:
> Kent West wrote:
>
>> Mathew Moore suggested I use wicd-curses.
>>
>> So I did; found the ACUWireless node; tried pressing "c" to connect;
>> nothing happened; then tried "C", and the machine froze up again.
>>
>>
>>
>
> Wait, wait. The machine came back to life after
Jochen Schulz wrote:
> Kent West:
>
>> Now I get no dhcp offers received. I don't understand how ifup/down and
>> /etc/modules and udev and /etc/network/interfaces and "wpa-conf
>> /etc/wpa_supplicant/wpa_supplicant.conf" and iwlist/spy/scan/whatever
>> and eth0 vs wlan0 vs sit0 and auto eth1 vs
Kent West:
>
> Now I get no dhcp offers received. I don't understand how ifup/down and
> /etc/modules and udev and /etc/network/interfaces and "wpa-conf
> /etc/wpa_supplicant/wpa_supplicant.conf" and iwlist/spy/scan/whatever
> and eth0 vs wlan0 vs sit0 and auto eth1 vs allow-hotplug eth1 and wep v
Kent West wrote:
> Mathew Moore suggested I use wicd-curses.
>
> So I did; found the ACUWireless node; tried pressing "c" to connect;
> nothing happened; then tried "C", and the machine froze up again.
>
>
Wait, wait. The machine came back to life after a few minutes.
But still, no indication
Chance Platt wrote:
> Kent West wrote:
>> Here's some relevant information, I believe:
>>
>> 01:08.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
>> 54g] 802.11g Wireless LAN Controller (rev 02)
>> Subsystem: Linksys WMP54GS version 1.1 [Wireless-G PCI Adapter]
>> 802.11g w/Sp
On Tue, Feb 02, 2010 at 14:03:56 -0600, Kent West wrote:
[...]
> Now I get no dhcp offers received. I don't understand how ifup/down and
> /etc/modules and udev and /etc/network/interfaces and "wpa-conf
> /etc/wpa_supplicant/wpa_supplicant.conf" and iwlist/spy/scan/whatever
> and eth0 vs wlan0 vs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kent West wrote:
> If I understood all that, I bet I could figure out how to get my
> wireless network working. However, I've been googling/studying off and
> on for the past year, everytime I try to put Debian (or Ubuntu, or
> whatever) on a laptop th
On Tuesday February 2 2010 1:28:21 pm Chance Platt wrote:
> Step Three - don't worry about the plumbing. Use either NetworkManager
> or WICD. These take care of the plumbing, and they work. If they don't
> work with your particular network, try connecting to an unsecured
> network first to check
Kent West wrote:
I have a Sid box with a wireless PCI card. Somehow or 'nuther I got it
working last year.
Last week the power supply died, and rather than scrounge up another, I
just moved the hard drive and wireless card to another computer. I'm
doing the work on the computer in a different lo
I have a Sid box with a wireless PCI card. Somehow or 'nuther I got it
working last year.
Last week the power supply died, and rather than scrounge up another, I
just moved the hard drive and wireless card to another computer. I'm
doing the work on the computer in a different location, with a diff
25 matches
Mail list logo
