Confirming this. My WAP AC is hopping all over the place. The device hasn’t physically moved since installation where it has been very happily running indoors on a ground floor on 5500 MHz.
Viewing current tx-power is not supported for ac-capable chipsets yet (and it’s not clean when it will be supported if at all).
That is a kinda well-known limitation.
Problem with DHCP server, always the same answer, DHCP … without success and the devices cant have the IP address, with ver 6.38.3
I replaced (downgrade) with 6.35.4 and everything is ok with vlan
internet to Rb3011 + fiber link to hp swith, and 3 others fiber ports to 3 mikrotik CRS-125 and 2 RB2011 (without any firewall rules) + devices srv, ip phone, etc
Some Android mobile not working with WiFi on 951 series and mAP lite.
In 6.38.3:
951G-2HnD
DHCP server on bridge
Port Wlan1 and ether2 - to bridge1 on 951
Android clients connect to WiFi1 of 951 and all(?..) is ok.
mAP lite
ether link to ether2 of 951G-2HnD
Port Wlan1 and ether - to bridge2 of mAP
If some android clients (mobile) connect to WiFi2 of mAP, they can’t take an ip addres, but log and status of dhcp client 951G is ok.
Another case.
My Android mobile 4.0.4 cannot connect to 951 - Invalid Security Credentials. But if i downgrade RouterOS on v.6.36.3 and older - it works.
Is it possible in dude to access the charts/graphs using web url like http://ipaddress/dude/chartfileforlinks.
I want to display usage graps ur to my clients like i giving in cacti.
Since v6.38 I have some trouble with WiFi on a CRS109 device. I use a CAPs based installation with different RouterBoards and one CRS109. The CRS is broadcasting the SSIDs, it looks that the clients are able to connect, but the clients can’t send or receive IP packets. Today I was lucky get the issue during a client was connected. So I was able to use ping to document the problem:
ping ct.de
PING ct.de (193.99.144.80): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
64 bytes from 193.99.144.80: icmp_seq=2 ttl=248 time=59.276 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
64 bytes from 193.99.144.80: icmp_seq=8 ttl=248 time=161.396 ms
Request timeout for icmp_seq 9
64 bytes from 193.99.144.80: icmp_seq=10 ttl=248 time=70.550 ms
64 bytes from 193.99.144.80: icmp_seq=11 ttl=248 time=34.136 ms
Request timeout for icmp_seq 12
64 bytes from 193.99.144.80: icmp_seq=13 ttl=248 time=84.672 ms
Request timeout for icmp_seq 14
64 bytes from 193.99.144.80: icmp_seq=15 ttl=248 time=103.062 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
64 bytes from 193.99.144.80: icmp_seq=22 ttl=248 time=122.725 ms
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
64 bytes from 193.99.144.80: icmp_seq=27 ttl=248 time=144.786 ms
64 bytes from 193.99.144.80: icmp_seq=28 ttl=248 time=111.927 ms
Request timeout for icmp_seq 29
64 bytes from 193.99.144.80: icmp_seq=30 ttl=248 time=126.983 ms
Request timeout for icmp_seq 31
^C
--- ct.de ping statistics ---
33 packets transmitted, 10 packets received, 69.7% packet loss
round-trip min/avg/max/stddev = 34.136/101.951/161.396/37.725 ms
The issue is on the CRS device only, all other devices working fine. The time it occurs is different and can some hours up to some days. Fall back to v6.37.x to avoid the issue. Has some one else the same problems?
EDIT:
I was wrong, did not think correctly. The phone was getting broadcast IP, this is the cause for not working … facepalm. Removing the broadcast IP from pool, it worked.
Sorry for the mess.
And Posting this again one more time as it is specific to 3.38.3
So i am running Dude 6.38.3 I spend 12 hours building out our entire network to wake up the next morning and having it all Gone. So I rebuilt it again. about 200 Devices running on a CCR1016. after I got the network completely done I went to back it up so that if i lost the data again i could restore. I started the backup 16 hours ago. 16 Hours ago. again for dramatic effect 16 HOURS AGO.
currently it is stating this:
/dude print
enabled: yes
data-directory: SSD
status: disabling before export: waiting for config changes to flush (3910678 bytes in queue)
After 16 Hours it has yet to backup a 45 Meg file. WTH. I am more then pleased that the DUDE was resurrected. However, I do not understand why a simple backup takes this long. It should take minute. I have backup my entire cloud platform 1.5 TBs twice during this simple database backup.
Can someone please give me and idea what the problem is.
I am running a CCR1016-12s-1S+ with an SSD dedicated for just the DUDE.
bug ??
in webfig/wireless into wlan1 at scan-list is not posible to put anything… only select default… in winbox its posible to put a range of frequencys like 5200-5450 …, until version 6.36 its works ok !!!
this bug has been found since 6.38. i did post this bug but due to unknown reason it seems unposted.
on fresh installed routerboard, we can not add more than one profile on usermanager. each time we add the second profile, the error shown is “failure: profile with such name-for-user already exists”
this error never happened before.