Remote-admin moments2 #99

Closed
opened 2026-10-05 03:21:14 +02:00 by adam · 12 comments
Owner

It seems there is no check if node had access at all or request something.
It shows whole remote menu, But user settings shown asis, even allow change something, but for sure it is not saved.
Same for modules - external notifications, it shows some default, not real data readed from remote node.

It seems there is no check if node had access at all or request something. It shows whole remote menu, But user settings shown asis, even allow change something, but for sure it is not saved. Same for modules - external notifications, it shows some default, not real data readed from remote node. <!-- github-sync-id:4980323760 -->
adam closed this issue 2026-10-05 03:21:14 +02:00
Author
Owner

maybe fixed in bfd20bfa49

maybe fixed in bfd20bfa4960d7c3ce7e36290c0d7fee4f441a4e <!-- github-comment-id:5084625788 -->
Author
Owner

maybe fixed in bfd20bf

No it is not.
Now remote admin started faster with no long wait, but no real check or data retrieval happens.
It shows some default values no matter what is really and is particular node can be managed or not.

> maybe fixed in [bfd20bf](https://github.com/pdxlocations/contact/commit/bfd20bfa4960d7c3ce7e36290c0d7fee4f441a4e) No it is not. Now remote admin started faster with no long wait, but no real check or data retrieval happens. It shows some default values no matter what is really and is particular node can be managed or not. <!-- github-comment-id:5085030503 -->
Author
Owner

Hm.
It seems it depends of what node is used via which interface.
Cheking.

Hm. It seems it depends of what node is used via which interface. Cheking. <!-- github-comment-id:5085058594 -->
Author
Owner

It seems there is a difference when app uses remoteadm via wifi connection or the local via port.

It seems there is a difference when app uses remoteadm via wifi connection or the local via port. <!-- github-comment-id:5085163362 -->
Author
Owner

Hm, dunno what is going on, but when i added key of my wifi node into new nodes it started working fine.

Is there any cache or something for the old\nodes when no key were added?

Hm, dunno what is going on, but when i added key of my wifi node into new nodes it started working fine. Is there any cache or something for the old\nodes when no key were added? <!-- github-comment-id:5085300932 -->
Author
Owner

Hm, dunno what is going on, but when i added key of my wifi node into new nodes it started working fine.

it is expected behavior to need your pub key in the admin field of the remote node.

Is there any cache or something for the old\nodes when no key were added?

were you successfully adminng a node that didn't have your pub key?

> Hm, dunno what is going on, but when i added key of my wifi node into new nodes it started working fine. it is expected behavior to need your pub key in the admin field of the remote node. > Is there any cache or something for the old\nodes when no key were added? were you successfully adminng a node that didn't have your pub key? <!-- github-comment-id:5085317230 -->
Author
Owner

were you successfully adminng a node that didn't have your pub key?

Not really, it successfully passed test for remote admin you were added.
But menu shown were mostly default values except user settings.

> were you successfully adminng a node that didn't have your pub key? Not really, it successfully passed test for remote admin you were added. But menu shown were mostly default values except user settings. <!-- github-comment-id:5085326333 -->
Author
Owner

I was expecting same behaviour as meshtastic cli or android app when it just refuses to show menu when no connection to the remote node can be made without key.

I was expecting same behaviour as meshtastic cli or android app when it just refuses to show menu when no connection to the remote node can be made without key. <!-- github-comment-id:5085330985 -->
Author
Owner

No, you are correct, it's not behaving how it was intended to.

No, you are correct, it's not behaving how it was intended to. <!-- github-comment-id:5085367116 -->
Author
Owner

maybe fixed in ac90b4af3e

maybe fixed in ac90b4af3ec2dda337ebfe6a5acfe5e5c59f40b6 <!-- github-comment-id:5085403057 -->
Author
Owner

maybe fixed in ac90b4a

seems better
I have removed key from remote node and app have reverted to the issue i reported with menu defaults still shown from remote node.

But when i restarted contact app, now checks works and it refuses access for me when requesting remote.

> maybe fixed in [ac90b4a](https://github.com/pdxlocations/contact/commit/ac90b4af3ec2dda337ebfe6a5acfe5e5c59f40b6) seems better I have removed key from remote node and app have reverted to the issue i reported with menu defaults still shown from remote node. But when i restarted contact app, now checks works and it refuses access for me when requesting remote. <!-- github-comment-id:5085734518 -->
Author
Owner

Great, I'll mark this closed for now!

Great, I'll mark this closed for now! <!-- github-comment-id:5085747445 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/contact#99