GeyserMC / Geyser

A bridge/proxy allowing you to connect to Minecraft: Java Edition servers with Minecraft: Bedrock Edition.
https://geysermc.org
MIT License
4.72k stars 675 forks source link

All bedrock clients crashing because of "Too many packets" #4926

Open galuxosi opened 2 months ago

galuxosi commented 2 months ago

Describe the bug

So I made a hide and seek server for me and my friends, using geysermc and viaversion, we played it and everything was cool, but we noticed that when the 4 player joins, every bedrock client is crashing after 30 seconds. In console it says "[epollEventLoopGroup-3-1/WARN]: [org.cloudburstmc.netty.handler.codec.raknet.server.RakServerRateLimiter] [/176.124.134.179] Blocked because packet limit was reached"

I tried to fix it by making lower the packets limit in paper config and viaversion, but now, it crashing even with 1 java client and 1 bedrock client. Also, I and friends were using the same wifi, but it's kicks you even if you the only bedrock client on server.

To Reproduce

  1. Install Geysermc and Viaversion plugins 2. Join the server from java client 3. Join the server from bedrock client 4. Play for 30 seconds on bedrock 5. Get every bedrock client kicked.

Expected behaviour

Well I think there is shouldn't be any bedrock clients kicked when played.

Screenshots / Videos

No response

Server Version and Plugins

No response

Geyser Dump

https://dump.geysermc.org/MWzzpJiydCMRXCwvkiRSUlmHDH5g4v0V

Geyser Version

In aternos: 632 (Bedrock v1.20.80 - v1.21.2)

Minecraft: Bedrock Edition Device/Version

Any version on android starting from 1.20.1 (bedrock)

Additional Context

I think it can be also a hide and seek plugin problem, but i used it a year ago, and everything was fine even when used the same wifi(literally the same)

onebeastchris commented 2 months ago

Are all 4 of you joining from the same IP?

galuxosi commented 2 months ago

Idk but we used the same wifi

galuxosi commented 2 months ago

I just checked and yes, we were using the same ip

onebeastchris commented 2 months ago

Hm, yeah, that's probably an oversight over the new network limits. We'll work on those soon, for the meantime, there's a few temporary fixes: