Modify

Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#13349 closed task (not_a_bug)

Root password configuration failed for OM2P image - r29397

Reported by: s13884neo@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version:
Keywords: root password, om2p, base-file Cc:

Description

I have been trying to build the custom firmware for OM2P with root password. Used OpenWRT Revision 29397 as om2p.patches are already included.

I have tried to setup root password in image but couldn't work. I have tried many methods as mentioned in following links but none of them are working for me. It does not allow me to login to router after flashing with new firmware.
/ticket/10422.html
/ticket/6369.html
/ticket/10537.html
https://forum.openwrt.org/viewtopic.php?id=22360
https://forum.openwrt.org/viewtopic.php?id=38072

Is that any other method to build root filesystem with default password for openwrt? Anyone please help to resolve the same?

Attachments (0)

Change History (6)

comment:1 Changed 5 years ago by anonymous

I have tried to flash the om2p using sysupgrade. I think, we can preserve the necessary files while upgrading so we can save old passwd and shadow files to save old password configuration. But sysupgrade don't appear to be working for om2p, got following message while using sysupgrade.

root@5_1_102_104:/tmp# sysupgrade -v openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Sysupgrade is not yet supported on om2p.
Image check 'platform_check_image' failed.
So latest sysupgrade version supports om2p flash?

I have tried to connect the om2p using telnet after upgrading with custom image and refusing connection.
http://wiki.openwrt.org/toh/openmesh/om2p
Tried both ap51-flash and mtd method but unable to login.

comment:2 Changed 5 years ago by s13884neo@…

sysupgrade supports for om2p added to OpenWRT latest version (35433). We can upgrade the om2p using latest sysupgrade.

comment:3 Changed 5 years ago by Sandip Sitapara <s13884neo@…>

Password hash works with OpenWrt r35433.

What I did for default password
mkpasswd -m md5 password

Output:
$1$i0V.Eugk$VBFRBmxOrQMuKn7Mit2DP0

I have used md5 method to generate password hash as om2p uses the same.

If your password hash start with $6$ than use md5 -m sha-512 to generate password hash

Use mkpasswd to generate password hash using md5 and copy that password to <trunk>/package/base-files/files/etc/shadow. The shadow file looks like
root:$1$i0V.Eugk$VBFRBmxOrQMuKn7Mit2DP0:0:0:99999:7:::
daemon:*:0:0:99999:7:::
ftp:*:0:0:99999:7:::
network:*:0:0:99999:7:::
nobody:*:0:0:99999:7:::

Run make command to build image. Once make is completed you can find the openwrt-ar71xx-generic-om2p-squashfs-factory.bin image in <trunk>/bin/ar71xx directory. Connect router to your system on eth0/eth1 and run following command to flash router.

ap51-flash eth0 openwrt-ar71xx-generic-om2p-squashfs-factory.bin (OM2P is connected on eth0 so interface should be eth0)

Once flash is completed power cycle the om2p. It should be up with default IP 192.168.1.1 and assign ip to your connected system's ethernet then try to connect using ssh root@192.168.1.1 and use password you configured while building image.

comment:4 Changed 5 years ago by Sandip Sitapara <s13884neo@…>

There was a mistake in previous comment for following line
<<If your password hash start with $6$ than use md5 -m sha-512 to generate password hash>>

Correct one:
If your password hash start with $6$ than use -m sha-512 to generate password hash

comment:5 Changed 5 years ago by nbd

  • Resolution set to not_a_bug
  • Status changed from new to closed

comment:6 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.