QUOTE(kwss @ Jul 26 2024, 07:00 PM)
How TM block D-Link Web UI with OMCIThis is a continuation to work done by
Anime4000.
In his custom firmware, he just restart the boa process to keep the Web UI functioning.
With some reverse engineering, I have figured out how it happens.
The offending code is loaded inside /bin/startup. It checks for MIB 517 (0x205).
The pseudo code is as follow:
CODE
 iVar2 = read_pid("/var/run/boa.pid");
 if (iVar2 < 0) {
  iVar2 = mib_get(0x205,&local_10);
  if (iVar2 == 0) {
   uVar1 = va_niced_cmd(&WEBSERVER,0,0);
   local_c = local_c | uVar1;
  }
  else if (local_10 == 1) {
   uVar1 = va_niced_cmd(&WEBSERVER,1,0,"-n");
   local_c = local_c | uVar1;
  }
  else if (local_10 == 2) {
   uVar1 = va_niced_cmd(&WEBSERVER,1,0,"-s");
   local_c = local_c | uVar1;
  }
  else {
   uVar1 = va_niced_cmd(&WEBSERVER,0,0);
   local_c = local_c | uVar1;
  }
 }
So technically any OLT can push that MIB and your Web UI will disappear, at least for the D-Link.
Exactly! haha, restart boa (Embedded WebGUI) is simplest method without patching the bin
you can make Firmware contain patches and removal of IoT stuff.
I still keep firmware chroot/repack at my GitHub, just modify a bit to work with ARM64 chroot instead of MIPS32. I believe D-Link RTL9607DQ use xz compression, the repack routine should be automatically detect which compression algorithm squashfs using.
making and compile own ARM64 binary should be easy too, you can find /bin/nijika a simple printf(); 🤣
I leave it to you for making D-Link DPN-FX3060 not suck 😬