Skip to content
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.

Make it possible to not send outgoing traffic to RFC1918 addresses #13

Open
fabricedesre opened this issue Jan 11, 2023 · 5 comments
Open
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@fabricedesre
Copy link
Contributor

This triggers abuse behavior detection from some hosting providers like Hetzner.

Can we add a flag in the p2p config for that if we don't want to block these addresses in all situations?

@fabricedesre
Copy link
Contributor Author

@dignifiedquire any idea where I should look at? I got a bit lost in the maze of libp2p events to figure out if we can have a say in which discovered multiaddr we want to actually connect to.

@dignifiedquire
Copy link
Contributor

There are a couple of places where we could look, but to be sure we would need to filter all dials, including the ones happening in libp2p. I would suggest opening an issue on rust-libp2p asking how to avoid this, as I haven't found any API to do this. :/

@dignifiedquire dignifiedquire added bug Something isn't working help wanted Extra attention is needed labels Jan 23, 2023
@fabricedesre
Copy link
Contributor Author

I opened libp2p/rust-libp2p#3370

@fabricedesre
Copy link
Contributor Author

There's a promising solution in libp2p/rust-libp2p#3370 (comment)

@dignifiedquire
Copy link
Contributor

nice, PRs welcome :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants