Skip to content
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

Another DoS? #2109

Open
SilmorSenedlen opened this issue Oct 22, 2024 · 21 comments
Open

Another DoS? #2109

SilmorSenedlen opened this issue Oct 22, 2024 · 21 comments

Comments

@SilmorSenedlen
Copy link

Good day
Just noticed an abnormally high transit traffic through my node: ~ 25 MiB/s / ~35k PPS

I2Pd_DoS_04

Usually transit is about 4-6 MiB/s, and occasionally reached up to 10 MiB/s (not counting other DoS).

Strangely, there is no abnormally large number of floodfills and/or increase in memory consumption (consumption frozen at devilish 666 MiB xD ), like in past DoS attacks.

I2Pd_DoS_04_Res

Apparently, this has been going on for about half a day, so, in my opinion, it does not look like an episodic increase in transit.

Any thoughts ?

@LLE8
Copy link

LLE8 commented Oct 22, 2024

2.53.1 and 2.54.0, both on Debian 11
There are the similar recent changes in performance characteristics, but less memory consumption, about 299000 KB after 83 d 22 h uptime and 237000 KB after 16 d 21 h uptime.

@Vort
Copy link
Contributor

Vort commented Oct 22, 2024

You are right, network is under attack.

  1. Several days ago unusually high amount of routers from China was added. Probably, this is where attack originates from;
  2. Right now attack consists only from abnormally high transit traffic.

image
(https://i2p-metrics.np-tokumei.net/router-distribution)

@LLE8
Copy link

LLE8 commented Oct 22, 2024

I2PD 2.53.1 and 2.54.0, on relatively inexpensive VDS, http://flibusta.i2p/ is available, it seems the DoS is not fully effective yet.

@Vort
Copy link
Contributor

Vort commented Oct 22, 2024

it seems the DoS is not fully effective yet

High traffic comes in spikes.
When there are no spike, data can flow as usual (almost).

Here is CPU load chart for my router (which is highly correlated with attack traffic):
image

@LLE8
Copy link

LLE8 commented Oct 22, 2024

Tunnel creation success rate is too low, about 6-8%, compared to normal operation not under attack about 15-20%

@Vort
Copy link
Contributor

Vort commented Oct 22, 2024

Tunnel creation success rate is too low, about 6-8%, compared to normal operation not under attack about 15-20%

Attacker can do something else besides high traffic, but it is unclear what exactly.
TCSR started decreasing right after extra routers were added to the network (before attack with high transit was started).

@mittwerk
Copy link
Contributor

@Vort Can you just ban the new Chinese routers?

@Vort
Copy link
Contributor

Vort commented Oct 22, 2024

@Vort Can you just ban the new Chinese routers?

It won't have much effect.
My router have no direct connections to their routers (I think they banned me long time ago with Great Firewall).
But transit traffic goes through lots of other random nodes and nothing can be done with it.

@LLE8
Copy link

LLE8 commented Oct 22, 2024

What are these "new Chinese routers" doing illegal? Are there any formal reasons for ban? They are simply using the i2p network as it intended, i think.

@orignal
Copy link
Contributor

orignal commented Oct 24, 2024

They malfunction. They declare themselves as floodfills, but don't serve as floodfiils.

@LLE8
Copy link

LLE8 commented Oct 30, 2024

I2PD process killed by OOM-killer as a result of the attack.

@Vort
Copy link
Contributor

Vort commented Oct 30, 2024

I2PD process killed by OOM-killer as a result of the attack.

My node on version 2.54.0-61-g0086f8e2 uses 192 MB of RAM right now, despite high transit traffic of attack.
I think RAM consumption is ok.

@LLE8
Copy link

LLE8 commented Oct 30, 2024

May be uptime is too short.

@SilmorSenedlen
Copy link
Author

I2PD process killed by OOM-killer as a result of the attack.

Over past time of constant load(~6-18 MiB/s), memory consumption on my node increased only by ~ 40 MiB.

@orignal
Copy link
Contributor

orignal commented Oct 30, 2024

Are you a floodfill?

@SilmorSenedlen
Copy link
Author

SilmorSenedlen commented Oct 31, 2024

Are you a floodfill?

Yep


ipv4 = true
ipv6 = true
bandwidth = X
share = 100
notransit = false
transittunnels = 200000
floodfill = true

@SilmorSenedlen
Copy link
Author

Another significant spike:
I2Pd_DoS_05

Now with much more transit tunnel count.

Probably will have to lower bandwidth of node to not to clog channel with that parasitic traffic -_-

@Vort
Copy link
Contributor

Vort commented Nov 3, 2024

Interestingly, yesterday it was possible to observe network state without attack:
On my node, TCSR was 30%. Today it is lowered to 12%.

Now with much more transit tunnel count.

Do you know that transit tunnel count depends on TCSR value?
Twice lower TCSR means twice higher tunnel count.
I think high count in this case means just overload state of network.

@SilmorSenedlen
Copy link
Author

Interestingly, yesterday it was possible to observe network state without attack

Yeah, bw had deceased on my node to 2-4 MiB, almost all day.

Do you know that transit tunnel count depends on TCSR value?

No, I didn't know that.

I think high count in this case means just overload state of network.

Very sad : /

@Vort
Copy link
Contributor

Vort commented Nov 3, 2024

No, I didn't know that.

Failed transit tunnels are still tracked as alive, because transit node can't check if they are fine.

@LLE8
Copy link

LLE8 commented Nov 3, 2024

Over past time of constant load(~6-18 MiB/s), memory consumption on my node increased only by ~ 40 MiB.

fresh trunk i2pd version 2.54.0-64-g4432c5a2 (0.9.64)
Uptime 2 d 10 h
Mem ~ 250000 kB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants