search

enowars / bambictf

Ansible/Packer/Terraform setup for our Bambi CTF on Hetzner Cloud
MIT License
11 stars 3 forks source link

One checker was not connected to the internal network #38

Closed Trolldemorted closed 3 months ago

Trolldemorted commented 1 year ago

I had to manually execute wg-quick up internal. How is it supposed to be started automatically?

Trolldemorted commented 1 year ago

@ldruschk any clue?

Trolldemorted commented 1 year ago

We should have listened to the first rule of tech support. DNS does not propagate quickly enough, the wrong address is resolved, and wg does not re-resolve (?)

cc @ldruschk @MMunier

ldruschk commented 1 year ago

Do you remember how you started everything? This is what this internal_floating_ip_only setting is used for.

https://github.com/enowars/bambictf/blob/a33bfbb02509d06278479e79f9f16d7aedcaa988/terraform/bambictf.tf#L49

You should first start the setup with this setting enabled so that the floating IPs and DNS records are created and have time to propagate. But I do agree that this should be documented somewhere

Trolldemorted commented 1 year ago

I think we always set internal_floating_ip_only to false, because we got errors when it was on the default value. Never truly understood what the setting does, and it wasn't documented as you said 😇

ldruschk commented 3 months ago

Can this be closed? I don' see us getting any more insights into this issue soon @Trolldemorted