From: Michael Aldridge <aldridge.mac@gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Troubleshooting 0kbps/0kbps video
Date: Fri, 14 May 2021 11:03:23 -0700 [thread overview]
Message-ID: <0a010004-21af-1fc1-d2cf-b45dbda7d1a3@gmail.com> (raw)
In-Reply-To: <87lf8hldwu.wl-jch@irif.fr>
>> Laptop -> VPN Server -> Proxy -> Proxy -> Proxy -> Galene
>
> Wow
Yeah the network architecture is slightly too exciting. If I add some
more labels it might make more sense as a traditional corporate service:
Laptop -> VPN Server -> Corp Edge -> Prod Edge -> Cluster Edge -> Galene
The VPN is a very traditional road-warrior setup, so knowledge of IPs
isn't a problem, there's already a nice dashboard that shows who's
likely to be on based on tunnel status.
> Yes. You need to put a TURN server somewhere where it can be reached by
> both the client and the server. So your diagram becomes:
>
> --------------> TURN Server <-------------
> / \
> Laptop -> VPN Server -> Proxy -> Proxy -> Proxy -> Galene
Since reaching all the way back into the corp network to see a client is
not practical in this network topology I'm trying to better understand
where/how to put the TURN server. Some cursory googling suggests that
its possible to tunnel all this traffic over HTTP. Is this something
that the built-in TURN server for Galene supports?
In your opinion is this network architecture even practical? With some
work I could refactor it to look like:
Laptop -> VPN Server -> LB -> Galene
I assume this would make things slightly cleaner from a traffic
management perspective, but that then involves spinning up a dedicated
machine for Galene which is a harder sell in my environment. If this is
the only practical approach though then that's what I'll explore.
--Michael
next prev parent reply other threads:[~2021-05-14 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 0:08 [Galene] " Michael Aldridge
2021-05-14 12:04 ` [Galene] " Juliusz Chroboczek
2021-05-14 18:03 ` Michael Aldridge [this message]
2021-05-14 19:03 ` Juliusz Chroboczek
2021-05-14 19:31 ` Michael Aldridge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a010004-21af-1fc1-d2cf-b45dbda7d1a3@gmail.com \
--to=aldridge.mac@gmail.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox