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

console / wireguard: add support for network #3051

Open
Tailzip opened this issue Nov 19, 2023 · 1 comment
Open

console / wireguard: add support for network #3051

Tailzip opened this issue Nov 19, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Tailzip
Copy link

Tailzip commented Nov 19, 2023

fly doesn't support setting --network flag for fly console and fly wireguard like it does for fly apps create. Therefore, it's impossible to connect to machines' 6PN address if launched in a custom network.

It looks like GraphQL API support for creating wireguard peer in given network exists:

input AddWireGuardPeerInput {
  # [...]

  # Network ID to attach wireguard peer to
  network: String

  # [...]
}

For reference, support for apps has been added in #563.

@Tailzip Tailzip added the bug Something isn't working label Nov 19, 2023
@Tailzip Tailzip changed the title console / wireguard: add support for app's network console / wireguard: add support for network Nov 19, 2023
@owenthereal
Copy link

I just ran into this issue and couldn't ssh into an app with an isolated network. Even better, I would auto-detect the network for fly ssh console because AFAIK an app can only have one network.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants