IPQ4019: Adding support for TP-Link Deco M5

no prob I'll update again, probably need to build but use the same trick to get it working on swconfig (by manually defining switch setting as hinted on this thread earlier). So far the only sure working VLAN is 19.07 from https://github.com/frankveltmans/openwrt/commit/e96d10cda60d13ec2e1ca5f7e9acad6ba8467520

Hey guys,

Being a while since I stopped using openwrt/lede.

I'm having a hard time trying to configure some stuff in my decos and was wondering what is the current state of the firmware for it. Is it working fine? What are the advantages of switching to lede that you found? Any downside? Any performance gain?

Performance-wise some here said no diff. VLANs still not supported (not like it's much better in stock), but all the benefits of OpenWRT.

Oh I see, thanks for the reply :slight_smile:

1 Like

I've been trying to get this from freanveltmans working but I just can't figure it out. I think someone mentioned that it's missing Luci. I can build it, I can flash the unit, it seems to come up, I get an IP but when I go to that IP the browser doesn't get anything. So it does look like it's missing a gui. Any tips for adding Luci?

before you build it select luci using make menuconfig. you can check the openwrt guides they have all the commands for building and customising your build. I add WireGuard, DDNS amongst other stuff I use to my build :slight_smile:

Ok I think I got it but something strange, Luci is up and running but I'm missing the devices tab beside interface. I also don't have the switches menu option. I must be missing a few things.

hi!

firstly, if your using freanveltmans's build, its from 19.07 there will be no DSA. The others here shared that DSA is not supported anyway. So, there will be no "Devices" tab.

secondly, as shared on this thread, you need to define the switch in network config before it appears in Luci. This is how I do it, but I'm not sure it's entirely correct as I can only define vlans for 1 of the 2 ports like this, but here goes:


config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'

config switch_vlan
option device 'switch0'
option ports '0t 5t'
option vlan '10'


all the best!

Ohhhh ok! Thanks for your help, I'm still very new to Openwrt as well as networking in general. I didn't realize the devices tab was part of DSA but now that makes sense!

1 Like

Glad to see it's been working great for everyone, just a screenshot for my case, 26 days uptime, both wifi radios smoothly functioning with 802.11k/v/r and 3 APs, as well the router with WireGuard

Just another update... WireGuard pushes about touching 10MB /s with loads of just under 1.90 .... yet to confirm if the CPU or the remote broadband is the limiting factor

@jprafael Did you get your problem sorted?

I am asking because I had the blinking blue light as well and I wasnt able to to connect to the device, turns out my ethernet cable was hooked up to the wrong port (it has to be connected to the port which is closes to the power cable), the thing it that the tftp works fine if its on the other port but once openwrt is running it configures that port as wan and thus is not reachable in the 192.168.1.1 ip

1 Like

Hi, can anybody share build binary? I tried to port https://github.com/openwrt/openwrt/pull/4309/files to branch openwrt-21.02 but no luck so far :confused:

Sent you a message with a link to compiled binary

1 Like

Thank you @Tomer

I've managed to port changes from PR to branch 21.02 and build the image.

I have one problem though, with performance of the lan over the cable.

In one direction I have almost 1Gbit, but in oposite direction barely 100Mbit.

Connecting to host 192.168.1.103, port 5201
[  5] local 192.168.1.133 port 35404 connected to 192.168.1.103 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   108 MBytes   902 Mbits/sec    0    342 KBytes       
[  5]   1.00-2.00   sec   112 MBytes   944 Mbits/sec    0    342 KBytes       
[  5]   2.00-3.00   sec   112 MBytes   943 Mbits/sec    0    441 KBytes       
[  5]   3.00-4.00   sec   111 MBytes   934 Mbits/sec    0    345 KBytes       
[  5]   4.00-5.00   sec   112 MBytes   944 Mbits/sec    0    351 KBytes       
[  5]   5.00-6.00   sec   111 MBytes   933 Mbits/sec    0    342 KBytes       
[  5]   6.00-7.00   sec   110 MBytes   923 Mbits/sec    0    348 KBytes       
[  5]   7.00-8.00   sec   112 MBytes   944 Mbits/sec    0    354 KBytes       
[  5]   8.00-9.00   sec   112 MBytes   944 Mbits/sec    0    351 KBytes       
[  5]   9.00-10.00  sec   111 MBytes   933 Mbits/sec    0    348 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  1.09 GBytes   934 Mbits/sec    0             sender
[  5]   0.00-10.01  sec  1.08 GBytes   927 Mbits/sec                  receiver

iperf Done.
➜  rpi4-arch iperf3 -s              
-----------------------------------------------------------
Server listening on 5201 (test #1)
-----------------------------------------------------------
Accepted connection from 192.168.1.103, port 33442
[  5] local 192.168.1.133 port 5201 connected to 192.168.1.103 port 33444
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  19.8 MBytes   166 Mbits/sec                  
[  5]   1.00-2.00   sec  4.17 MBytes  35.0 Mbits/sec                  
[  5]   2.00-3.00   sec  9.64 MBytes  80.9 Mbits/sec                  
[  5]   3.00-4.00   sec  9.30 MBytes  78.0 Mbits/sec                  
[  5]   4.00-5.00   sec  8.31 MBytes  69.7 Mbits/sec                  
[  5]   5.00-6.00   sec  2.67 MBytes  22.4 Mbits/sec                  
[  5]   6.00-7.00   sec  3.77 MBytes  31.6 Mbits/sec                  
[  5]   7.00-8.00   sec  6.29 MBytes  52.7 Mbits/sec                  
[  5]   8.00-9.00   sec  6.21 MBytes  52.1 Mbits/sec                  
[  5]   9.00-10.00  sec  5.22 MBytes  43.8 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.00  sec  75.3 MBytes  63.2 Mbits/sec                  receiver
-----------------------------------------------------------
Server listening on 5201 (test #2)
-----------------------------------------------------------

My openwrt config:


config interface 'loopback'
	option device 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fd2d:ef7e:c838::/48'

config device
	option name 'br-lan'
	option type 'bridge'
	list ports 'eth0'
	list ports 'eth1'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option netmask '255.255.255.0'
	option ipaddr '192.168.1.198'
	option delegate '0'

config device
	option name 'eth0'

config device
	option name 'eth1'

config interface 'lan1'
	option type 'bridge'
	option proto 'static'
	option ipaddr '192.168.1.197'
	option netmask '255.255.255.0'
	option device 'br-lan'
1 Like

Hi, can anybody share build binary? I can't compile a file in github. PleaseπŸ˜….

Sent you a link with my compiled version

1 Like

Does anyone have a working VLAN config they can share? Currently have a basic swconfig - but it's not working as I would expect.
I'm trying to set up a single port with 2 Wifi VLANs, but no matter what I try, all I achieve is dropping all access to the router :frowning_face: - even when I try and set up just a basic wired vlan.

That isn't really specific to this device. If you still want untagged traffic to be able to reach the device via a port then you have to keep the interface for it around. So even if you have eth1.123 and eth1.456 as two different VLANs interfaces you still need an interface with eth1 as its physical interface. And it needs to have an IP and shouldn't be unmanaged.

Hello good, I would like to try openwrt in my deco m5, sorry for my English but I am using google translator.
My decos are the following:
EU / 1.0
EU / 1.1

I do not know how to compile a firm I have no idea but if there was a manual of the steps I could follow it, or a binary which could update it as it is in the case of another netgear device that I have.

thanks greetings