OpenWrt for Zyxel WSM20 (Multy M1) development discussion

frollic · 2023-03-14T11:54:13.263Z

SirLouen:

What I'm not confident if it would be possible to trigger a TFTP without soldering.

that's the part I've been trying to figure out, uboot is more future proof, since most vendors won't update it once the device is shipped, while you can add new checks in a stock fw upgrade.

ercolino · 2023-03-14T12:53:49.278Z

frollic:

I assume there's output, but u-boot ignores the buttons ...

i had the same problem on a device, and that was a bad cable or adapter not sure. replaced and worked.

hecatae · 2023-03-14T13:03:16.656Z

@Annick can you issue reboot while in failsafe mode?

SirLouen · 2023-03-14T15:20:20.023Z

Annick:

OEM firmware very poor
configuration only fine with smartphone ( Multy app ) !!!
no DFS channels possibility
no igmpproxy for TV

And this is why we aim for openwrt

andyboeh · 2023-03-14T17:00:06.202Z

Annick:

i can modify nothing because folder & files are read only

That's supposed to be that way. Can you issue some of the other generic OpenWrt failsafe commands like mount_root? This should give you full access to all files.

Annick · 2023-03-14T18:09:49.537Z

andyboeh you are a god ...

after

OpenWrt Wiki – 1 Oct 16

Failsafe Mode, Factory Reset, and Recovery Mode

Failsafe Mode, Factory Reset, and Recovery Mode OpenWrt offers several ways to “start over” with your router. * Failsafe Mode is useful if you have lost control of your device, and it has become inaccessible, perhaps through a configuration...

cd /overlay upper/etc/config
i can run mount_root and i can modify file

i edit network and good modified ip after reboot

another command exist

root@(none):/usr/sbin# fw_printenv
bootcmd=mtkautoboot
bootmenu_0=Startup system (Default)=mtkboardboot
bootmenu_1=Upgrade firmware=mtkupgrade fw
bootmenu_2=Upgrade bootloader=mtkupgrade bl
bootmenu_3=Upgrade bootloader (advanced mode)=mtkupgrade bladv
bootmenu_4=Load image=mtkload
bootmenu_5=Upgrade mtkfirmware=mtkupgrade mtkfw
fdtcontroladdr=8ffeb890
ipaddr=10.10.10.123
serverip=10.10.10.3
stdin=serial
stdout=serial
stderr=serial
serialnum=S220Y42575
countrycode=E1
ethaddr=D4:1A:D1:16:3C
wifiwpapsk=FJVVJN4474
bootmenu_delay=0
root@(none):/usr/sbin#

frollic · 2023-03-14T18:44:41.642Z

Annick:

ipaddr=10.10.10.123
serverip=10.10.10.3

seems the TFTP recovery params are there ...

andyboeh · 2023-03-14T18:56:20.745Z

The password is in /etc/shadow, not /etc/passwd. Try running passwd after mount_root

ercolino · 2023-03-14T21:25:51.818Z

if you want go this way that's the hash you need compare

$1$UZX6JR4v$LkdBJWrYiTd/3cRsJWLdy1
that's and md5crypt hash

ercolino · 2023-03-14T21:35:40.222Z

Annick:

root:!$1$UZX6JR4v$LkdBJWrYiTd/3cRsJWLdy1:19430:0:99999:10:::

can you edit this string?

if you can in a way or another use this sting

root:$1$pjKB26GF$T9mfHI/C6JGX9rQ8CYDPl/

password is openwrt

ercolino · 2023-03-15T06:13:05.927Z

Annick:

login name possible not root ?

that hash is = openwrt
password = openwrt

try admin
try ZyXEL

SirLouen · 2023-03-15T08:49:54.916Z

Annick:

root:!$1$UZX6JR4v$LkdBJWrYiTd/3cRsJWLdy1:19430:0:99999:10:::

Isn't strange that ! before the hash?

patient0 · 2023-03-15T09:02:11.646Z

The ! means the account login using a password is disabled, see shadow(5).

If the password field contains some string that is not a
           valid result of crypt(3), for instance ! or *, the user will
           not be able to use a unix password to log in (but the user
           may log in the system by other means).

Remove it (only the !) to enable login.

ercolino · 2023-03-15T09:41:01.351Z

patient0:

Remove it (only the !) to enable login.

but you still need know the password

patient0 · 2023-03-15T09:49:38.875Z

Of course @ercolino you're right. But you can generate a password yourself:

Manually generate password for /etc/shadow or search the internet for 'linux shadow generate password'.

add: And you provided already a hash in an earlier post, that should work.

frollic · 2023-03-15T10:18:14.856Z

patient0:

But you can generate a password yourself:

that would assume the shadow file is writable though, doesn't it ?

patient0 · 2023-03-15T10:20:10.756Z

Yes indeed but I assume sometime earlier in the thread mounting writable was possible with mount_root as mentioned by @andyboeh .

frollic · 2023-03-15T10:25:38.201Z

yet he failed, but it might be caused by the ! in shadow.

ercolino · 2023-03-15T10:33:02.327Z

frollic:

yet he failed

no he say that worked. he just cannot login

frollic · 2023-03-15T10:43:43.800Z

ercolino:

no he say that worked. he just cannot login

yeah, might have misinterpreted ....