I notice that there is a code "429: Denied due to excessive requests. Please try again later." in the source code of I2P here: https://github.com/i2p/i2p.i2p/blob/mas ... nager.java
I wonder how the server side decides that 2 requests are from the same router cos I notice this error code several times when I try to open 2-3 tabs of zzz.i2p. Does this approach help against DOS/DDOS attacks to an eepsite? Or it can't help if an eepsite is being requests from many sources?
How does an eepsite decide that requests are from the same requesting source?
-
spammywindy
- Posts: 11
- Joined: 02 May 2018 20:00
Re: How does an eepsite decide that requests are from the same requesting source?
Hi
as in every TCP/IP based networks, a source address is sent along with the request to the server.
In I2P those are b64 addresses, for hidden services those are fixed until keyfile get coruppt or missing. For clients those are are until next tunnel restart.
You can use stable client b64 if you tick the checkmark box in tunnel settings.
So a client is identified by its (temporary) b64 address, which is needed to send data back towards.
echelon
as in every TCP/IP based networks, a source address is sent along with the request to the server.
In I2P those are b64 addresses, for hidden services those are fixed until keyfile get coruppt or missing. For clients those are are until next tunnel restart.
You can use stable client b64 if you tick the checkmark box in tunnel settings.
So a client is identified by its (temporary) b64 address, which is needed to send data back towards.
echelon