On Tue, 12 Nov 2002 07:44 pm, Grahame Kelly wrote:
Further to the information I have supplied. If I even run "top" with a 2
second cycle (on the wireless client) the wireless interface goes tropo as
well so "heavy work" is a somewhat inopportune definition.
An example ifconfig at problem time is as follows:
eth0 Link encap:Ethernet HWaddr 00:90:4B:02:8C:5A
inet addr:10.10.10.101 Bcast:10.10.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:68 errors:1 dropped:0 overruns:0 frame:0
TX packets:65 errors:69454 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:6762 (6.6 Kb) TX bytes:27069 (26.4 Kb)
Interrupt:9 Base address:0x8000 Memory:dedfd000-dedfdfff
note the TX errors.
Cheers. Grahame
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
