Can't wait to try this on my MR33. Thank you @riptide_wave ! (Off-topic: will the MX64 also get support like the MX60 did? Not asking for ETA, just a sense.)

do you have trouble with wifi radio ?

i'm not able to start 1 of them...

From my understanding, 2 of the radios are used to connect through and the 3rd radio is for scanning the environment.  On my MR33, I've disabled radio 0 and enabled radio 1 and 2 with the defaults.    Seems to be working just fine.  Seeing RSSI noise of 30-70 dBm and a Tx rate of up to 900Mbs (which is awesome!)

(Last edited by nonsequitir on 21 Mar 2018, 12:06)

Been running OpenWRT on the MR33 for a couple of days now.  While it's working just fine as an AP (with radio0 disabled and the other two radios set to default), I've noticed the following...

• SSH logins stop working after about 30 minutes or so

• Luci/Httpd stop responding in the same way as SSH

• AP functionality does not appear to be affected when these other services stop working

Has anyone else seen this behaviour?  Can I help with any specific log outputs?

(Last edited by nonsequitir on 21 Mar 2018, 14:24)

Does anyone else get a different response from ubootwrite.py?

Instead of this:

Hello from MR33 U-BOOT
eth0 PHY1 up Speed :1000 Full duplex
Using eth0 device
Listening for TFTP transfer on 192.168.1.1

I get this:

Hello from MR33 U-BOOT
Creating 1 MTD partitions on "nand0":
0x000000c00000-0x000007c00000 : "mtd=0"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smalle

(yes, that's how it ends every time I try)

i try the last snapshot (yesterday 21/03/2018) and 3 radio are working. but still have a curious bug :

sometimes the AP doesn't repond anymore (luci get stuck , no ssh, no ping) i have to switch power off/on ....

(Last edited by eliam on 22 Mar 2018, 11:49)

Quotes are also for replying so...

Awesome Thanks riptide_wave.

(Last edited by riahc3 on 25 Mar 2018, 11:02)

Soldered a 4 pin header to the board.

Reading the instructions and the process looks interesting.

That being said, I think you should add the environment you used. It looks like Linux but did you use a VM, etc.

Makes it easier to replicate.

Thanks.

If you dont get a ping, sounds like a kernel panic.

Do you get any output via serial?

(Last edited by riahc3 on 25 Mar 2018, 20:30)

no, the AP is  not connected any more with the serial.

but i have made some test, and i loose connectivity only when i check the lan component in the wireless parameters.

if i do it with the interface page, no problem...

Any ideas why it doesn't start TFTP server, as shown:

thanks again riptide_wave,

my second mr33 flashed

What environment did you use? Windows or a Linux distro? Physical or virtual?

While I've no problem flashing the MR33 (it works SO GREAT!) I have noticed that the DropBear config file is corrupt (binary stream of garbage).  Deleting it, and replacing it with a default config seems to work.  Just wondering if anyone else has seen this?

I've reflashed the device just now and will hook it up to the LAN and try a recent firmware build to see if it persists.

physical, with windows , tera term and the script to transorm the .py file to tera term macro.

I had the same problem, but if you look at the output from your serial TTL board, you'll see the TFTP server is actually up.

I had another problem though: the ethernet port would drop the connection each time I plugged in the serial board. I didn't even need to use PoE or the power cable to start ubootwrite.py.

Turns out I was using the board at the wrong voltage. Changing the jumper to 3.3V did the trick.

Thanks, I got it working by making sure there's nothing else on the network (sharing a subnet seemed to cause problems). I modified the buffer size from 256 to 1024 in ubootwrite.py in order to see the full output. One time I had to connect via minicom and run tftpsrv manually but subsequent attempts worked ok.

I find that a Raspberry Pi is perfect (correct voltage, easy to connect, easy to use) although I had to swap Rx and Tx wires for some reason.