I have RB133 with fw 3.19 here on my table. I’m trying to add virtual iface via Winbox named wlan2. Trying wireless/interface/add/virtualAP. I’m creating this from wlan1 - normal wlan card inserted in the board. The virtual AP is successfully created, but when I login via telnet to the board and print the wlan interface /interface/wireless/print, I see:
Why is there “master-interface=(unknown)” in the wlan2 output? In the dialog box I properly set up the master interface to wlan1… I don’t know, what I’m doing wrong
It doesn’t work either…
[admin@MikroTik] /interface wireless> /interface wireless set wlan2 master-interface=wlan1 mac-address=02:05:4E:41:BC:83
input does not match any value of master-interface
And I don’t understand, why this is not properly set by Winbox!
1 name=“wlan2” mtu=1500 mac-address=02:05:4E:41:BC:83 arp=enabled master-interface=(unknown) ssid=“hgf” wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no
default-authentication=yes default-forwarding=yes default-ap-tx-limit=0 default-client-tx-limit=0 hide-ssid=no security-profile=default
[admin@MikroTik] /interface wireless> /interface wireless set wlan2 master-interface=wlan1
input does not match any value of master-interface
[admin@MikroTik] /interface wireless>
I would try deleting that entry and try adding another. The default mac should be ok, but if you put more than one VAP on a un-natted net, increment the last number set only for each additional VAP.
ADD: Is wlan1 up and running? I see the band and frequency are the default. We can’t use that frequency here.
We tried to remove/add virtual AP’s many times before without success, that’s why I’m here
The routerboard is here beside me on my working table, so it doesn’t matter what freq I’m using. And you are right - here in CZ we also cannot use this frequency. This board I have only for testing purposes here, I’m trying to develop an API client to read ESSID and frequency from every of our’s Mikrotik radio wlan interface.
The wlan1 is ap-bridge so it doesn’t matter what frequency do I use. And I think I tried to set up czech republic and some proper frequency and ssid without success.
I started to think, that this is some feature. And must have the same conditions as ussual for testing.
edit: and did not have the same MACs: see wlan2=02:05:4E:41:BC:79 vs. wlan1=00:05:4E:41:BC:79
That is incorrect. If you are in ap-bridge mode, it is already transmitting your SSID every 100ms on an illegal frequency. If no antenna, you may be ok if it doesn’t burn the transmitter.
And I have several RB133s set up just like this, but they are all on V2.9.51. I will think about the other problem.
We have boards with 3.14, but these are not RB133. We can’t use RB133 anymore because of lower performace so I have some here on my table for testing my software only.
I have more 433s than 133s now, and one lone RB333, which performs every bit as well as the 433s for its application. Now at uptime=20w6d16h33m46s. They are all on V3.14 also. I have heard, but not tried, that the V3.X OS does not work well on the RB1XX series routers.
This is the key!!! I have tried the RB433 and fw 3.10 and everything worked as expected. Then I tried to upgrade from 3.10 to 3.19 on that radio and everything works also.
Many thanks for help!
It isn’t really considered a bug anymore.
The unfortunate part is the RB133 is now End-Of-Life (EOL), as are many of the earlier RouterBoard series.
That is why I have more RB433s now. I am slowly replacing the 133 units with the superior-performing RB433 at about the same price.
ADD: If downgrade the 133 to V2.9.51, it will work also.
If I downgrade to 2.9.x I will not have an option to use API - the command “/ip service enable api” will be unavailable! I need API for my perl script I use for reading ssid and frequency from the radios.
