Folks, I have recently been brought on board with this company and am having to play some catch up. So have a few questions for the group. The software currently being used is Wisp-Dist (and some additional lrps like dhcpcd). We will probably be changing over to uClibc since it appears more current but that will take some time. We are currently experiencing what looks like resets on our access points and bridges. Since the current log is so small I don't have much to go on. Below is a partial copy of a log:
Jun 6 01:30:52 tlabjpt kernel: netcs1: TXEXC - fid=0x02fc - status=0x0001 ([RetryErr]) tx_control=000c Jun 6 01:30:52 tlabjpt kernel: retry_count=0 tx_rate=110 fc=0x0a08 (Data::0) Jun 6 01:30:52 tlabjpt kernel: addr1=00:02:6f:33:44:6b addr2=00:02:6f:36:8f:d2 addr3=00:02:6f:36:8f:d2 Jun 6 01:30:52 tlabjpt kernel: netcs1: STA 00:02:6f:33:44:6b TX rate lowered to 55 Jun 6 01:30:52 tlabjpt kernel: netcs1: STA 00:02:6f:33:44:6b TX rate raised to 110 Jun 6 01:30:53 tlabjpt kernel: netcs1: TXEXC - fid=0x0325 - status=0x0001 ([RetryErr]) tx_control=000c Jun 6 01:30:53 tlabjpt kernel: retry_count=0 tx_rate=110 fc=0x0a08 (Data::0) Jun 6 01:30:53 tlabjpt kernel: addr1=00:02:6f:33:44:6b addr2=00:02:6f:36:8f:d2 addr3=00:02:6f:36:8f:d2 Jun 6 01:30:53 tlabjpt kernel: netcs1: STA 00:02:6f:33:44:6b TX rate lowered to 55 Jun 6 01:30:53 tlabjpt kernel: netcs0: TXEXC - fid=0x02f6 - status=0x0001 ([RetryErr]) tx_control=000c Jun 6 01:30:53 tlabjpt kernel: retry_count=0 tx_rate=0 fc=0x0908 (Data::0) Jun 6 01:30:53 tlabjpt kernel: addr1=00:02:6f:36:aa:76 addr2=00:02:6f:35:31:18 addr3=00:02:6f:36:aa:76 Jun 6 01:30:53 tlabjpt kernel: netcs1: STA 00:02:6f:33:44:6b TX rate raised to 110 Jun 6 01:30:55 tlabjpt kernel: netcs1: TXEXC - fid=0x02e2 - status=0x0001 ([RetryErr]) tx_control=000c Jun 6 01:30:55 tlabjpt kernel: retry_count=0 tx_rate=110 fc=0x0a08 (Data::0) Jun 6 01:30:55 tlabjpt kernel: addr1=00:02:6f:33:44:6b addr2=00:02:6f:36:8f:d2 addr3=00:02:6f:36:8f:d2 Jun 6 01:30:55 tlabjpt kernel: netcs1: STA 00:02:6f:33:44:6b TX rate lowered to 55 The log is lost when the reset occurs so there is not a way to see what occurred just before the reset occurred. Would someone tell me what I am looking at here in the log? Maybe this is reason for the resets? Also, is there a way to turn more extensive logging on and have it sent to a server periodically? I do not see a module for ntp. Is there such a module to keep the points time synced? And the last question, I do not see in uClibc anything like the wavemon in Wisp-Dist. Is there something similar in uClibc? Reason I ask is it comes in handy looking at signal strengths and noise on a certain segment of the wireless segments. Thanks for the help. Terri Kelley Network Engineer T-Lab Broadband Wireless ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
