Broken Upload with Chromium?

Installing and Using OpenWrt
1

https://openwrt.org/inbox/toh/d-link/dap-x1860

Note: The browser Mozilla Firefox seems to not support the upload fully and users end up with incorrect firmware.bin file sizes. Please try Chrome or Microsoft Edge for the upload instead. To find out, if the uploaded file size is correct, please compare the sha256sum, which is shown upon upload, with the original sha256sum provided by OpenWrt.

I flashed a D-Link DAP-X1860 with openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin

The web interface looks ok but maybe there was something wrong.

I see:
OpenWrt 23.05.2 r23630-842932a63d / LuCI openwrt-23.05 branch git-23.306.39416-c86c256

I used Chromium Version 119.0.6045.159 (Offizieller Build) snap (64-Bit) with Ubuntu 22.04, so I did not pay attention, but now I remember that the shown md5sum was different when uploading from the D-Link website.

$ sha256sum openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin 
ebc0cdab8baf5de5cbaa2231428b9d55336ac08f76f9e484c1739d484a798bc8  openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin

$ md5sum openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin 
290d48f3cd5d60861cbada2928a4810e  openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin

This is from my local files.

So how can I check, if the installed openwrt is ok, since I saw a different md5sum with Chromium?

2

If the installed OpenWrt version is 'good enough' to access via luci/ ssh, just sysupgrade it again with a verified image.

The bootloader based rescue httpd is old and rather picky (pretty much an ie6-only environment), but it's always available - so you could just as well use it again (I'd still go the sysupgrade route first, you can always use this if the former doesn't work).

2 Likes
3

I remembered, that I made a screenshot

checksum
checksum3840×2160 155 KB

13500544 Nov 24 00:44 openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin

So the filesize in the screenshot is the same as with ls, but md5sum is different.

In other words, does this mean, there is no linux-browser to flash it correctly?

I didn't notice any problems, but the ip-address is now in the Fritzbox-net, 192.168.178.53.

Is it recommended to change the IP-address of the openwrt device?

4

I'm just saying that this httpd implementation is very picky, but I still used linux to flash mine (successfully) - and the worst that can happen here, is having to try again (with a different browser/ OS, etc.).

To your second question, you can change IPs and subnets as you like (it probably even makes sense to change both subnets to custom values, to reduce the chances of accidental overlap with new/ factory-reset devices).

1 Like
5

So you recommend to do a sysupgrade with the IP-address I use now, although the file size is the same.

There is not much configured at the moment. I don't like it to change and restart networks for flashing, enabling wifi for posting, a.s.o. There can happen mistakes (by me).

I notice again, that "linux devices" like phones, dvb with custom os are often better flashed with windows. Hard to understand.

6

Because that's what the vendors work on, test and (over-)optimize, they break it the way it is, rather than simply providing standards compliant software.

1 Like
7

Following https://openwrt.org/inbox/toh/d-link/dap-x1860?datasrt=^firmware%20openwrt%20upgrade%20url I downloaded

$ sha256sum openwrt-23.05.0-ramips-mt7621-dlink_dap-x1860-a1-squashfs-sysupgrade.bin
3aa98a21d45715ac59894c6d2d336bd7f7128c493d1348dee8a6e6c582f2666d  openwrt-23.05.0-ramips-mt7621-dlink_dap-x1860-a1-squashfs-sysupgrade.bin

Sorry, I cannot find a checksum on the website.

And the sysupgrade is older than then factory file. 5.2 vs. 5.0

I am confused, where I downloaded the 5.2 file, when I check the website, I see 5.0 too for the factory file.

Browser history says:
https://downloads.openwrt.org/releases/23.05.2/targets/ramips/mt7621/openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-factory.bin

Searching the download path there is https://downloads.openwrt.org/releases/23.05.2/targets/ramips/mt7621/

and

https://downloads.openwrt.org/releases/23.05.2/targets/ramips/mt7621/openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-sysupgrade.bin

$ sha256sum openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-sysupgrade.bin
42f2152d9df0be881b5e3acd6f331f5cf7667df4cf5ef21a020a4fc9f3599bf5  openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-sysupgrade.bin

I assume this is the file I want, but why I can't find this as link at the device page?

8

Hope that everything is ok now. Note, a constant green light on the device, doesn't mean that the device has booted fully. I had to wait longer.

Following https://openwrt.org/docs/guide-user/installation/sysupgrade.cli I used ssh and scp.

root@X1860-K1M:/tmp# sha256sum openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-
squashfs-sysupgrade.bin 
42f2152d9df0be881b5e3acd6f331f5cf7667df4cf5ef21a020a4fc9f3599bf5  openwrt-23.05.2-ramips-mt7621-dlink_dap-x1860-a1-squashfs-sysupgrade.bin

root@X1860-K1M:/tmp# free
              total        used        free      shared  buff/cache   available
Mem:         250340       58268      168324        6796       23748      152228
Swap:             0           0           0

root@X1860-K1M:/tmp# sysupgrade -v /tmp/openwrt-23.05.2-ramips-mt7621-dlink_dap-
x1860-a1-squashfs-sysupgrade.bin 
Wed Nov 15 02:03:23 UTC 2023 upgrade: Saving config files...
etc/config/dhcp
etc/config/dropbear
etc/config/firewall
etc/config/luci
etc/config/network
etc/config/rpcd
etc/config/system
etc/config/ucitrack
etc/config/uhttpd
etc/config/wireless
etc/dropbear/authorized_keys
etc/dropbear/dropbear_ed25519_host_key
etc/dropbear/dropbear_rsa_host_key
etc/group
etc/hosts
etc/inittab
etc/luci-uploads/.placeholder
etc/nftables.d/10-custom-filter-chains.nft
etc/nftables.d/README
etc/opkg/keys/b5043e70f9a75cde
etc/passwd
etc/profile
etc/rc.local
etc/shadow
etc/shells
etc/shinit
etc/sysctl.conf
etc/uhttpd.crt
etc/uhttpd.key
Wed Nov 15 02:03:23 UTC 2023 upgrade: Commencing upgrade. Closing all shell sessions.
Command failed: Connection failed
root@X1860-K1M:/tmp# Connection to 192.168.178.53 closed by remote host.
Connection to 192.168.178.53 closed.
1 Like
9

Hmmm, I've been trying to flash Openwrt on my DAP-x1860 but so far unable to enter the recovery mode. Do I only need to enter the IP on the host pc or do I need to enter additional information?

Steps:

  1. Download the openWRT factory image. (E.g. via https://firmware-selector.openwrt.org)
  2. Connect to the repeater with ethernet cable.
  3. Enter recovery mode. (Hold RESET button, before plugin in the repeater, until orange power light starts blinking)
  4. In Chrome open http://192.168.0.50 (maybe you have to set an manual IP to your PC in the 192.168.0.x range)
  5. Upload factory.bin
  6. Wait a couple of minutes.
  7. You should now be able to acess LuCI at http://192.168.1.1
10

Ah wait, had to set the gateway to 192.168.0.50, now flashing.

Should actually be added to the device page or is it that obvious that it's not needed?

11

As already mentioned, the color was red here after I did a reset with the original firmware. Be careful when entering IP-address, gateway and dns. I made a mistake here after flashing openwrt.

12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.