Stephen Harris wrote:
> Create a simple S09 script (eg S09PROMISC) which basically just does
> "/sbin/ifconfig wlan0 promisc up"
>
> eg create this as /etc/init.d/PROMISC and then do "chkconfig PROMISC on"
>
>
> #!/bin/sh
>
> # PROMISC puts wlan0 in promisc mode
> #
> # chkconfig: 2345 09 91
>
On Thu, Jul 29, 2010 at 10:04:56PM -0400, Phil Savoie wrote:
> Ross Walker wrote:
> > Don't know, but I think there is an option you can put in your interface
> > file to bring it up in promiscuous mode. Try that and see if NM can grab it
> > on boot.
> There used to be a PROMISC=yes setting I c
Ross Walker wrote:
> On Jul 29, 2010, at 5:57 PM, Phil Savoie wrote:
>
>>> Doesn't it look like the wpa connection is successful?
>>> It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure)
>>> successful. Connected to wireless network 'pszone'."
>>> Only stages 3/4 (the DHCP par
On Jul 29, 2010, at 5:57 PM, Phil Savoie wrote:
>> Doesn't it look like the wpa connection is successful?
>> It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure)
>> successful. Connected to wireless network 'pszone'."
>> Only stages 3/4 (the DHCP part) seems to fail...
>> The
> Doesn't it look like the wpa connection is successful?
> It says: " Activation (wlan0/wireless) Stage 2 of 5 (Device Configure)
> successful. Connected to wireless network 'pszone'."
> Only stages 3/4 (the DHCP part) seems to fail...
> The DHCPDISCOVER times out.
> Google says that some people
From: Dave Miller
> Larry Vaden writes:
>
> >
> > On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie
> rogers.com> wrote:
> > > Beginning DHCP transaction.
> >>TRIMMED<<
> > > Jul 27 19:32:23 smurf3 NetworkManager: Device 'wlan0' DHCP
> > > transaction took too long (>45s), stopping it.
> >
On Wed, Jul 28, 2010 at 10:49 AM, Dave Miller wrote:
> I've also seen restating wpa_supplicant (as root, "service wpa_supplicant
> restart) fix things. Also, I've had better luck just getting the
> wpa_supplicant configuration right and not using NetworkManager (service
> NetworkManager stop).
Larry Vaden writes:
>
> On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie
rogers.com> wrote:
> > Beginning DHCP transaction.
>>TRIMMED<<
> > Jul 27 19:32:23 smurf3 NetworkManager: Device 'wlan0' DHCP
> > transaction took too long (>45s), stopping it.
> > Jul 27 19:32:23 smurf3 NetworkManager: w
John Doe wrote:
> Could it be IPv6?
>
> JD
>
I don't think so as I disabled IPV6 on install. But I do appreciate
your suggestion.
Thanks,
Phil
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
From: Phil Savoie
> I have the AR9285 wireless adaptor on an HP DV6-2128ca notebook. I can
> see it. it comes up in NetworkManager but never gets an IP. the router
> is a linksys using WPA/PSK security. Would/could someone please help me
> out trying to get this to work? Output of seve
Larry Vaden wrote:
> It would seem that one possibility is that the AP is not running a
> DHCP server.
>
> Another is that if the AP is running a DHCP server, it is restricting
> IP addresses to known clients.
>
> kind regards/ldv
Hi Larry,
Thanks for your reply. This wifi card is a known hos
On Tue, Jul 27, 2010 at 6:33 PM, Phil Savoie wrote:
> Beginning DHCP transaction.
> Jul 27 19:31:38 smurf3 dhclient: Internet Systems Consortium DHCP Client
> V3.0.5-RedHat
> Jul 27 19:31:38 smurf3 dhclient: Copyright 2004-2006 Internet Systems
> Consortium.
> Jul 27 19:31:38 smurf3 dhclient: All
Hello,
I have the AR9285 wireless adaptor on an HP DV6-2128ca notebook. I can
see it. it comes up in NetworkManager but never gets an IP. the router
is a linksys using WPA/PSK security. Would/could someone please help me
out trying to get this to work? Output of several commands follows:
d
13 matches
Mail list logo
