@gef3233 Look at this post. 
How do I apply the seed once I got the brd file?
Also 6.43.12 is no l onger in the archives of the Mikrotik webpage 
EDIT: Never mind I got the file. Just have to figure o ut how to apply the seed.
Ok, I decrypted using the correct seed (thank you so much by the way! :D) and now I am getting a CRC error.
Any tips on how to overcome this?
[ 2809.620700] wil6210 0000:01:00.0 wlan0: wil_fw_verify: ERR[ FW ]checksum mismatch: calculated for 3588 bytes 0xeb5c4046 != 0xd414aa93
Again, its all written.
You need to manually edit the CRC in the header to one spit by the driver.
Mikrotik does some manual patching in the driver and simply ignores the header
I think I will start writing a wiki article about wireless wire.
I got it, thank you very much!
For anyone struggling with this, find the seed of the file as commented above (or use the one given by robimarko) and then use this file https://gist.github.com/ius/decb73bf9749915d3368218d00eed20c#file-mikrotik_brd_decrypt-py to decrypt.
Then load it on the device and it will tell you the correct CRC:
[ 2809.620700] wil6210 0000:01:00.0 wlan0: wil_fw_verify: ERR[ FW ]checksum mismatch: calculated for 3588 bytes 0xeb5c4046 != 0xd414aa93
In this case the correct CRC is 0xeb5c4046, now just open the file with a hex editor and modify the bytes 93 aa 14 d4 by 46 40 5c eb.
Hope this helps!
Hi all,
I have an additional question. Currently I am "flashing" the initramfs file, but everytime I reboot the device the default Mikrotik OS comes back up. Is there a way of permanently flashing the device with openwrt?
Simply sysupgrade from the initramfs image using the sysupgrade image
Thank you so much! Worked like a charm!
@gef3233
But not the 60 GHz interface, or? Can u start an AP on it, or do a scan?
Hi PolynomialDivision, I have a couple of wAP 60G devices and I am able to successfully start the hostapd and to start the wpa_client on the other device connecting both between them.
I have forked the project and the code and the prebuilt binaries are in https://github.com/IMDEANetworksWNG/Mikrotik-researcher-tools let me know if that helps.
1 Like
Thank u! I will try!
Recently, I had so many problems with ad devices... I even had to disable the wpa_supplicant ubus bindings, because it was crashing wpa_supplicant. I'm really excited to test your branch.
Here is the comment of the bug:
I can not start hostapd
root@OpenWrt:~# hostapd /etc/hostapd.conf -B
Configuration file: /etc/hostapd.conf
Configuration file: -B
Could not open configuration file '-B' for reading.
Failed to set up interface with -B
Failed to initialize interface
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan0 wasn't started
root@OpenWrt:~# hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Using interface wlan0 with hwaddr cc:2d:e0:91:1f:37 and ssid "Mikrotik"
Failed to set beacon parameters
Interface initialization failed
wlan0: interface state COUNTRY_UPDATE->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
wlan0: interface state DISABLED->DISABLED
wlan0: AP-DISABLED
wlan0: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan0 wasn't started
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
ELOOP: remaining socket: sock=16 eloop_data=0xb6ff8d20 user_data=0 handler=0x51288
Neither, I can do a scan
root@OpenWrt:~# iw dev wlan0 scan
scan aborted!Lol. I used a different one and now it seems to work.
root@OpenWrt:~# hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Using interface wlan0 with hwaddr 04:d6:aa:74:32:f9 and ssid "Mikrotik"
wlan0: interface state COUNTRY_UPDATE->ENABLED
wlan0: AP-ENABLEDI am very glad it worked! What do you mean by "used a different one"? Do you mean a different hostapd.conf or openwrt image?
Also the -B goes before the conf file, that is what gave you an error.
@gef3233 Did ever tried this?
BE CAREFULL!!! MAYBE MAKES WIL6210 CHIP UNUSUABLE!!!
If you type in:
ip link set wlan0 up
... the stuff is not working anymore?! And a new tftpboot with it is also not working?!
The device becomes just unusable on OpenWrt?!
But still the link between two stations with original ROS is working?!
No I have not, I use these commands to manage the interface and they work flawlessly:
ifconfig wlan0 192.168.2.1 # Set an IP
ifconfig wlan0 down
ifconfig wlan0 up
Ahhhh bullshit. Sry!
It is the version!!! I have two different versions. One shipped with 6.44.X and one with 6.41.X.
And only the version with 6.41.X is working. There I can do a scan and all things are working smooth!!!
@gef3233 Which version ROS was shipped with your wap 60Gs?