enowars/bambictf

One checker was not connected to the internal network

Closed this issue · 5 comments

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

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

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

internal_floating_ip_only = var.vpn_floating_ip_only || var.internal_floating_ip_only

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

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 😇

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