-
Notifications
You must be signed in to change notification settings - Fork 182
feat: add IPFS_PROFILE to fix VPS NetScan abuse #1249
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
base: main
Are you sure you want to change the base?
Conversation
|
Important Review skippedAuto reviews are limited to specific labels. 🏷️ Labels to auto review (2)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
@rimrakhimov Can you help review it? |
|
@sevenzing Could you have a look? |
|
@sevenzing Could you have a look? |
|
@sevenzing @rimrakhimov ping |
ref: ipfs/kubo#8585 (comment)
Result:

(1) left:v0.14.0 right:v0.14.0+
IPFS_PROFILE=serverIt can be found from the log that after adding the environment variable, the scanning of the internal network was reduced.
(2)v0.14.0+

IPFS_PROFILE=serverrestart ipfs dockerleft: restart right: first time start
It can be found that after the restart, the internal network scanning situation is as expected.