maybe i plugged it on the wrong port or something else (pretty new to all this)? I connected the laptop to the WAN port of the router 
Thanks for your help, hoping to unbrick it soon enought 
And what does laptop say about the port state?
what do you mean? the dnsmasq terminal?
I mean the literal physical port state
ifconfig says that Ihe IP set up on the laptop is good (broadcast on 0.0.0.0?).
The port seems to be blinking (this crap laptop doesn't have those lovely green and orange LEDs...) I will try again tomorrow on another laptop (it 10:35pm here and I have exams tomorrow )
as for the dnsmasq just in case:
Again, the physical state, like what does IP link say?
The router nor the crapy laptop have à y LEDs so i can't tell you rn. I Will try with another Linux computer tomorrow
I mean the literal: ip link command
I've done tftp recovery from Mac without any problem. Connect via ethernet cable, configure static IP & subnet mask for lan interface (macOS GUI Network settings), then run dnsmasq.
Just a quick question, is the transmission power with this openwrt experimental build as powerful as the transmission power of the original Chinese fw?
How did you get dnsmasq on Mac ? (or how did you configuré it ?) I installé it via brew but dont know how to do with thé config files)
I Will retry both from Mac and two Linux machines at school in about 2hours)
Thx to you and @robimarko for your help !
Sorry robi for yesterday I got to bed before seeing your answer, I didn't even know that ip link is a command 
Hm.. UDP timeout is 120 sec, TCP timeout (for established) is 7440 sec, and it seems these values do apply correctly, as the conntrack tabale does not contain any entries outside of these values. It is clearly not a router side issue, more like transmission is not closing the idling sessions as it should...
Can somebody give me a quick answer regarding the transmission power?
You are aware that just spraying 30dBm isn't legal pretty much anywhere?
2 Likes
I'm back, flashing raspberryOS and I will be ready to go to try again and give you the ip link result. sorry for the wait.
I am aware, but it is legal where I live... (North America) - so does this build support it or not?
1 Like
On 5GHz or 2.4GHz?
@robimarko here are the results, unfortunatly even changing the linux doesn't help
the interface used is enp0s25.
ubuntu@ubuntu:/tmp/tftp$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 3c:97:0e:41:db:ea brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 60:67:20:b7:c7:04 brd ff:ff:ff:ff:ff:ff
ubuntu@ubuntu:/tmp/tftp$ ifconfig
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.31.100 netmask 255.255.255.0 broadcast 0.0.0.0
ether 3c:97:0e:41:db:ea txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5 bytes 441 (441.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf2500000-f2520000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 5570 bytes 514247 (514.2 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5570 bytes 514247 (514.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.4.105 netmask 255.255.255.0 broadcast 192.168.4.255
inet6 fe80::6792:7395:b4d6:ee83 prefixlen 64 scopeid 0x20<link>
ether 60:67:20:b7:c7:04 txqueuelen 1000 (Ethernet)
RX packets 45236 bytes 49718214 (49.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 33394 bytes 5520300 (5.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Wait, do you have UART write support?
Cause if so then you can just use OpenWrt to recover
I don't really know I have to confess, the UART is plugged in, screen is detecting my keypresses (and the usb too (blue LED blinking at each key) but the router doesn't wait on boot for me to interupt so I'm clueless...