OpenWrt for Zyxel WSM20 (Multy M1) development discussion

For Developers
26

I have to review it by myself when they come to the office. But from what I've read since this is already using openwrt, I think they use in their main UI the basic openwrt upgrading commands, so I think that you can basically flash straight from there.

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

27

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.

29

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

30

@Annick can you issue reboot while in failsafe mode?

32

And this is why we aim for openwrt

2 Likes
33

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.

1 Like
34

andyboeh you are a god ...

after

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#

35

seems the TFTP recovery params are there ...

1 Like
37

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

39

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

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

1 Like
40

can you edit this string?

if you can in a way or another use this sting

root:$1$pjKB26GF$T9mfHI/C6JGX9rQ8CYDPl/

password is openwrt

1 Like
43

that hash is = openwrt
password = openwrt

try admin
try ZyXEL

44

Isn't strange that ! before the hash?

45

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.

2 Likes
46

but you still need know the password

47

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.

48

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

49

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

50

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

51

no he say that worked. he just cannot login