-
Notifications
You must be signed in to change notification settings - Fork 6
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
firewall not set with fresh toolkit install on Debian10 #458
Comments
Might be related to #427 |
@szymontrocha Can you check if enabling the This can be done by adding the following line in the
and then installing the new version with:
And then rerun the perfSONAR script. |
I think this seem to change the situation:
|
That is indeed looking good. I think we can just provide the updated iptables 1.8.5 package in our repository, copied from |
I used a fresh Debian 10 and added this apt sources file: https://perfsonar-repo.geant.org/debian/perfsonar-5.0-snapshot.list.
|
Well, that seems more complicated than anticipated. The new I'd suggest that instead we write a FAQ entry stating that if users want to make full use of the |
Would it be worth making activating that repository a standard step in the installation just as we do for EPEL on Red Hat systems? |
I'm not sure it's needed as a general rule, but maybe. This is the only case where that would help, but maybe we could benefit from newer versions of some other packages too. |
@szymontrocha Here is what I suggest to add to the FAQ: The
|
I added a FAQ entry |
I noticed that after fresh install of perfsonar-toolkit bundle under Debian 10.13 I don't have any perfsonar setting in firewall which I guess should open/block specific ports related to services:
The text was updated successfully, but these errors were encountered: