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.

Sign up for GitHub

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

Jump to bottom

Axiom breaks with DO if any droplet has a reserved IP #613

Open
sudo-jtcsec opened this issue Sep 13, 2022 · 1 comment
Open

Axiom breaks with DO if any droplet has a reserved IP #613

sudo-jtcsec opened this issue Sep 13, 2022 · 1 comment

Comments

@sudo-jtcsec
Copy link

After spinning up a new DO fleet, I kept getting sshconfig errors when launching scans such as below:

/root/.axiom/tmp/gau 16631043189022/sshconfig line 7: no argument after keyword "167.172.x.y"
/root/.axiom/tmp/gau 16631043189022/sshconfig: terminating, 2 bad configuration options
error with number of instances, exiting

Looking at my .axiom/.sshconfig file, I found an entry was scuffed:

Host recon-automation-manager-vm
        HostName 137.184.x.y
167.172.x.y
167.172.x.y
        User op
        Port 2266

The issue persisted after I fixed the config file manually - Im assuming its checked in the background and will repush the bad config.

More investigation shows that for a DO droplet not in my fleet I configured a reserved IP, which I believe is being returned in a query for VM IPs as an unexpected additional entry, which then breaks the sshconfig generation.
@sudo-jtcsec sudo-jtcsec mentioned this issue Sep 13, 2022
Open
@thapr0digy
Copy link

Just recently ran into this, but also think it might be good to only create new sshconfig for droplets that have been created by axiom. I worked around this by creating a new "instances_axiom()" function in do-functions.sh. I'll try and submit a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@thapr0digy @sudo-jtcsec