-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asuswrt cannot connect over ssh #20361
Comments
Same issue with Hass.io raspberrypi3 Operating environment |
OpenSSL is not a part of HASS, however what is the output of |
I'm getting the same error after upgrading from 0.85.1 to 0.86.0, downgrading back to 0.85.1 works right away. |
Not sure if related, but do any of you also use HomeKit? There was a homekit component update that upgraded a cryptography package: #20325 |
I have the same error but do not use homekit. Downgrading helped |
Issue still present with 0.86.1 |
I confirm that on 0.86.1 the issue exists. It didn't on 0.85.1. |
Running Hassio on RPi3B+ Same issue, asuswrt died going from 0.85.1 to 0.86.0 says invalid configuration. I never got telnet to work but ssh has be pretty solid and going back to 0.85.1 fixes it immediately. I tried telnet again before falling back and it's still broken as well. I have ssh access only available by LAN in my router config to eliminate outside access so I'm not using a key. In my configuration.yaml asuswrt: |
Same here. It is annoying that it it broken again. |
Same here :) |
Same. Downgrade and working again. |
I belive it is very popular component and device tracking system and I don't understand why it is getting broken almost every time there is update. I love HA regardles but it make life hard sometimes especially when there is a lot of automation based on device tracking. Is there any workaround?? (apart of downgrading - I like lovelace :)) |
You could temporarily use bluetooth as a tracker if you have it available but for me it just doesn't have the range, I have a big house so WiFi made more sense. |
Same here 😁 |
I am having the same issue. |
Unfortunetely I cannot find better presence tracker than asuswrt - when it is working 😉 |
Same issue here. Using SSH, not using a key. Just user/pass as it is all only accesible from LAN. |
same problem. |
Same here. AsusWRT worked on 0.85.1, quit working upon upgrading to 0.86.1 |
same here, ok on 0.85.1, stopped working on 0.86.1, rpi3b+, docker, ssh |
same issue here, using ssh key to log in |
Telnet is broken aswell... at least for me |
For telnet I'd have to see your logs, please open an issue here: github.com/kennedyshead/aioasuswrt/issues/ For the ssh issue I'm 90% sure it have to do wit ssh-key and running in docker. A temporary solution would be to login without key for now and re-enable it when the problem in Hassio is solved. |
Several people in this thread, including me, are not using ssh_key. |
I just tried switching to telnet to eliminate OpenSSL from the picture and got the following:
|
Have you set port 23? |
Yes I am, here's the relevant config, sorry I forgot to include that:
|
@glentakahashi Oh i see :) |
+1 |
Same error on 0.86.2 |
Could someone please test |
That seems to have fixed the Edit: Did this fix for anybody else? I had duplicated the |
Is this problem solved? |
How can I try that fix on hassos? Sorry but I don't know how to use it. |
It should be fixed, it is merged so hopefully we can get a 0.86.3 release soon with this included. |
Note that the underlying root cause of this is that HASS.io uses alpine:3.8 which is based on musl libc and not glibc. This means |
Seeing this in 0.86.2 still. |
+1, alas. Not using key, plain SSH username/password.
|
@olskar did this make it into the .3 release? The release notes state otherwise. |
I confirm that the issue is still present in .3. Just updated and rebooted. |
not in .3, frustrating this major bug is being ignored |
Put https://github.com/kennedyshead/home-assistant/blob/20d929b3883c4ce374dfa6dd93caebede5792bd4/homeassistant/components/asuswrt.py in custom_components reboot and try again |
Hi @kennedyshead. I tried as per your advice and rebooted, but the error is still there. |
Ok, then we need to wait for the hassio fix of openssl. Not sure why libnacl dont work. Edit: now I get it, there has been a change i asyncssh to use pyCA instead of libnacl. You could use an earlier version of asyncssh if you know howto. |
Thanks, @kennedyshead. I'd rather not "cook" too much my prod Hassio installation. Will wait for the official fix. |
Is it possible this didn't make it into the build because the status of this issue is set to "Closed"? |
Both SSH and Telnet not working with 86.3, hopefully 86.4 comes out with a fix for ASUSWRT. Until then I'll manually have to do what my presence detection automation was setup to do. Hopefully it gets resolved quickly |
me too,not work in 0.86.3 |
Please lock this issue, it is taken cared of in hassio! Note that the underlying root cause of this is that HASS.io uses alpine:3.8 which is based on musl libc and not glibc. This means manylinux1 wheels do not work. So while cryptography==2.3.1 is installed and does actually support X25519, the way HASS.io builds it (against an old alpine version of openssl) means some features get turned off. On Debian and Ubuntu the manylinux1 wheel is used, so all the features of cryptography==2.3.1 are present and accounted for. |
@kennedyshead When you say it is taken care of in Hassio are you saying they updated to use glibc and in the next release it should be fixed? I'm just not quite sure if you are saying 1. It's not a bug 2. It is a bug and there is a work around out there or 3. It's fixed in the next (or a future release). |
Home Assistant release with the issue:
0.86.0b3
Last working Home Assistant release (if known):
0.85.1
Operating environment (Hass.io/Docker/Windows/etc.):
Docker raspberrypi3-homeassistant
Component/platform:
https://www.home-assistant.io/components/asuswrt/
Description of problem:
the asuswrt component can no longer connect over ssh, instead throwing an error about X25519 not being supported on this version of openssl. This applies to both password and key authentication.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: