Opened 14 years ago

Last modified 5 years ago

#6323 closed bug

wifi drops after a few mins on my Acer Aspire One — at Version 4

Reported by: l8night Owned by: axeld
Priority: normal Milestone:
Component: Servers/net_server Version: R1/alpha2
Keywords: Cc: modeenf
Blocked By: Blocking:
Platform: All

Description (last modified by diver)

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

ifconfig then shows ~> ifconfig loop Hardware Type: Local Loopback, Address: none

inet addr: 127.0.0.1, Mask: 255.0.0.0 MTU: 16384, Metric: 0, up loopback link Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Collisions: 0

/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 loop Hardware Type: Local Loopback, Address: none

inet addr: 127.0.0.1, Mask: 255.0.0.0 MTU: 16384, Metric: 0, up loopback link Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Collisions: 0

/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

Change History (4)

comment:1 by bbjimmy, 14 years ago

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.

Last edited 14 years ago by bbjimmy (previous) (diff)

comment:2 by deejam, 14 years ago

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.

comment:3 by modeenf, 13 years ago

Cc: modeenf added

I Will test this to :)

comment:4 by diver, 13 years ago

Component: - GeneralNetwork & Internet/Wireless
Description: modified (diff)
Owner: changed from nobody to axeld

Is it still reproducible?

Note: See TracTickets for help on using tickets.