Flycast between organisations with apps in custom private networks

Is it possible to use flycast to bridge apps across organizations, when the apps are both in custom private networks in their orgs ?

Here is what I tried:

Org one

  • App A - Created in it’s own custom network (org-one-app-a)

Org two

  • App B - Created in it’s own custom network (org-two-app-b)

I created a private IP for org one, app a, with org two permissions.
fly ips allocate-v6 --private --org org-two

However app b in org two cannot resolve app a in org one (or ping it’s IP6 address).

If I deploy app b in org two in the default network, then it works… But ideally I need to keep the apps isolated in org two.

1 Like

Interesting… Perhaps --network can just be combined with --org?

(The docs could be interpreted either way, and a quick glance at the source code didn’t reveal any measures preventing them both…)

Added proxy

Just ran a test, yes it appears you can add --network as well as org and then it works.

Only issue I have with that is I need to keep a flycast ipv6 for each app, and clean them up when I clean up the app’s… not the end of the world… still impressed by what you can do with Fly.

I might try and see if custom networks can access items in the org’s default network, and then I can just re architect a little around that…

I wonder if you can hit the private network call to get the list of address for both orgs

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.