TP-Link EAP Series experiences

I don’t move configs ever, to much headache and compatibility issues.
Use uci-defaults insted.
And only make as little and minimum required changes as possible in the image because there is no backup if you screw this up in the actual firmware.

The rest of configs you do on a working system!

Everything you do in imagebuilder should have manually been tried on a working setup at first if it doesn’t work then it surely won’t work if you burn it to the memory.

I have two devices of each I use just to handle the blood pressure when they crash. A lot of users here should also have more devices since it is good for the health.

You can solder a connector for serial as wiki describes, I haven’t done that yet because I didn’t feel worried because I have been doing OpenWRT for almost four years now on three different devices so is wasn’t really any unknowns to setup this device.

1 Like

Once flashed with the openwrt firmware, do they include the already activated “openwrt” WiFi ssid for setup?

The ssid is there as usual but OpenWRT never has a wifi activated.

I read that in the quick start guide just after I posted that probably gonna have to look into how to rub the UCI Defaults on fist boot then in order to get into the config page after installing the firmware.

I haven’t installed OpenWRT yet, because both my boxes apparently have problems with the wifi chip mt76xx. Some have given up hope but I’m holding my breath since there’s attempts going on to fix it.

Which EAP do you have?

EAP235-Wall and EAP245-v3

Master already has a newer mt76 driver that should fix the MT7613 issue. So does 21.02 HEAD but you'll have to wait for the next point release for images that include it (or compile it yourself).

I'm running the EAP235-Wall with 21.02 HEAD and it works just fine now for me. Main one (for three of which two in service) has been up for 18 days (basically since last update) and my wife does video calls all day for work.

1 Like

No issues with stability or video calls stuttering badly? Also how was the install process? Did you need to do anything outside of normal OpenWRT setup for an AP?

The commit has full installation instructions:

That's all you need. No complaints about stability personally. You can still revert to stock if needed. Instructions in that very same commit.

I’ve been running 21.02 and subsequently 21.02.1 more recently on two EAP245v3’s since each version was released, haven’t had any issues to date, very happy overall.

Followed instructions on the device page to install from factory firmware to 21.02.


Good I might have to give this a try then. I’ve always liked openwrt and the price for the APs was/is very good for what you get. It’s too bad the software side of it is lacking.

I’ve been running openwrt on two EAP225s now for a few days but I’ve been having issues enabling 802.11r for some devices which leaves them unable to connect. Is anyone else having issues enabling 802.11r on some devices with this build 21.02?

Yeah, at least here I remember various users having reported similar issues:

I am using 802.11r with openwrt and have no issues with archer c7 and some other devices. I remember when I set it up, I was a little bit confused about the setup and experienced issues until it was properly set. At least all tp-link devices which I use, 802.11r works. I hope eap series is no exclusion as well as I am interested in how cpe series performs with openwrt.

I've got eap225-outdoor, eap235-wall and eap-245 for testing, would be bad if 802.11r does not work.

@moderators if this thread is actually the same, please feel free to close/delete it.

EDIT: Does anybody know if there is difference in eap series for EU firmware for different EU countries, how do I know if it is for Germany, Switzerland, Austria,France,Spain..? I backed up original, I am just curious if there is any difference as support page for different eu countries shows different versions.

Tp-link has only one firmware for EU. TP-link has no country selection in firmware to begin with. For OpenWRT you don’t need to care about countries in EU devices. Set country to driver default then you get EU original wifi speed.

1 Like

For my issue with 802.11r, it came down to a different rom on the specific android device. That is/was more rom development related than anything. I have turned 802.11r back on, on my TP-Link devices. Along with Dawn, it’s working pretty well. Only time will tell.

Thanks for the reply, I did think the same that there is no difference but thinking is not knowing. It seems there is difference, if on german tp-link more than one firmware is available and looking at austrian, there is only one. I did not go further to check other EU countries but would assume, like in germany, that there might be differences in radio and maybe some other beside language settings, however, the reason to know it was simply for ability to flash back original firmware downloaded from tp-link, sure I backed up original firmware, however, I kinda dislike the need to manage and keep those files or links, that's why I asked as on the package one can see only the EU but not for which EU country it is intended. Probably tp-link can reply better why they offer different firmwares for different EU countries.

@stansmith good to hear it works well, you can use it without Dawn which is a little ressource heavy.

That could as well just be such vendor's ignorance resp. stupidity.

I have noticed in the past that TP-Link will list different availabe firmware versions for different locales (regions). However, if you look at the same version for two region, you'll see that they actually identical (e.g. checksums). The US and EU firmwares are even identical, but there is a config partition on the device that indicates in what region it should operate.

That being said, don't upgrade to a Canadian firmware. Those will turn your device into a Canadian. CA firmwares have an extra piece of metadata that is checked on FW upgrades, preventing it from installing the universal FW.