FS#830 - No SSH Access to Device TP-Link MR3420 V2 (even in failsafe) #5849
Labels
Comments
|
arjendekorte: This is a known problem with dropbear and GCC7 (see FS#814). |
|
None: There's a known 'disagreement' between gcc 7, mips, dropbear & '-Os' optimisation. You could: Not compile with gcc 7. Or compile with gcc 7 but set the target optimisation flags from '-Os' to '-O2'. Whether this is a gcc 7 bug, or a bug in an older 'libtommath/crypt' exposed by gcc 7 isn't clear. |
|
nouman8: how to set -Os flag to -O2 ? |
|
arjendekorte: See http://lists.infradead.org/pipermail/lede-dev/2017-May/007843.html |
|
nouman8: off-topic: will ar71xx devices get 4.9 kernel anytime soon? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nouman8:
Yesterday i reported bug #828 which was fixed few hours later so i build toolchain from git trunk sources successfully on my Archlinux machine. on make menuconfig i selected profile tp link mr3420 v2 and only changed gcc toolchain version to 7.x and images were build successfully. i flashed sysupgrade image and lost ssh access to the router i could ping 192.168.1.1 but when trying ssh root@192.168.1.1 it shows "ssh: connect to host 192.168.1.1 port 22: Connection refused" and even in FAILSAFE mode it shows the same error..
so i opened the router for serial access and run top command process "dropbearkey -t rsa -f /tmp/d" was running non stop with 100% cpu utilization...after that i reboot into the bootloader and flashed daily snapshot for mr3420v2 which restored ssh access.
The text was updated successfully, but these errors were encountered: