Quote:
Originally Posted by Aleron Ives
Oh, sorry. I misread your post. Maybe Kobo has increased the security level on the current firmware? Developer mode has always been enough by itself to enable telnet for me on 4.35 and earlier.
|
Now that I provided the information you originally suggested that I look for, I turned my attention to my Kobo Elipsa to see if I could login via telnet. I had recently logged back into my main account on it after using my Japanese account, so dev mode had not been reenabled yet. The nm installation had persisted between accounts, however.
1) Attempting to telnet into the Elipsa with neither dev mode nor telnet through nm enabled failed, as expected.
2) Turning dev mode on did not allow me to telnet into the Elipsa. As far as I know, this has always been the case for me. That’s why I looked into nm in the first place years ago. I am running firmware 4.38.21908
3) Enabling telnet via nm allowed me to successfully telnet into the Elipsa
Then for giggles, I enabled sideloaded mode. After successfully entering that mode, and with devmode enabled, I still could not telnet unless I enabled telnet via nm. I don’t have a Kobo with the earlier firmware installed on it, and I have saturated on this particular problem, so I’m unlikely to downgrade my Elipsa’s firmware to compare. at least not today.
I hope my descriptions were thorough enough for you to follow along.
Now, to get this back on topic, here are the iwconfig & iwlist results for my Elipsa.
Notice the full list of channels compared to the Libra Colour’s results. I wonder if there is something here to point to this intermittent WiFi connectivity issue.