htop has been broken for a while. The workaround is easy but annoying:
Code:
root@Async:~# export TERM=xterm
root@Async:~# htop
// working htop
root@Async:~#
See post https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1290444#1290444 for details. Broken in Windows, macOS and Debian (both GNOME and xfce). _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Last edited by TCB13 on Sun Oct 22, 2023 18:53; edited 2 times in total
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Fri Sep 29, 2023 8:45 Post subject:
there was a thread how to fix it (htop).... if im not wrong...not gonna waste time finding it sharing it as im too busy atm...
otherwise it works ok using putty...you can install Putty either on win or linux...no clue for MacOS..sorry..
I use htop on all my routers from my sig...(740 is excluded as it doesn't have an USB) some either have it preinstalled or you can use the entware package manager and install it manually... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Obviously this doesn't happen if I try to use htop in a generic Debian server. This only happens with DD-WRT boxes and has been happening for more than a year now.
In other words, fix your client programs or use PuTTY, it's *NOT* a DD-WRT issue.
PuTTY is available for Windows, Linux, and MacOS (via Homebrew or MacPorts).
Thank you, come again. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Last edited by kernel-panic69 on Fri Sep 29, 2023 10:35; edited 1 time in total
In other words, fix your client programs or use PuTTY, it's *NOT* a DD-WRT issue. PuTTY is available for Windows, Linux, and MacOS (via Homebrew or MacPorts). Thank you, come again.
C'mon how is this a "client issue" if it fails in all major clients that happen to work just fine with any other Linux system?
What are you even suggesting? PuTTY is the only one that is right? That the official HTOP/SSH Daemon in all Linux systems have specific hacks to enable all client to work fine besides PuTTY? lol
And in case you didn't read the first post, I know about the "export TERM=xterm" workaround, have been doing it for a long time. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Fri Sep 29, 2023 10:48 Post subject:
TCB13 wrote:
C'mon how is this a "client issue" if it fails in all major clients that happen to work just fine with any other Linux system?
What are you even suggesting? PuTTY is the only one that is right? That the official HTOP/SSH Daemon in all Linux systems have specific hacks to enable all client to work fine besides PuTTY? lol
And in case you didn't read the first post, I know about the "export TERM=xterm" workaround, have been doing it for a long time.
After upgrading to OSX Lion, I started getting this error on certain (Debian/Ubuntu) servers. The fix is simply to install the “ncurses-term” package which provides the file /usr/share/terminfo/x/xterm-256color.
Setting the TERM environment variable (to "xterm-color", "xterm", "vt220", "vt100", "putty", "dumb" ...) is possibly the simplest solution. You only lost colors... _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
After upgrading to OSX Lion, I started getting this error on certain (Debian/Ubuntu) servers. The fix is simply to install the “ncurses-term” package which provides the file /usr/share/terminfo/x/xterm-256color.
Setting the TERM environment variable (to "xterm-color", "xterm", "vt220", "vt100", "putty", "dumb" ...) is possibly the simplest solution. You only lost colors...
I can't treat something that only happens with DD-WRT as a generic errors. Again no issues with htop under any other Linux box.
kernel-panic69 wrote:
And there are ways to make the workaround persistent, as already noted twice. Do the hacks, test. I'm not going to bother Sebastian with this.
Why is this only "broken" under DD-WRT? Why does it work with every other Linux? _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
