Re: connecting to a WPA secured wireless network often fails and takes a very long time



On Fri, 2006-09-22 at 17:12 +0300, Ertugrul Harman wrote:
> 
> 
> On 22/09/06, Darren Albers <dalbers gmail com> wrote:
>         On 9/22/06, Ertugrul Harman <ertugrulharman gmail com> wrote:
>         > On 22/09/06, Darren Albers <dalbers gmail com> wrote:
>         > > On 9/21/06, Ertugrul Harman <ertugrulharman gmail com>
>         wrote:
>         > > > This time it failed two times and could connect in the
>         3rd try (it took
>         > 11 
>         > > > min in total). The log is attached. It was in
>         var/log/syslog.
>         > >
>         > > Here is the problem:
>         > > Sep 21 23:24:54 localhost dhclient: DHCPDISCOVER on eth1
>         to
>         > > 255.255.255.255 port 67 interval 8
>         > > Sep 21 23:24:59 localhost kernel: [17179810.768000] eth1:
>         no IPv6
>         > > routers present
>         > > Sep 21 23:25:02 localhost dhclient: DHCPDISCOVER on eth1
>         to
>         > > 255.255.255.255 port 67 interval 9
>         > > Sep 21 23:25:02 localhost dhclient: DHCPOFFER from
>         192.168.1.1
>         > > Sep 21 23:25:02 localhost dhclient: DHCPREQUEST on eth1
>         to 
>         > > 255.255.255.255 port 67
>         > > Sep 21 23:25:07 localhost dhclient: DHCPREQUEST on eth1 to
>         > > 255.255.255.255 port 67
>         > > Sep 21 23:25:18 localhost dhclient: DHCPDISCOVER on eth1
>         to
>         > > 255.255.255.255 port 67 interval 8
>         > > Sep 21 23:25:26 localhost dhclient: DHCPDISCOVER on eth1
>         to 
>         > > 255.255.255.255 port 67 interval 12
>         > > Sep 21 23:25:35 localhost NetworkManager:
>         <information>^IDevice 'eth1'
>         > > DHCP transaction took too long (>45s), stopping it. 
>         > > Sep 21 23:25:36 localhost dhclient: DHCPRELEASE on eth1 to
>         192.168.1.1
>         > port 67
>         > > Sep 21 23:25:36 localhost dhclient: send_packet: Network
>         is unreachable
>         > > Sep 21 23:25:36 localhost dhclient: send_packet: please
>         consult README
>         > > file regarding broadcast address.
>         > > Sep 21 23:25:36 localhost NetworkManager:
>         <information>^IActivation
>         > > (eth1) Stage 4 of 5 (IP Configure Timeout) scheduled... 
>         > > Sep 21 23:25:36 localhost NetworkManager:
>         <information>^IDHCP daemon
>         > > state is now 14 (normal exit) for interface eth1
>         > > Sep 21 23:25:36 localhost NetworkManager:
>         <information>^IDHCP daemon 
>         > > state is now 11 (unknown) for interface eth1
>         > > Sep 21 23:25:36 localhost NetworkManager:
>         <information>^IDHCP daemon
>         > > state is now 14 (normal exit) for interface eth1
>         > > 
>         > > Something odd is happening when your laptop requests a
>         dhcp address,
>         > > what type of router or AP do you have?
>         >
>         >
>         > It is a 3com OfficeConnect ADSL Wireless 11g Firewall
>         Router.
>         >
>         
>         Mmm  I don't see anyone else complaining about DHCP issues
>         with that
>         device.  I see that the device offers you an IP but 33 seconds
>         later
>         your box never seems to accept it...   What wireless card is
>         it?
> 
> 
> It's Intel� PRO/Wireless 3945 802.11a/b/g Integrated Wireless LAN. 

ipw3945 seems to still be somewhat flaky still, given recent reports.

One other way to test this is to install Wireshark/Ethereal, and grab
packets that come over the air to see if the the AP is actually sending
out a DHCP reply.

Dan

> By the way maybe I should mention that there isn't any issue like this
> with this card and router under Windows XP.
> 
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]