Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion

Two wall test:

  1. rt5010w-d350_rev0.bin
Connecting to host 192.168.1.1, port 5201
[  5] local 192.168.1.183 port 50376 connected to 192.168.1.1 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  38.4 MBytes   322 Mbits/sec    0   1.51 MBytes       
[  5]   1.00-2.00   sec  40.0 MBytes   336 Mbits/sec    0   2.12 MBytes       
[  5]   2.00-3.00   sec  41.2 MBytes   346 Mbits/sec    0   2.68 MBytes       
[  5]   3.00-4.00   sec  38.8 MBytes   325 Mbits/sec    0   3.00 MBytes       
[  5]   4.00-5.00   sec  42.5 MBytes   356 Mbits/sec    0   3.00 MBytes       
[  5]   5.00-6.00   sec  42.5 MBytes   357 Mbits/sec    0   3.00 MBytes       
[  5]   6.00-7.00   sec  38.8 MBytes   325 Mbits/sec    0   3.00 MBytes       
[  5]   7.00-8.00   sec  42.5 MBytes   356 Mbits/sec    0   3.00 MBytes       
[  5]   8.00-9.00   sec  43.8 MBytes   367 Mbits/sec    0   3.00 MBytes       
[  5]   9.00-10.00  sec  36.2 MBytes   304 Mbits/sec    5   2.10 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   405 MBytes   339 Mbits/sec    5             sender
[  5]   0.00-10.01  sec   402 MBytes   337 Mbits/sec                  receiver

iperf Done.
Connecting to host 192.168.1.1, port 5201
Reverse mode, remote host 192.168.1.1 is sending
[  5] local 192.168.1.183 port 41582 connected to 192.168.1.1 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  51.5 MBytes   432 Mbits/sec                  
[  5]   1.00-2.00   sec  53.5 MBytes   449 Mbits/sec                  
[  5]   2.00-3.00   sec  55.8 MBytes   468 Mbits/sec                  
[  5]   3.00-4.00   sec  53.3 MBytes   447 Mbits/sec                  
[  5]   4.00-5.00   sec  54.5 MBytes   457 Mbits/sec                  
[  5]   5.00-6.00   sec  47.3 MBytes   396 Mbits/sec                  
[  5]   6.00-7.00   sec  55.5 MBytes   465 Mbits/sec                  
[  5]   7.00-8.00   sec  55.7 MBytes   468 Mbits/sec                  
[  5]   8.00-9.00   sec  52.5 MBytes   440 Mbits/sec                  
[  5]   9.00-10.00  sec  57.6 MBytes   483 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.01  sec   541 MBytes   453 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   537 MBytes   451 Mbits/sec                  receiver

iperf Done.
  1. GoldenBin_20210323.bin
Connecting to host 192.168.1.1, port 5201
[  5] local 192.168.1.183 port 53326 connected to 192.168.1.1 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  39.5 MBytes   331 Mbits/sec    0   1.76 MBytes       
[  5]   1.00-2.00   sec  38.8 MBytes   325 Mbits/sec    0   2.41 MBytes       
[  5]   2.00-3.00   sec  43.8 MBytes   367 Mbits/sec    0   2.91 MBytes       
[  5]   3.00-4.00   sec  41.2 MBytes   346 Mbits/sec    0   3.07 MBytes       
[  5]   4.00-5.00   sec  41.2 MBytes   346 Mbits/sec    0   3.07 MBytes       
[  5]   5.00-6.00   sec  41.2 MBytes   346 Mbits/sec    0   3.07 MBytes       
[  5]   6.00-7.00   sec  40.0 MBytes   336 Mbits/sec    0   3.07 MBytes       
[  5]   7.00-8.00   sec  43.8 MBytes   367 Mbits/sec    0   3.07 MBytes       
[  5]   8.00-9.00   sec  41.2 MBytes   346 Mbits/sec    0   3.07 MBytes       
[  5]   9.00-10.00  sec  41.2 MBytes   346 Mbits/sec    0   3.07 MBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   412 MBytes   346 Mbits/sec    0             sender
[  5]   0.00-10.01  sec   410 MBytes   343 Mbits/sec                  receiver

iperf Done.
Connecting to host 192.168.1.1, port 5201
Reverse mode, remote host 192.168.1.1 is sending
[  5] local 192.168.1.183 port 46608 connected to 192.168.1.1 port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  68.2 MBytes   572 Mbits/sec                  
[  5]   1.00-2.00   sec  72.3 MBytes   607 Mbits/sec                  
[  5]   2.00-3.00   sec  69.7 MBytes   584 Mbits/sec                  
[  5]   3.00-4.00   sec  63.4 MBytes   532 Mbits/sec                  
[  5]   4.00-5.00   sec  63.1 MBytes   529 Mbits/sec                  
[  5]   5.00-6.00   sec  63.7 MBytes   535 Mbits/sec                  
[  5]   6.00-7.00   sec  62.3 MBytes   523 Mbits/sec                  
[  5]   7.00-8.00   sec  60.8 MBytes   510 Mbits/sec                  
[  5]   8.00-9.00   sec  62.2 MBytes   522 Mbits/sec                  
[  5]   9.00-10.00  sec  63.0 MBytes   529 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.02  sec   652 MBytes   545 Mbits/sec    0             sender
[  5]   0.00-10.00  sec   649 MBytes   544 Mbits/sec                  receiver

iperf Done.

But this is just a quick test...

2 Likes

Its impossible to say what the ODM intended, do note that they multiple similar boards with a single image

This available as source?

Can BDF files be edited? @Ansuel was changing regdb inside them.

The package was manually prepared.
BDF files can be found in the firmware: https://dl46.askeycloudapi.com/file/dynalink/RT5010W-D350/DL-WRX36/1.10.01.254/Dynalink-RT5010W-d350-V1.10.01.254_sysupgrade_nand_img.bin
You can unpack it e.g. like this: docker run --rm -v .:/data/output -v .:/data/input ghcr.io/onekey-sec/unblob /data/input/Dynalink-RT5010W-d350-V1.10.01.254_sysupgrade_nand_img.bin and prepare board-2.bin using ath11k-bdencoder.

2 Likes

So I take that this is part of the closed source of the WiFi FW? Where to push to in a custom build ?

Why are we using docker to unpack?

unblob is written in Python. You probably didn't know that. Otherwise you'd know better than to ask that question. Here, I'll let Randall explain:
xkcd: Python Environment

6 Likes

This made me laugh.

But I still don't understand why docker and not native python or is this applicable to window users or because we need to run a specic version (older) ver. of python

Using docker is easier because you don't need to install (often even compile) the required dependencies. But this is just an individual preference.
Even binwalk is available as a docker image: https://hub.docker.com/r/refirmlabs/binwalk

3 Likes

Basically, what @lytr said.

A more involved explanation (laced with an opinion, though I know I'm not the only one holding it) would be that, although Python is a great language for ducktyping a quick and handy prototype or shell script, and it has an enormous, thriving ecosystem, it's performance leaves much to be desired (it is even slower than PHP), which is why most performance-critical Python projects depend on components written in serious languages, such as C, C++, or, lately, Rust. This, coupled with the shitshow that is Python dependency management, means that getting a project run on a native Python installation may turn out to be, to put it mildly, a bit... finicky.

So, once you've managed to painstakingly pull all the oddly Python-shaped pieces and native binaries together into a working whole, to ensure a low-hassle deployment on user systems, you might be better off by putting the whole shebang in a Docker container. Which is exactly what the unblob team does.

It was just last week when we ran into this problem rather painfully at my work.

We had all been happily using the notorious cassandra-migrate tool to update the local (Docker, mostly) instances of the namesake DBS on our work machines, when, after a long-overdue distro upgrade from Ubuntu 22.10 to 23.04, it just stopped working. Evidently some Python dependency/version mismatch. Nothing we tried was working (and I probably borked my systemwide Python installation), so, being pressed for time, we did just the above — pulled the Docker image that we're using to run DB migrations in our CI/CD pipelines, wrapped it in a thin POSIX shell script, and called it a day.

Moral of the story: Docker is reliable. Unlike Python.

3 Likes

this all makes me think if I should have maybe.. backed up the firmware before adding openwrt to keep the calibration data.

This is my experience with Python as well... In fact, I'm using a tool atm to address this issue the name of which escapes me... I'll dig it up Edit: Conda. Thanks for the in-depth.

1 Like

Openwrt uses exactly the same radio calibration used by dynalink FW.
If you go back to dynalink fw it will be like it was when bought.

Okay, so, experiencing a new issue...

I have 3xDL-WRX36 that host 4 VLAN 5Ghz ssid and 1 VLAN 2.4Ghz.

Upon a fresh reboot, all ssid function fine, without internet. Then after a while, VLAN_134 (192.168.134.0/24) No longer can ping 8.8.8.8 nor resolve google.com or other.

DL-WRX36_Log_1:


Sun Sep 17 01:50:25 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Sep 17 01:50:25 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: associated (aid 1)
Sun Sep 17 01:50:25 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED c1:91:44:b5:a0:af auth_alg=ft
Sun Sep 17 01:50:27 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 10:d5:61:27:c1:89
Sun Sep 17 01:50:32 2023 kern.warn kernel: [18634.487996] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
Sun Sep 17 01:50:32 2023 daemon.info hostapd: phy1-ap0: STA 10:d5:61:27:c1:89 IEEE 802.11: authenticated
Sun Sep 17 01:50:40 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED c1:91:44:b5:a0:af
Sun Sep 17 01:51:15 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: authenticated
Sun Sep 17 01:51:15 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: associated (aid 13)
Sun Sep 17 01:51:15 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED c1:91:44:b5:a0:af auth_alg=open
Sun Sep 17 01:51:15 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af WPA: pairwise key handshake completed (RSN)
Sun Sep 17 01:51:15 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED c1:91:44:b5:a0:af
Sun Sep 17 01:53:31 2023 daemon.warn odhcpd[2242]: No default route present, overriding ra_lifetime!
Sun Sep 17 01:53:52 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED c1:91:44:b5:a0:af
Sun Sep 17 01:54:18 2023 daemon.info hostapd: phy1-ap0: STA 10:d5:61:27:c1:89 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Sep 17 01:54:42 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: authenticated
Sun Sep 17 01:54:42 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: associated (aid 6)
Sun Sep 17 01:54:42 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED c1:91:44:b5:a0:af auth_alg=open
Sun Sep 17 01:54:42 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af WPA: pairwise key handshake completed (RSN)
Sun Sep 17 01:54:42 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED c1:91:44:b5:a0:af
Sun Sep 17 01:55:15 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED c1:91:44:b5:a0:af
Sun Sep 17 01:55:18 2023 daemon.warn odhcpd[2242]: No default route present, overriding ra_lifetime!
Sun Sep 17 01:55:21 2023 daemon.notice hostapd: phy0-ap2: AP-STA-DISCONNECTED 16:84:f7:08:48:a8
Sun Sep 17 01:55:21 2023 daemon.info hostapd: phy0-ap2: STA 16:84:f7:08:48:a8 IEEE 802.11: disassociated due to inactivity
Sun Sep 17 01:55:22 2023 daemon.info hostapd: phy0-ap2: STA 16:84:f7:08:48:a8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Sep 17 01:55:39 2023 authpriv.info dropbear[7544]: Child connection from 192.168.129.70:38052
Sun Sep 17 01:55:39 2023 authpriv.notice dropbear[7544]: Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:null from 192.168.129.70:38052
Sun Sep 17 01:55:47 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Sun Sep 17 01:55:47 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: associated (aid 1)
Sun Sep 17 01:55:47 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED c1:91:44:b5:a0:af auth_alg=ft
Sun Sep 17 01:56:02 2023 daemon.err uhttpd[7597]: [info] luci: accepted login on / for root from 192.168.129.70

DL-WRX36_Log_2:

Sun Sep 17 01:50:43 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: disconnected due to excessive missing ACKs
Sun Sep 17 01:50:43 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED c1:91:44:b5:a0:af
Sun Sep 17 01:50:48 2023 kern.warn kernel: [18649.768001] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
Sun Sep 17 01:50:49 2023 daemon.info hostapd: phy1-ap0: STA 10:d5:61:27:c1:89 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Sep 17 01:51:13 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Sep 17 01:51:55 2023 daemon.warn odhcpd[2245]: No default route present, overriding ra_lifetime!
Sun Sep 17 01:53:29 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: authenticated
Sun Sep 17 01:53:29 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: associated (aid 18)
Sun Sep 17 01:53:29 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED c1:91:44:b5:a0:af auth_alg=open
Sun Sep 17 01:53:29 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af WPA: pairwise key handshake completed (RSN)
Sun Sep 17 01:53:29 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED c1:91:44:b5:a0:af
Sun Sep 17 01:53:59 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED c1:91:44:b5:a0:af
Sun Sep 17 01:54:04 2023 kern.warn kernel: [18846.328003] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 4
Sun Sep 17 01:54:46 2023 daemon.warn odhcpd[2245]: No default route present, overriding ra_lifetime!
Sun Sep 17 01:55:08 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED d8:1f:12:a8:c4:6d
Sun Sep 17 01:55:13 2023 kern.warn kernel: [18915.047998] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 12
Sun Sep 17 01:55:13 2023 daemon.notice hostapd: phy1-ap0: STA d8:1f:12:a8:c4:6d IEEE 802.11: did not acknowledge authentication response
Sun Sep 17 01:55:20 2023 daemon.info hostapd: phy1-ap0: STA d8:1f:12:a8:c4:6d IEEE 802.11: authenticated
Sun Sep 17 01:55:20 2023 daemon.info hostapd: phy1-ap0: STA d8:1f:12:a8:c4:6d IEEE 802.11: associated (aid 16)
Sun Sep 17 01:55:20 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED d8:1f:12:a8:c4:6d auth_alg=open
Sun Sep 17 01:55:20 2023 daemon.info hostapd: phy1-ap0: STA d8:1f:12:a8:c4:6d WPA: pairwise key handshake completed (RSN)
Sun Sep 17 01:55:20 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED d8:1f:12:a8:c4:6d
Sun Sep 17 01:55:46 2023 authpriv.info dropbear[7722]: Child connection from 192.168.129.70:40332
Sun Sep 17 01:55:46 2023 authpriv.notice dropbear[7722]: Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:null from 192.168.129.70:40332
Sun Sep 17 01:56:06 2023 daemon.err uhttpd[7774]: [info] luci: accepted login on / for root from 192.168.129.7

DL-WRX36_Log_3:

Sun Sep 17 01:49:16 2023 daemon.warn odhcpd[2240]: No default route present, overriding ra_lifetime!
Sun Sep 17 01:49:58 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: authenticated
Sun Sep 17 01:49:58 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: associated (aid 11)
Sun Sep 17 01:49:58 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED c1:91:44:b5:a0:af auth_alg=open
Sun Sep 17 01:49:58 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af WPA: pairwise key handshake completed (RSN)
Sun Sep 17 01:49:58 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED c1:91:44:b5:a0:af
Sun Sep 17 01:50:49 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: disconnected due to excessive missing ACKs
Sun Sep 17 01:50:49 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED c1:91:44:b5:a0:af
Sun Sep 17 01:50:54 2023 kern.warn kernel: [18656.168130] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
Sun Sep 17 01:51:19 2023 daemon.info hostapd: phy1-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sun Sep 17 01:53:55 2023 daemon.warn odhcpd[2240]: No default route present, overriding ra_lifetime!
Sun Sep 17 01:54:32 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: authenticated
Sun Sep 17 01:54:32 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: associated (aid 1)
Sun Sep 17 01:54:32 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED c1:91:44:b5:a0:af auth_alg=open
Sun Sep 17 01:54:32 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af WPA: pairwise key handshake completed (RSN)
Sun Sep 17 01:54:32 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED c1:91:44:b5:a0:af
Sun Sep 17 01:54:34 2023 daemon.warn odhcpd[2240]: No default route present, overriding ra_lifetime!
Sun Sep 17 01:55:50 2023 authpriv.info dropbear[7726]: Child connection from 192.168.129.70:39410
Sun Sep 17 01:55:50 2023 authpriv.notice dropbear[7726]: Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:null from 192.168.129.70:39410
Sun Sep 17 01:56:00 2023 daemon.info hostapd: phy0-ap3: STA 16:84:f7:08:48:a8 IEEE 802.11: authenticated
Sun Sep 17 01:56:00 2023 daemon.info hostapd: phy0-ap3: STA 16:84:f7:08:48:a8 IEEE 802.11: associated (aid 1)
Sun Sep 17 01:56:00 2023 daemon.notice hostapd: phy0-ap3: AP-STA-CONNECTED 16:84:f7:08:48:a8 auth_alg=open
Sun Sep 17 01:56:00 2023 daemon.info hostapd: phy0-ap3: STA 16:84:f7:08:48:a8 WPA: pairwise key handshake completed (RSN)
Sun Sep 17 01:56:00 2023 daemon.notice hostapd: phy0-ap3: EAPOL-4WAY-HS-COMPLETED 16:84:f7:08:48:a8
Sun Sep 17 01:56:02 2023 daemon.info hostapd: phy0-ap0: STA c1:91:44:b5:a0:af IEEE 802.11: disconnected due to excessive missing ACKs
Sun Sep 17 01:56:02 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED c1:91:44:b5:a0:af
Sun Sep 17 01:56:08 2023 kern.warn kernel: [18969.368147] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 1
Sun Sep 17 01:56:18 2023 daemon.err uhttpd[7778]: [info] luci: accepted login on / for root from 192.168.129.70

"Disable Inactivity Polling" is enabled
Time interval for rekeying GTK: 600
Station inactivity limit: 300
Maximum allowed Listen Interval:65535
Disassociate On Low Acknowledgement: Enabled
I believe IPV6 is disabled on dumb AP and Main, so not sure why no route in relation to ipv6 is in the log

The 3xDL-WRX36 are Dumb AP. Routing is done on WRT1900ACS.

Lastly, device "c1:91:44:b5:a0:af" ismy laptop MAC address and I am connected to the ssid with an ip, yet, no apparent internet activity

Update: Appears to just intermittently stop/start again;

[cloud@rog ~]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.134.1 icmp_seq=1 Destination Port Unreachable
From 192.168.134.1 icmp_seq=3 Destination Port Unreachable
From 192.168.134.1 icmp_seq=4 Destination Port Unreachable
From 192.168.134.1 icmp_seq=8 Destination Port Unreachable
From 192.168.134.1 icmp_seq=9 Destination Port Unreachable
From 192.168.134.1 icmp_seq=13 Destination Port Unreachable
64 bytes from 8.8.8.8: icmp_seq=15 ttl=117 time=26.8 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=117 time=21.0 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=117 time=31.7 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=117 time=18.3 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=117 time=158 ms
64 bytes from 8.8.8.8: icmp_seq=20 ttl=117 time=17.0 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=117 time=19.3 ms

This laptop is 8 ft away from the DL-WX36 AP. Should add, connected by 2.4Ghz here

############################

Same behavior on another VLAN, this time 5Ghz;

PING 192.168.130.1 (192.168.130.1) 56(84) bytes of data.
From 192.168.130.1 icmp_seq=3 Destination Port Unreachable
From 192.168.130.1 icmp_seq=4 Destination Port Unreachable
From 192.168.130.1 icmp_seq=8 Destination Port Unreachable
From 192.168.130.1 icmp_seq=9 Destination Port Unreachable
From 192.168.130.1 icmp_seq=12 Destination Port Unreachable
From 192.168.130.1 icmp_seq=13 Destination Port Unreachable
From 192.168.130.1 icmp_seq=14 Destination Port Unreachable
From 192.168.130.1 icmp_seq=18 Destination Port Unreachable
From 192.168.130.1 icmp_seq=19 Destination Port Unreachable
^C
--- 192.168.130.1 ping statistics ---
19 packets transmitted, 0 received, +9 errors, 100% packet loss, time 18224ms

[cloud@rog ~]$ ping google.com
PING google.com (146.112.61.104) 56(84) bytes of data.
64 bytes from hit-block.opendns.com (146.112.61.104): icmp_seq=1 ttl=58 time=17.2 ms
64 bytes from hit-block.opendns.com (146.112.61.104): icmp_seq=2 ttl=58 time=17.1 ms
64 bytes from hit-block.opendns.com (146.112.61.104): icmp_seq=3 ttl=58 time=17.9 ms
64 bytes from hit-block.opendns.com (146.112.61.104): icmp_seq=4 ttl=58 time=17.7 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 17.133/17.486/17.887/0.323 ms
[cloud@rog ~]$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=20.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=19.5 ms

Why does it fail initially, but eventually start up again?

I would like to mount rootfs_1's squqshfs while we have booted with root from rootfs mtd partition. I tried using ubiattach command first, then ubiblock command to create block device like /dev/ubiblock1_[0,1,2].
Finally I used "mount -t squashfs /dev/ubiblock1_1 /mnt". I got error message:
/dev/ubiblock1_1: Can't open blockdev

Has anybody tried this steps?