reaver hangs when assotiates with ZTE routers

[GoogleCodeExporter]

A few things to consider before submitting an issue:

0. We write documentation for a reason, if you have not read it and are
having problems with Reaver these pages are required reading before
submitting an issue:
http://code.google.com/p/reaver-wps/wiki/HintsAndTips
http://code.google.com/p/reaver-wps/wiki/README
http://code.google.com/p/reaver-wps/wiki/FAQ
http://code.google.com/p/reaver-wps/wiki/SupportedWirelessDrivers
1. Reaver will only work if your card is in monitor mode.  If you do not
know what monitor mode is then you should learn more about 802.11 hacking
in linux before using Reaver.
2. Using Reaver against access points you do not own or have permission to
attack is illegal.  If you cannot answer basic questions (i.e. model
number, distance away, etc) about the device you are attacking then do not
post your issue here.  We will not help you break the law.
3. Please look through issues that have already been posted and make sure
your question has not already been asked here: http://code.google.com/p
/reaver-wps/issues/list
4. Often times we need packet captures of mon0 while Reaver is running to
troubleshoot the issue (tcpdump -i mon0 -s0 -w broken_reaver.pcap).  Issue
reports with pcap files attached will receive more serious consideration.

Answer the following questions for every issue submitted:

0. What version of Reaver are you using?  
reaver 1.4

1. What operating system are you using (Linux is the only supported 
OS)?backtrack 5 r2

2. Is your wireless card in monitor mode (yes/no)?yes mon0

3. What is the signal strength of the Access Point you are trying to crack?in 
backtrack -47

4. What is the manufacturer and model # of the device you are trying to
crack?rtl 8187

5. What is the entire command line string you are supplying to reaver?
reaver -i mon0 -b xx:xx:xx:xx:xx:xx -S -vv -c 6(tried with -L also)
6. Please describe what you think the issue is.
I think that reaver is not able to crack this kind of router(ZTE Router)because 
it support wps lock which doesn't unlock's anymore after it locks onse.
I have been waited for 36 hours and still nothing.
P.S. reaver has to workaround with those routers

7. Paste the output from Reaver below.
impossible at the moment.

Original issue reported on code.google.com by srdja...@gmail.com on 21 May 2012 at 6:48

[GoogleCodeExporter]

Please does anyone knows the problem here,or we should wait for reaver 1.5?

Original comment by srdja...@gmail.com on 23 May 2012 at 9:04

[GoogleCodeExporter]

you should wait for the router to reboot and try again.

Original comment by BHT...@gmail.com on 2 Jun 2012 at 2:56

[GoogleCodeExporter]

So I should wait for a days to reboot it again 'cause wait already for about 15 
hours and still nothing.

Original comment by srdja...@gmail.com on 2 Jun 2012 at 3:57