kar200
April 10, 2025, 7:48pm
44
Hi @EasternMystic ,
Which mac addresses are different from stock? Of which interface?
The issue if I recall correctly was to do with the single wireless interface (DBDC). It needed to create a secondary one.
There a long discussion on the pull request here:
master ← kar200:master
opened 07:32AM - 18 Aug 20 UTC
Specifications:
* SoC: MT7621AT
* RAM: 256MB
* Flash: 128MB NAND flash
* WiF… i: MT7615DN (2.4GHz+5Ghz) with DBDC
* LAN: 5x1000M
* Firmware layout is Uboot with extra 96 bytes in header
* Base PCB is DIR-1360 REV1.0
* LEDs Power Blue+Orange,Wan Blue+Orange,WPS Blue,"2.4G"Blue, "5G" Blue,
USB Blue
* Buttons Reset,WPS, Wifi
lan factory 0xe000 (label - same as stock firmware)
wan factory 0xe006 (same as stock)
2.4 GHz factory 0x4+bitswap (same as stock)
5.0 GHz factory 0x4 (Same as stock)
Flashing instruction:
The Dlink "Emergency Room" cannot be accessed through the reset
button on this device. You can either use console or use the
encrypted factory image availble in the openwrt forum [or here](https://www.mediafire.com/file/z8jmmfz6nwbw1ys/openwrt-21.02.0-rc2-ramips-mt7621-dlink_dir-853-a3-squashfs-factory-enc.bin/file)
The image is 21.02-rc2 encrypted ready to be flashed.
Once the encrypted image is flashed throuh the stock Dlink web
interface, the sysupgrade images can be used.
Header pins needs to be soldered near the WPS and Wifi buttons.
The layout for the pins is (VCC,RX,TX,GND). No need to connect the VCC.
the settings are:
Bps/Par/Bits : 57600 8N1
Hardware Flow Control : No
Software Flow Control : No
Connect your client computer to LAN1 of the device
Set your client IP address manually to 192.168.0.101 / 255.255.255.0.
Call the recovery page or tftp for the device at http://192.168.0.1
Use the provided emergency web GUI to upload and flash a new firmware to
the device
At the time of writing the the wireless config need to be setup by
editing the wireless config file. A sample wireless config file can
be found on the openwrt forum as well.
Signed-off-by: Karim Dehouche <karimdplay@gmail.com>
You can see that Adrian took a wise decision to generate a secondary one. We could not work out what Dlink did at the time.
If you get mac addresses you should be good to go. They dont travel past the first router. The lan and wan should be the same as stock though.
EDIT: If you also look at the DTS you should see where it gets the addresses from.
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
#include "mt7621.dtsi"
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/input/input.h>
#include <dt-bindings/leds/common.h>
/ {
compatible = "dlink,dir-853-a3", "mediatek,mt7621-soc";
model = "D-Link DIR-853 A3";
aliases {
label-mac-device = &gmac0;
led-boot = &led_power_orange;
led-failsafe = &led_power_blue;
led-running = &led_power_blue;
led-upgrade = &led_net_orange;
};
show original