View Full Version : apconfig login problem
Some war boards seem to have problems when logging on with apconfig
username: admin
password: 1234
ip: 192.168.1.1
I can ping the war okay
apconfig authenticates okay and seems to start up but when it tries loading atheros settings it eventually times out with an error message:
tired of waiting for a reply from server
anyone else seen this ?
simcor23
02-20-2006, 11:03 AM
I had that problem, Had to swap the radio. Then everything worked fine. Try power cycling the board. Give it a minute before powering it up. If the problem persists try a different radio.
lonnie
02-20-2006, 11:36 AM
What are you using to power the board with?
I'm using a 15volt 1200 mAmp ac-dc converter. I have used this power supply with other boards that do not have a problem
I've tried swapping out some of the radio cards & it seems there is a problem.
If I take all the cm9 cards out it works.
If I put 1 cm9 card in at a time - only 1 of the cm9 cards appears, all the others do not appear, I have checked the seatings on the PCI connector.
So I am still uncertain whether it is a problem with the board or 3 of the 4 cm9's. Statistically I think it is more likely to be a problem with the board.
I will investigate further !
After investigating further ... there appears to be more than 1 problem.
Lonnies diagnosis of a power problem seemed logical so I tried cranking up the power using a bench supply, no change.
I then followed simcor's suggestion & tried swapping round the radio cards. It appears that 3 of the cm9's in this one war4 were not working at all. I tried swapping in & out with other boards & the cm9's are definitely the problem. I have not seen this with any of the other wars I have so I am a bit puzzled - 3 radios going bad in one board seems to be statistically unlikely.
So I removed the faulty cm9's & tried again. apconfig would come up & the replacement radio cards were all visible so far so good, but occasionally it would crash & occasionally apconfig would exhibit the same problem or not connect at all.
By trial & error I found that if I cleared the arp cache on the PC (arp -d) I could then reconnect okay, but it would still lose the connection some random time later.
In the end I ran ethereal to see what was going on & I noticed an arp broadcast for the wars default route (192.168.1.254) , when working with uninitialised systems I usually set my pc's ip address to 192.168.1.2 in order to see the war/wrap at 192.168.1.1. I changed my ip address to 192.168.1.254 & everything worked fine.