DWL-AG530 (AR5213) & 2.8.21

RouterOS General
1

Hi folks,

Just posting to confirm that 2.8.21 has indeed fixed the problems with the D-Link DWL-AG530. Using the normal wireless package (not nstreme but also not wireless-legacy) on a link of 6km in an extremely busy RF environment:

/tool bandwidth-test 10.16.0.81 protocol=tcp random-data=yes direction=both

status: running
duration: 1m11s
tx-current: 4.19Mbps
tx-10-second-average: 4.17Mbps
tx-total-average: 4.01Mbps
rx-current: 4.18Mbps
rx-10-second-average: 4.18Mbps
rx-total-average: 4.02Mbps

The cards on both ends are DWL-AG530 and the chip info is: mac:0x5/0x9, phy:0x43, a5:0x36, a2:0x0, eeprom:0x4008

Looks like we have a winner!

2

Great! but what do you mean with

Using the normal wireless package (not nstreme but also not wireless-legacy)

there are only two wireless packages: the regular one, and the old one with no changes.

3

I think he is using normal wireless driver (not legacy) but not using nstreame option…
I am looking forward to test this driver…but Im quite bussy this days…

4

Normis, You will need to correct few things :wink:

first :

0 wlan3 00:0F:3D:0F:C0:C2 no -21 11Mbps
1 wlan3 00:0D:88:A4:58:A3 no -22 2Mbps
2 wlan3 00:30:4F:2C:4C:80 no -23 11Mbps
3 wlan3 00:40:05:31:EA:BC no -22 11Mbps
4 wlan3 00:40:05:55:EF:37 no -20 11Mbps
5 wlan3 00:40:F4:95:4D:E8 no -30 2Mbps
6 wlan3 00:40:F4:95:4D:DA no -19 11Mbps
7 wlan3 00:10:A7:1A:67:89 no -20 11Mbps
8 wlan2 000D88C8D8C8 00:0D:88:C8:D8:C8 yes -72 24Mbps
9 wlan3 00:50:FC:C7:6B:BB no -22 11Mbps
10 wlan3 00:0B:6A:F7:AB:A8 no -21 2Mbps
11 wlan3 00:0B:6A:08:D7:A7 no -22 11Mbps
12 wlan3 00:0A:E6:5F:6F:14 no -23 11Mbps
13 wlan3 00:08:A1:6A:EC:7F no -23 11Mbps
14 wlan3 00:80:1E:12:D7:A9 no -23 11Mbps
15 wlan3 00:0F:3D:68:BE:6E no -21 11Mbps
16 wlan3 00:30:4F:30:28:C1 no -70 2Mbps
17 wlan3 00:0F:3D:68:BC:3C no -27 11Mbps
18 wlan3 00:0D:88:A4:E5:F7 no -29 11Mbps


only on 2.8.21(strange bug)
very positive bug :smiley: but this must be normalised…(see signal strenght)

second :

Turbo g mode on 2,4GHz - just it is not possible to link two MT (yeah what do You say about that : One Mikrotik to link them all ? )
Third :smiley:

PRISM 2.5 card

ping 192.168.1.106 size=1470
192.168.1.106 1470 byte ping: ttl=128 time=30 ms
192.168.1.106 1470 byte ping: ttl=128 time=158 ms
192.168.1.106 ping timeout
192.168.1.106 ping timeout
192.168.1.106 ping timeout
192.168.1.106 1470 byte ping: ttl=128 time=44 ms
192.168.1.106 1470 byte ping: ttl=128 time=30 ms
192.168.1.106 1470 byte ping: ttl=128 time=65 ms
192.168.1.106 1470 byte ping: ttl=128 time=41 ms
192.168.1.106 ping timeout
192.168.1.106 ping timeout
192.168.1.106 ping timeout
192.168.1.106 ping timeout
192.168.1.106 1470 byte ping: ttl=128 time=43 ms
192.168.1.106 1470 byte ping: ttl=128 time=34 ms
192.168.1.106 1470 byte ping: ttl=128 time=60 ms
192.168.1.106 1470 byte ping: ttl=128 time=99 ms
192.168.1.106 ping timeout
192.168.1.106 ping timeout
192.168.1.106 1470 byte ping: ttl=128 time=47 ms
192.168.1.106 ping timeout
192.168.1.106 1470 byte ping: ttl=128 time=103 ms
192.168.1.106 1470 byte ping: ttl=128 time=88 ms
23 packets transmitted, 13 packets received, 43% packet loss

ping on “normal 32b” packets is “good enough” but irregular and high!

ping 192.168.1.106
192.168.1.106 64 byte ping: ttl=128 time=26 ms
192.168.1.106 64 byte ping: ttl=128 time=6 ms
192.168.1.106 64 byte ping: ttl=128 time=18 ms
192.168.1.106 64 byte ping: ttl=128 time=5 ms
192.168.1.106 64 byte ping: ttl=128 time=41 ms
192.168.1.106 64 byte ping: ttl=128 time=6 ms
192.168.1.106 64 byte ping: ttl=128 time=7 ms
192.168.1.106 64 byte ping: ttl=128 time=6 ms
192.168.1.106 64 byte ping: ttl=128 time=20 ms
192.168.1.106 64 byte ping: ttl=128 time=32 ms
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 5/16.7/41 ms


utilisation:

received-packets-per-second: 5
received-bits-per-second: 2.15kbps
sent-packets-per-second: 30
sent-bits-per-second: 101kbps

but this is extremaly

ping 192.168.1.82 size=1470
192.168.1.82 ping timeout
192.168.1.82 ping timeout
192.168.1.82 1470 byte ping: ttl=128 time=116 ms
192.168.1.82 1470 byte ping: ttl=128 time=56 ms
192.168.1.82 1470 byte ping: ttl=128 time=120 ms
192.168.1.82 1470 byte ping: ttl=128 time=41 ms
192.168.1.82 1470 byte ping: ttl=128 time=382 ms
192.168.1.82 1470 byte ping: ttl=128 time=86 ms
192.168.1.82 ping timeout
192.168.1.82 1470 byte ping: ttl=128 time=117 ms
192.168.1.82 1470 byte ping: ttl=128 time=244 ms
192.168.1.82 ping timeout
192.168.1.82 1470 byte ping: ttl=128 time=339 ms
13 packets transmitted, 9 packets received, 30% packet loss
round-trip min/avg/max = 41/166.7/382 ms

I will send supout’s as fast as it’s possible but these MT work on private IP’s and i don’t have acces to router.
Could You tell me Your “direct-email” ?
or send me some information to my mail marksx@mikro-tik.pl ??

5

send it to support@mikrotik.com and me or uldis will check it out.

6

You are using dlink dwl-ag530 on a, b or g ?

7

We have DWL-AG530 and DWL-AG520 PCI cards deployed using 5.2 & 5.8 GHz. Also have Proxim 8242 PCI cards on A. With the 2.8.21 of the software all are running beautifully.