Aura H2O Yet another telnet/sshd & misc tools package...

[OfficerAction]

Originally Posted by NiLuJe

Are you sure you're setting up the interface properly on your end? That vaguely looks like you're attempting to connect to a completely different machine .

(The sshd is the same, there's no reason it'd work over wifi but not usbnet ).

Ok my bad, it turns out I still had a different config for that IP from before

Another thing: htop doesn't show any processes, is that also just me?

[NiMa]

Originally Posted by OfficerAction

Ok my bad, it turns out I still had a different config for that IP from before

Another thing: htop doesn't show any processes, is that also just me?

That happened to me on my Glo HD last week. I had a chroot set up though. When I did get to the chroot shell prompt, it showed all processes with htop and out of the chroot, it showed nothing.
That was strange...

[NiLuJe]

The default config is setup for a dark color theme (e.g., Solarized Dark). Things may be "invisible" in some configurations; try switching the color theme from within htop itself (F2 > Colors).

Extremely exotic (and/or broken) terminal emulators may exacerbate the issue, too (e.g., broken/missing terminfo). (Or stuff that blatantly lies about/break the TERM env var).

Anything xterm compatible should behave, though, and I don't recall any issues in pactice with common terminal emulators on *nix (pretty much all the things that identify as xterm, which is effectively nearly everything these days), macOS (iTerm, Terminal) & Windows (PuTTY).

[OfficerAction]

Thanks for the fast replies. I am using the regular linux terminal. It's not the colors though, I just tried all of them. I can see the text just fine but the processes list is empty. top works as expeted. Very strange

[NiLuJe]

That's... weird, but then there's something wonky going on with the tree view on Kobos since a few htop commits that I haven't had the time to look into...

Does it behave in list view? (F5).

[NiLuJe]

Hmm, might be yet another O_PATH shenanigan because of stupidly old kernels.

I'll double-check... Soon(TM).

[NiMa]

Originally Posted by NiLuJe

Hmm, might be yet another O_PATH shenanigan because of stupidly old kernels.

I'll double-check... Soon(TM).

Ah ... Could explain why it was working on my Libra (4.1) and not on my Glo HD (3.0.35+)

[NiLuJe]

Yeah, it'd be broken on kernels between 2.6.39 and roughly 3.6~3.12.

On Kobo, that means Mk. 6. (Mk. 5 is "safe" because it doesn't support O_PATH at all (2.6.35), and Mk. 7 is safe because it supports O_PATH everywhere. In between, O_PATH itself is supported in open, but breaks a number of fun and useful syscalls if they're fed an O_PATH fd).

[NiLuJe]

Okay, the latest round of updates should have fixed the htop issue on Mk. 6 (and a potentially similar one with libarchive).

Speaking of htop, sorting behaves properly again, too.

[nihilazo]

hi,
When I try and connect to SSH over wifi it works perfectly, but it's slow due to my poor wifi connection, so I'd like to use the USB network. When I toggle USBnet the device shows up on my (linux) PC as "ethernet connection 2" in networkmanager, and it shows a successful message on the kobo display.
This didn't work immediately so I manually added the 192.168.2.* addresses to this interface in networkmanager, and now I can ping my kobo over USB on 192.168.2.2.
However, if I try and SSH into the kobo over USB, I get a message "ssh root@192.168.2.2 port 22: connection refused". over wifi I can connect fine.

[Frenzie]

If you're combining that with the SSH currently shipped with KOReader, keep in mind the port (2222) and such.

[nihilazo]

Originally Posted by Frenzie

If you're combining that with the SSH currently shipped with KOReader, keep in mind the port (2222) and such.

this is using the ssh that comes with the package, do I need to do something to run ssh on usb network after enabling it rather than wifi?

[NiLuJe]

Nope, if it works over Wi-Fi, it works over USBNet.

Which would just imply NM screwed the pooch. I can't tell you much about that, I've never used NM, I just throw an ifconfig at it.

I'm not at my usual box right now, so I don't have it on hand, but the Kindle docs may help figure this out. Be warned that it's probably using a completely different subnet in the examples ^^.
The legacy Kindle docs should be using the same subnet, though, but the docs themselves may be less verbose .

[nihilazo]

Originally Posted by NiLuJe

Nope, if it works over Wi-Fi, it works over USBNet.

Which would just imply NM screwed the pooch. I can't tell you much about that, I've never used NM, I just throw an ifconfig at it.

I'm not at my usual box right now, so I don't have it on hand, but the Kindle docs may help figure this out. Be warned that it's probably using a completely different subnet in the examples ^^.
The legacy Kindle docs should be using the same subnet, though, but the docs themselves may be less verbose .

I tried disabling NM and doing it manually with the ip command (arch considers ifconfig deprecated, but I used the equivalent commands) and I can ping 192.168.2.2 and get a response, which I then don't get if I turn off USBnet on the kobo (so I am assuming that means the kobo is responding to pings and visible on my USB network) however I still get a "connection refused" when trying to connect over SSH or telnet. I get the same if I try and connect to koreader's SSH over usbnet. (this is the same as what happened with NM). I've also tried running ssh as root and that also didn't change anything, so I'm really not sure what is going on here.

[NiLuJe]

Is, per chance, you actual real network on the same subnet? Because that would screw things up...