wifi drops after a few mins on my Acer Aspire One

[l8night]

on my Acer Aspire One I find that the wifi works for a bit then just drops ifconfig then shows

~> ifconfig
/dev/net/atheroswifi/0
        Hardware Type: Ethernet, Address: 00:24:2b:1d:ae:cd
        inet addr: 169.254.0.113, Bcast: 169.254.255.255, Mask: 255.255.0.0
        MTU: 1500, Metric: 0, up broadcast link auto-configured
        Receive: 1587 packets, 0 errors, 1376409 bytes, 0 mcasts, 0 dropped
        Transmit: 1629 packets, 1 errors, 195121 bytes, 0 mcasts, 0 dropped
        Collisions: 0

/dev/net/rtl81xx/0
        Hardware Type: Ethernet, Address: 00:23:8b:54:d7:04
        inet addr: 169.254.0.47, Bcast: 169.254.255.255, Mask: 255.255.0.0
        MTU: 1500, Metric: 0, up broadcast auto-configured
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 9 packets, 0 errors, 2673 bytes, 0 mcasts, 0 dropped
        Collisions: 0

instead of the original

~> ifconfig
/dev/net/atheroswifi/0
        Hardware Type: Ethernet, Address: 00:24:2b:1d:ae:cd
        inet addr: 192.168.1.14, Bcast: 192.168.1.255, Mask: 255.255.255.0
        MTU: 1500, Metric: 0, up broadcast link auto-configured configuring
        Receive: 16 packets, 0 errors, 6854 bytes, 0 mcasts, 0 dropped
        Transmit: 16 packets, 1 errors, 4313 bytes, 0 mcasts, 0 dropped
        Collisions: 0

/dev/net/rtl81xx/0
        Hardware Type: Ethernet, Address: 00:23:8b:54:d7:04
        inet addr: 
        MTU: 1500, Metric: 0, up broadcast configuring
        Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped
        Transmit: 6 packets, 0 errors, 1782 bytes, 0 mcasts, 0 dropped
        Collisions: 0

[bbjimmy]

This happens to me on my eeepc, but only if there are more thanone wireless networks available. In these cases I need to change to a static ip then re-boot. The system will then maintain a connection. Without the re-boot, it will use dhcp and then change the ip to 169.254.0.113 and the connection is dead again.

[deejam]

Is this error still present? If it is, please attach the syslog showing the DHCP logging when this occured. The description in this ticket is not enough to be able to spot the problem.

[modeenf]

I Will test this to :)

[diver]

Is it still reproducible?

[diver]

Actually it looks like a dhcp issue. Changing component.

[waddlesplash]

Please retest with a recent nightly.

[waddlesplash]

No reply, closing.

[nielx]

Remove milestone for tickets with status = closed and resolution != fixed