Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Ability to 100% disable all federation for a synapse #2619

Closed
ara4n opened this issue Nov 1, 2017 · 8 comments
Closed

Ability to 100% disable all federation for a synapse #2619

ara4n opened this issue Nov 1, 2017 · 8 comments

Comments

@ara4n
Copy link
Member

ara4n commented Nov 1, 2017

So far we've recommended people who want a non-federated synapse to disable inbound federation by removing the federation listener. However, in practice it seems that the synapse may will emit outbound federated traffic (e.g. for invites) which will never complete. Having a config option to cleanly and completely disable federation seems like a no-brainer. I thought we already had an ancient 2014-vintage bug for this, but can't find it anywhere.

@bennabiy
Copy link

+1

@Half-Shot
Copy link
Collaborator

Is this fixed by #2820 @ara4n ?

@ara4n
Copy link
Member Author

ara4n commented Mar 17, 2018

why yes it is :)

@ara4n ara4n closed this as completed Mar 17, 2018
@jeremiah-k
Copy link

What is the procedure, please?

@krombel
Copy link
Contributor

krombel commented Apr 11, 2018

@kcsrnd Have you read my comment on issue #2820?

@jeremiah-k
Copy link

I thought I had, somehow I missed your comment at the bottom. Got it now. Thanks.

@oliverjanik
Copy link

Is there a Guide how to setup a separate isolated federation cluster?

@krombel
Copy link
Contributor

krombel commented Apr 24, 2018

As of #2820 you can put the following in your config:

federation_domain_whitelist:
- chat1.example.com
- chat2.example.com
- <otherServerName>

d3m3vilurr added a commit to d3m3vilurr/matrix-dockers that referenced this issue Jun 26, 2019
this option is stressful & reduce server performance.

ref:
- matrix-org/synapse#2619
- matrix-org/synapse#2917
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants