search

javitu / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 2 forks source link

Asus RT-N56U wireless-to-ethernet-bridge problems with WPA/WPA2? #1377

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.
Main router connected to internet, setup as router
2.
Secondary router setup as wireless ap (2.4GHz as ap-client only + 5GHz radio 
off, supposed to act as wireless-to-ethernet-bridge for printers etc.)
3.
Different unit names, wireless channel fixed, correct SSID selected (WPA as 
well as WPA2 tried and tested)

What is the expected output? What do you see instead?
Expected output: would be that the wired clients on the secondary Asus RT-N56U 
would be able to communicate with the clients of the main router, as well as 
the internet - and the clients of the main router to be able to communicate 
back.

Actual output: When using WPA AES or WPA2 AES the wired clients attached to the 
secondary router can ping other wired clients on the secondary router - as well 
as the secondary router itself, but not the main router (or its clients, or the 
internet). When using WPA TKIP or WPA2 TKIP the wired clients attached to the 
secondary router can ping eachother + the router itself BUT only intermittently 
ping the main router, its clients and the internet.

Ping statistics from wired client on the secondary router when using WPA AES or 
WPA2 AES:

$ ping 192.168.1.14
PING 192.168.1.14 (192.168.1.14): 56 data bytes
64 bytes from 192.168.1.14: icmp_seq=0 ttl=64 time=0.349 ms
64 bytes from 192.168.1.14: icmp_seq=1 ttl=64 time=0.418 ms
64 bytes from 192.168.1.14: icmp_seq=2 ttl=64 time=0.512 ms
64 bytes from 192.168.1.14: icmp_seq=3 ttl=64 time=0.453 ms
^C
--- 192.168.1.14 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.349/0.433/0.512/0.059 ms

$ ping 192.168.1.52
PING 192.168.1.52 (192.168.1.52): 56 data bytes
64 bytes from 192.168.1.52: icmp_seq=0 ttl=64 time=0.307 ms
64 bytes from 192.168.1.52: icmp_seq=1 ttl=64 time=0.495 ms
64 bytes from 192.168.1.52: icmp_seq=2 ttl=64 time=0.476 ms
64 bytes from 192.168.1.52: icmp_seq=3 ttl=64 time=0.435 ms
^C
--- 192.168.1.52 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.307/0.428/0.495/0.073 ms

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^C
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

$ ping 192.168.1.2
PING 192.168.1.2 (192.168.1.2): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
^C
--- 192.168.1.2 ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss

Ping statistics from wired client on the secondary router when using WPA TKIPor 
WPA2 TKIP:

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.416 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=1.370 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
cRequest timeout for icmp_seq 13
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=5.523 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=2.471 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=6.005 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=3.995 ms
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=1.945 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=55.653 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=2.729 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=13.044 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=1.159 ms
64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=1.478 ms
64 bytes from 192.168.1.1: icmp_seq=31 ttl=64 time=1.127 ms
64 bytes from 192.168.1.1: icmp_seq=32 ttl=64 time=1.114 ms
64 bytes from 192.168.1.1: icmp_seq=33 ttl=64 time=1.353 ms
64 bytes from 192.168.1.1: icmp_seq=34 ttl=64 time=1.655 ms
64 bytes from 192.168.1.1: icmp_seq=35 ttl=64 time=1.273 ms
Request timeout for icmp_seq 36
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
Request timeout for icmp_seq 39
Request timeout for icmp_seq 40
64 bytes from 192.168.1.1: icmp_seq=41 ttl=64 time=7.993 ms
64 bytes from 192.168.1.1: icmp_seq=42 ttl=64 time=26.010 ms
64 bytes from 192.168.1.1: icmp_seq=43 ttl=64 time=1.697 ms
64 bytes from 192.168.1.1: icmp_seq=44 ttl=64 time=1.181 ms
Request timeout for icmp_seq 45
64 bytes from 192.168.1.1: icmp_seq=46 ttl=64 time=1.709 ms
Request timeout for icmp_seq 47
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
Request timeout for icmp_seq 50
Request timeout for icmp_seq 51
Request timeout for icmp_seq 52
64 bytes from 192.168.1.1: icmp_seq=53 ttl=64 time=2.480 ms
64 bytes from 192.168.1.1: icmp_seq=54 ttl=64 time=5.281 ms
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
Request timeout for icmp_seq 59
Request timeout for icmp_seq 60
64 bytes from 192.168.1.1: icmp_seq=61 ttl=64 time=1.716 ms
64 bytes from 192.168.1.1: icmp_seq=62 ttl=64 time=1.172 ms
64 bytes from 192.168.1.1: icmp_seq=63 ttl=64 time=1.391 ms
Request timeout for icmp_seq 64
Request timeout for icmp_seq 65
Request timeout for icmp_seq 66
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
64 bytes from 192.168.1.1: icmp_seq=69 ttl=64 time=1.274 ms
64 bytes from 192.168.1.1: icmp_seq=70 ttl=64 time=2.887 ms
Request timeout for icmp_seq 71
Request timeout for icmp_seq 72
Request timeout for icmp_seq 73
Request timeout for icmp_seq 74
Request timeout for icmp_seq 75
Request timeout for icmp_seq 76
Request timeout for icmp_seq 77
64 bytes from 192.168.1.1: icmp_seq=78 ttl=64 time=1.228 ms
64 bytes from 192.168.1.1: icmp_seq=79 ttl=64 time=1.187 ms
64 bytes from 192.168.1.1: icmp_seq=80 ttl=64 time=2.801 ms
Request timeout for icmp_seq 81
Request timeout for icmp_seq 82
Request timeout for icmp_seq 83
Request timeout for icmp_seq 84
Request timeout for icmp_seq 85
Request timeout for icmp_seq 86
Request timeout for icmp_seq 87
Request timeout for icmp_seq 88
Request timeout for icmp_seq 89
Request timeout for icmp_seq 90
Request timeout for icmp_seq 91
Request timeout for icmp_seq 92
Request timeout for icmp_seq 93
^C
--- 192.168.1.1 ping statistics ---
95 packets transmitted, 32 packets received, 66.3% packet loss
round-trip min/avg/max/stddev = 1.114/5.104/55.653/10.245 ms

What version of the product are you using? On what operating system?

Using Padavan RT-N56U_3.4.3.8-088_base.trx on Asus RT-N56U

Further information:
The secondary router gets an IP/connects just fine to the main router, and the 
wired clients gets IP via DHCP from the main router OK.

The secondary router lists the clients of the main router in its network map.

The secondary router lists internet connection intermittently OK (probably the 
same issues as the wired clients, some requests gets through - just like the 
ping packets?)

Summary:
From what I've researched on my own the issue seems to originate from the 
encryption used, WPA/WPA2 AES is a no-go, WPA/WPA2 TKIP works intermittently.

I haven't tried using no encryption at all yet, will try to do so during the 
weekend.

Is this a known bug? or is it just me? (: If it is a known bug.. is there some 
older version of the firmware that I could use that does not suffer from it?

To conclude I'd just like to add that I _really_ like the web gui used in this 
firmware (: nice and smooth!

Original issue reported on code.google.com by spwn...@gmail.com on 12 Dec 2014 at 8:12

GoogleCodeExporter commented 8 years ago 
I've made some progress...

First I tried to bridge the 2.4GHz radio to/against an open (no 
security/encryption) network.. same result as with WPA/WPA2 TKIP, i.e. 
intermittently working...

I then (lacking better things to do) turned off the 2.4GHz radio and instead 
enabled and bridged the 5GHz radio against the same primary router - and it 
worked like I supposed the 2.4GHz would. No issues.

Is this news to anyone? same for the other people reporting similar issues? or 
perhaps its just me (: anyways, really happy having this up and running!

Original comment by spwn...@gmail.com on 12 Dec 2014 at 9:59

GoogleCodeExporter commented 8 years ago 
No issue for me. Primary is rt-n56u, secondary is tomato router, setup as 
wireless ethernet brdige and NFS client. Security use is wpa2.

Original comment by leandro.ong@gmail.com on 16 Dec 2014 at 11:01