Skip to content
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

comitup-cli x #214

Open
qwksilver opened this issue Sep 4, 2022 · 3 comments
Open

comitup-cli x #214

qwksilver opened this issue Sep 4, 2022 · 3 comments
Labels

Comments

@qwksilver
Copy link

comitup-cli x

version 1.38-1 from apt-get on buster, manual install
buster is 2021-05-07-raspios-buster-armhf
stock from pi image no upgrade (upgrade not doable at this time (it breaks other things for me))
bullseye no doable for same reason

my understanding is that the x command deletes all current connections, and resets the comitup returning it to hotspot state
currently x does nothing visable, and the hotspot returns, sill connected to last connection.

comitup-cli d x
is what i am using instead, but it likely is only deleting current connection, and not all connections.

if this is correct sorry for the issue entry, if this is not correct, thank you for your help.

@davesteele
Copy link
Owner

"comitup-cli d x" will delete the current connection. The argument is ignored.

The nuke option requires that enable_nuke is enabled in the configuration file (the command is dangerous, and not useful for most).

The connections are managed by NetworkManager. You can view them with "nmcli con" and delete one with "nmcli con del x".

@qwksilver
Copy link
Author

ah, can you elaborate as to what makes the nuke option dangerous.

a slightly unrelated question too:
is there a preferred deactivation procedure that doesn't take comitup completely out of the unit, but would allow the gui to manage connections?

@davesteele
Copy link
Owner

It's just dangerous in that can delete bunches of connections, and is easy to activate from comitup-cli.

The preferred deactivation procedure is to stop or disable the comitup.service systemd service. Current active connections are preserved, but it won't interfere with any changes you make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants