https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v
    well i can
  • v
    and i still can't figure it out
  • v
    because each tunnel need to be named after both peers names otherwise you get into naming clashes
  • v
    e.g. they can't all be named wg0
  • v
    each tunnel is named after my peer
  • v
    right
  • v
    so that's this bit: @@wireguard::interface { 'curie':
  • v
    or, if you will, @@interface { $hostname: }
  • v
    or whatever
  • v
    the problem i have is with the public_key field
  • v
    you can't export the right one, because you haven't realized that yet
  • v
    well you did, but you don't know you did, see what i mean?
  • v
    like later i would Interface <<| |>> { addresses => ... }
  • v
    but that doesn't tell me what the name of the peer is so i can reuse it in (say) dig($facts, 'wireguard_keys', $peer)
  • v
    does that make sense?
  • v
  • v
    right, so everything is hardcoded
  • v
    well not everything, but the pubkey and the peer names and endpoints
  • v
    I would probably try this without exported resources, but with PQL queries
  • v
    oh dear, this is not going to work at all... i can't have the same address on all those tunnels
  • v
    why not?
  • v
    can't i?
  • v
    on the local machine? yes you can
  • v
    oh neat
  • v
    okay, so that should work
  • v
    i just need to figure out the pubkey stuff then
  • v
    tip: internet routers do that since 30 years and it works well on linux
  • v
    just looks odd :D
  • v
  • v
    all my wireguard interfaces on one box have the same IPv4 and IPv6 IP. it's a naming convention. that allows me also to calculate the ip for peers
1...177178179...648Latest